API marketplace

Landscaping material estimating as an API — the "how much mulch, soil or gravel do I need" maths, computed locally and deterministically. The coverage endpoint works out the volume to cover an area at a depth — in cubic yards, cubic metres, cubic feet and litres — and, given a material or a custom bulk density, the weight in US tons, tonnes and kilograms, plus the number of bags for a given bag size. The area can be entered directly or as a rectangular, circular or triangular bed, and depth in inches, centimetres, feet or metres. The depth endpoint is the inverse: it works out the depth that an available volume (or a number of bags) gives over an area — handy when you already have a load of material. The material endpoint is a reference of typical bulk densities (mulch, compost, topsoil, gravel, sand) and how much area one cubic yard covers at 1 to 4 inch depths. Everything is computed locally and deterministically, so it is instant and private. Densities are typical values and bulk material varies with moisture and compaction, so order around 5–10% extra. Ideal for landscaping and garden-centre tools, hardscaping and bulk-material retailers, and DIY and yard-project planners. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is landscaping-material estimating; for paint, tiles, concrete and bricks use a construction-calculator API.

Uptime

100.0%

Latency

183ms

Subs

3,791

Tank volume and fill-level maths as an API, computed locally and deterministically. The volume endpoint gives the total capacity — in litres, US gallons and cubic metres — of a vertical cylinder, horizontal cylinder, rectangular tank, sphere or capsule, from its dimensions in metres, centimetres, millimetres, feet or inches. The fill endpoint computes the volume of liquid and the percent full at a given fill depth, using the exact geometry for each shape — including the circular-segment formula for a horizontal cylinder (where the level is famously non-linear) and the spherical-cap formula for a sphere. The level endpoint is the inverse "dipstick" calculation: it finds the depth that corresponds to a target volume or a target percentage, solving the segment geometry by bisection. Everything is computed locally and deterministically, so it is instant and private. Ideal for fuel, water, oil and chemical tank monitoring, agriculture and irrigation, process and industrial tooling, and tank-gauging and dipstick apps. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is tank-gauging geometry; for swimming-pool volume and chemical dosing use a pool API, and for plain unit conversion use a unit-conversion API.

Uptime

100.0%

Latency

159ms

Subs

4,465

Marketing and advertising metrics as an API — the everyday campaign maths, computed locally and deterministically and entirely currency-agnostic. The funnel endpoint takes any of impressions, clicks, conversions, spend and revenue and computes every metric the inputs allow: click-through rate (CTR), cost per click (CPC), cost per mille (CPM), conversion rate, cost per acquisition (CPA), average order value, return on ad spend (ROAS), return on investment (ROI) and profit — anything not derivable is returned as null rather than guessed. The roas endpoint focuses on profitability: ROAS, ROI and profit, and — given a gross margin — the break-even ROAS and gross profit, with a profitable flag. The target endpoint reverse-plans a campaign: from a conversion or revenue goal and your known rates it works out the required clicks, impressions and budget and the expected revenue and ROAS. Everything is computed locally and deterministically, so it is instant and private. Rates such as conversion_rate and ctr are given as fractions (0.05 = 5%). Ideal for marketing dashboards and reporting, media-buying and bid tools, agency and campaign planners, and e-commerce analytics. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is advertising-metric maths; for loan and investment maths use a finance-calculator API.

Uptime

100.0%

Latency

153ms

Subs

4,862

Swimming-pool maths as an API, computed locally and deterministically. The volume endpoint computes the water volume of a rectangular, round or oval pool — in litres, US gallons and cubic metres — from the dimensions and either an average depth or separate shallow and deep depths (it averages them), in feet or metres. The dose endpoint computes how much of a chemical to add to raise a level by a target ppm: give the pool volume and the desired increase, and either the product strength percent or a preset (cal-hypo, dichlor, trichlor, liquid chlorine, bleach), and it returns the amount in grams, kilograms, ounces and pounds. The salt endpoint computes the salt needed to reach a target salinity in a saltwater pool from the current and target ppm, in kilograms and pounds (and 40 lb bags). Everything is computed locally and deterministically, so it is instant and private. Dosing depends on the actual product strength and your test readings — always follow the product label, add in stages and re-test before adding more. Ideal for pool-service and maintenance apps, pool-builder and retailer tools, and smart-pool and home-automation systems. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is pool maths; for general volume or unit conversion use a unit-conversion API.

Uptime

100.0%

Latency

177ms

Subs

4,442

Battery and accumulator maths as an API, computed locally and deterministically from basic electrical relationships. The runtime endpoint estimates how long a battery will last under a given load — from the capacity (in mAh, Ah or Wh) and the load (in watts, or amps at a voltage), with adjustable depth-of-discharge and conversion efficiency — and reports the usable energy and the runtime in hours and minutes. The capacity endpoint converts a battery capacity between milliamp-hours, amp-hours, watt-hours, kilowatt-hours and joules at a given voltage. The pack endpoint builds a series/parallel cell pack (for example 3S2P): it returns the pack voltage, capacity and energy and the total cell count — series adds voltage, parallel adds capacity. The charge endpoint estimates the charge time from the capacity and the charge current (or a C-rate), with a charge efficiency and an optional from/to state-of-charge window. Everything is computed locally and deterministically, so it is instant and private. Real-world figures depend on temperature, age, C-rate and the discharge curve, so treat the results as estimates. Ideal for consumer-electronics and IoT tools, solar and off-grid sizing, drone and RC planning, UPS and backup-power sizing, and EV and battery-pack design. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is battery maths; for Ohm's-law voltage/current/resistance use an electronics API.

Uptime

100.0%

Latency

181ms

Subs

4,005

Shipping dimensional-weight maths as an API. Carriers bill the greater of a parcel's actual weight and its dimensional (volumetric) weight — the volume divided by a carrier "dim divisor" — so a big, light box can cost far more than the scales suggest. The dimweight endpoint computes the dimensional weight in both pounds and kilograms from the length, width and height (in inches or centimetres) and a dim divisor, which you can give directly or pick by carrier (UPS, FedEx, USPS, DHL, IATA). The billable endpoint takes the actual weight as well and returns the billable weight — the greater of actual and dimensional — telling you which one you will be charged on. The girth endpoint computes the girth (twice the width plus height of the two smaller sides), the length-plus-girth and the longest side, and flags whether the parcel is oversize against length limits (defaulting to typical US ground values). Everything is computed locally and deterministically, so it is instant and private. Ideal for e-commerce checkout and shipping estimators, fulfilment and warehouse tools, freight and logistics software, and packaging optimisation. Pure local computation — no key, no third-party service, instant. Live, nothing stored. Divisors and limits are typical published values — confirm with your carrier and service. 3 endpoints. This is dimensional-weight maths; for live shipping rates use a carrier's own API, and for plain unit conversion use a unit-conversion API.

Uptime

100.0%

Latency

176ms

Subs

3,013

Gross-pay maths as an API — the everyday salary and wage calculations, computed locally and deterministically and entirely currency-agnostic. The convert endpoint turns a pay figure given at any cadence — annual, monthly, bi-weekly, weekly, daily or hourly — into all the others, using configurable hours per week, weeks per year and days per week. The overtime endpoint computes regular, overtime (time-and-a-half by default) and double-time pay from the hours worked, with adjustable thresholds and multipliers, and reports the effective hourly rate. The raise endpoint applies a percentage or fixed raise, or works out the percentage from a new salary. The prorate endpoint pro-rates a salary by a worked fraction, or by days worked over days in the period — for joiners, leavers and part-periods. Everything is gross pay only: it deliberately excludes tax, deductions and benefits, which are jurisdiction-specific, so the maths stays exact and never goes stale. Computed locally, instant and private. Live, nothing stored. 4 endpoints. Ideal for HR and payroll tools, job boards and offer calculators, freelance and contractor rate tools, and budgeting apps. This is gross-pay maths; for loan, interest and investment maths use a finance-calculator API, and for net/take-home pay apply your local tax rules separately.

Uptime

100.0%

Latency

149ms

Subs

4,869

Blood-alcohol estimation as an API, using the Widmark equation, computed locally and deterministically. The estimate endpoint works out the peak and current blood-alcohol concentration — in both per mille (‰) and percent (%) — from the alcohol consumed, body weight, sex and the time elapsed since drinking, and tells you roughly how long until you are sober or back under a chosen legal limit. Alcohol can be given as grams, as US standard drinks, or as a drink volume and ABV. The drink endpoint is a standard-drink calculator: from a volume and ABV it returns the grams of pure alcohol, US standard drinks (14 g), UK units (10 ml) and EU standard drinks (10 g). The sober endpoint estimates the time for a current BAC to fall to zero or to a target limit at a chosen elimination rate. Everything is computed locally and deterministically, so it is instant and private. IMPORTANT: this is a rough estimate for educational use only — real blood-alcohol depends on many personal and situational factors. Never use it to decide whether it is safe or legal to drive; when in doubt, do not drive. Ideal for educational and harm-reduction tools, hospitality and event apps, and personal drink trackers. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is blood-alcohol maths; for the calories or nutrition of drinks use a food or nutrition API.

Uptime

100.0%

Latency

166ms

Subs

3,395

Construction and material estimating as an API — the everyday "how much do I need to buy" maths for building and renovation jobs, computed locally and deterministically from standard geometry and trade rules of thumb. The paint endpoint works out the litres and number of cans for a surface, allowing for the number of coats and the paint's coverage and deducting doors and windows. The tile endpoint computes how many tiles (and full boxes) a floor or wall area needs from the tile dimensions and a wastage allowance. The concrete endpoint gives the concrete volume in cubic metres, cubic yards and litres — and the number of pre-mix bags — for a slab, footing, wall or round column, with an optional batch quantity. The bricks endpoint computes how many bricks a wall needs from the brick size and mortar joint (default 215×65 mm brick with a 10 mm joint ≈ 60 bricks per square metre). Everything is computed locally and deterministically, so it is instant and private. Ideal for builders' merchants and trade apps, DIY and home-improvement tools, quoting and estimating software, and project planners. Pure local computation — no key, no third-party service, instant. Live, nothing stored. Estimates are guidance — allow for site conditions and follow the manufacturer's stated figures. 4 endpoints. This is materials estimating; for plain unit conversion use a unit-conversion API and for tyre or drivetrain maths use a tyre API.

Uptime

100.0%

Latency

165ms

Subs

4,171

International size conversion as an API, for the everyday wearables that ship in different scales around the world. The shoe endpoint converts a shoe size between EU (Paris point), UK, US men, US women, Mondopoint and foot length in centimetres — derived from the standard barleycorn and Paris-point relationships — and reports both the exact figure and the nearest standard half-size. The ring endpoint converts a ring size between US numeric, ISO 8653 (inside circumference in millimetres, used across most of Europe), inside diameter, inside circumference and the UK alphabetical scale. The hat endpoint converts a hat size between head circumference (centimetres or inches), the EU metric size, US and UK, with a simple S/M/L band. Everything is computed locally and deterministically, so it is instant and private. Ideal for fashion and footwear e-commerce, jewellery shops, size-guide widgets, returns-reduction tooling and international checkout. Pure local computation — no key, no third-party service, instant. Live, nothing stored. Guidance only — manufacturers' sizing varies, so always check the brand's own chart for a critical fit. 3 endpoints. This is wearable-size conversion; for plain length/weight unit conversion use a unit-conversion API.

Uptime

100.0%

Latency

167ms

Subs

3,233

Sleep-cycle planning as an API, built around the fact that a full sleep cycle averages about 90 minutes and that waking at the end of a cycle — rather than mid-cycle — leaves you feeling more refreshed. The bedtime endpoint takes a wake-up time and suggests the times to fall asleep so that you wake at the end of a whole number of cycles (6, 5, 4 or 3 cycles), allowing for the time it takes to drift off. The wake-time endpoint does the reverse: from a bedtime (or "now") it suggests the best times to set an alarm. The duration endpoint takes a bedtime and a wake time and reports time in bed, actual sleep, the number of full cycles, how many minutes you are into the current cycle and how close you are to a clean cycle boundary, with a healthy-duration assessment. The nap endpoint plans power, short, slow-wave and full-cycle naps from a start time and explains the trade-offs. All clock maths is modulo 24 hours and accepts both 24-hour ("23:15") and 12-hour ("10:30 PM") times. Everything is computed locally and deterministically, so it is instant and private. Ideal for sleep, alarm-clock and wellbeing apps, smart-home routines, shift-work planning and productivity tools. Pure local computation — no key, no third-party service, instant. Live, nothing stored. INFORMATIONAL ONLY — sleep needs vary by individual; not medical advice. 4 endpoints. This is sleep-cycle timing maths; for time-zone conversion use a time API and for body metrics such as BMI use a health-calculator API.

Uptime

100.0%

Latency

181ms

Subs

4,034

Standard clinical and nursing calculators as an API — the everyday medical maths, computed locally. The bsa endpoint computes body surface area from weight and height by the Mosteller, Du Bois and Haycock formulas (used for chemotherapy and drug dosing). The egfr endpoint estimates kidney function from serum creatinine, age and sex using the race-free CKD-EPI 2021 equation, and the Cockcroft-Gault creatinine clearance when a weight is given (creatinine in mg/dL or µmol/L). The drip-rate endpoint computes an IV infusion's drops per minute and millilitres per hour from the volume, time and drop factor. The gcs endpoint scores the Glasgow Coma Scale from its eye, verbal and motor components and gives the severity band. Everything is computed locally and deterministically, so it is instant and private. INFORMATIONAL ONLY — not medical advice; always verify with clinical judgement and approved tools. Ideal for healthcare and nursing apps, clinical decision-support prototypes, medical education, and EHR tooling. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is clinical maths; for drug reference data use a drug API and for BMI, BMR and calories use a health-calculator API.

Uptime

100.0%

Latency

153ms

Subs

3,661

Tyre, wheel and drivetrain maths as an API. The tire endpoint parses a metric tyre size such as 205/55R16 into all its real dimensions — section width, aspect ratio, sidewall height, rim and overall diameter in millimetres and inches, rolling circumference, and revolutions per kilometre and per mile. The compare endpoint takes an original and a replacement tyre size and works out the change in overall diameter and the resulting speedometer and odometer error — so you know how much faster you are really going than the dial shows after a tyre change. The gear endpoint computes a gear ratio from ring and pinion tooth counts, or the road speed from engine RPM, total gear ratio and tyre size. Everything is computed locally and deterministically, so it is instant and private. Ideal for automotive and motorsport apps, tyre shops and fitment tools, modding and restomod planning, and vehicle configurators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is tyre and drivetrain maths; for vehicle specifications by VIN use a vehicle-database API.

Uptime

100.0%

Latency

178ms

Subs

3,070

Scientific number representation as an API. The scientific endpoint expresses a number in both scientific notation (one digit before the decimal point × a power of ten) and engineering notation (the exponent a multiple of three, lining up with SI prefixes), and reports the mantissa and exponent. The sigfigs endpoint rounds a number to a chosen number of significant figures, and counts the significant figures in a value — respecting the rules for leading zeros, trailing zeros and the decimal point, and flagging the ambiguous cases such as "1200". The si-prefix endpoint formats a number with the right metric prefix (1500 → 1.5 k, 2.3×10⁹ → 2.3 G, 0.0023 → 2.3 m) with an optional unit, and parses a prefixed value back to a plain number (2.2 MΩ → 2,200,000). Everything is computed locally and deterministically, so it is instant and private. Ideal for science and engineering tools, lab and measurement software, electronics and signal work, and education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is scientific number representation; for locale number formatting use a number-format API and for number-to-words or Roman numerals use a number API.

Uptime

100.0%

Latency

167ms

Subs

4,896

Convert between latitude/longitude and the Maidenhead Locator System — the grid-square "QTH locator" (like JN58td or IO91wm) used by amateur radio, APRS and contesting to describe a position compactly. The encode endpoint turns a latitude and longitude into a locator at 4-, 6-, 8- or 10-character precision. The decode endpoint turns a locator back into the centre coordinates, the south-west corner and the size of the grid square. The distance endpoint gives the great-circle distance (kilometres and miles) and bearing between the centres of two locators — the classic "how far and which way is that station". Everything is computed locally and deterministically, so it is instant and private. Ideal for amateur-radio and APRS tools, contest logging, antenna aiming, and grid-based mapping. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is the Maidenhead system; for Plus Codes, MGRS, UTM and DMS use a geo-convert API and for precise geodesic distance use a geodesy API.

Uptime

100.0%

Latency

156ms

Subs

4,890

Media, file-size and data-transfer maths as an API. The file-size endpoint relates bitrate, duration and file size: give any two and it computes the third — so you can find the size of a video at a given bitrate and length, the bitrate of a file of known size and length, or how long a file will play. The transfer-time endpoint computes how long a file takes to download or upload over a given bandwidth (with optional protocol overhead), or the bandwidth needed to move it within a target time. The storage endpoint works out how many hours of media at a bitrate, or how many items of a given size, fit in a storage capacity. Bitrates use decimal units (kbps, Mbps, Gbps) and sizes are reported in both decimal (KB/MB/GB/TB) and binary (KiB/MiB/GiB/TiB). Everything is computed locally and deterministically, so it is instant and private. Ideal for video and audio encoding, streaming and CDN planning, storage and backup sizing, and download-time estimates. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is bitrate and transfer maths; for plain byte-unit conversion use a bytes API.

Uptime

100.0%

Latency

168ms

Subs

3,136

Cycling performance maths as an API. The power endpoint estimates the power in watts needed to ride at a given speed on a given gradient, from a physical model — rolling resistance, gravity on the climb, and aerodynamic drag — with sensible defaults you can override (rolling-resistance coefficient, drag area CdA, air density, drivetrain efficiency and headwind), and breaks the power down into its rolling, gravity and aero components plus watts-per-kilogram. The ftp-zones endpoint turns a Functional Threshold Power into the seven Coggan training zones, from active recovery to neuromuscular power, as watt ranges. The vam endpoint computes VAM — vertical ascent metres per hour, the climbing-speed metric — either from elevation gained and time, or from speed and gradient. Everything is computed locally and deterministically, so it is instant and private. Ideal for cycling and training apps, bike computers and power-meter tools, coaching, and route and climb analysis. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is cycling maths; for running pace use a pace API and for heart-rate training zones use a heart-rate API.

Uptime

100.0%

Latency

175ms

Subs

4,139

Advanced geodesy beyond the simple great circle. The vincenty endpoint computes the distance between two latitude/longitude points on the WGS84 ellipsoid using Vincenty's inverse formula — accurate to within a millimetre, far better than the spherical approximation — plus the initial and final bearings, in metres, kilometres, miles and nautical miles. The rhumb endpoint computes the rhumb-line (loxodrome) distance and the single constant compass bearing that follows it — the path you steer by holding a heading, as used in marine and air navigation. The cross-track endpoint finds how far a point lies to the left or right of a great-circle path between two points (the cross-track distance) and how far along that path it is (the along-track distance). Everything is computed locally and deterministically, so it is instant and private. Ideal for marine and aviation navigation, surveying and GIS, route analysis, and precise mapping. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is advanced geodesy; for simple great-circle distance, bearing, midpoint and destination use a geo-distance API and for coordinate-format conversion use a geo-convert API.

Uptime

100.0%

Latency

151ms

Subs

4,278

Computational geometry for arbitrary polygons and point sets — on a plane, with no map or shape templates needed. The area endpoint takes a polygon as a list of [x,y] vertices and returns its area (by the shoelace formula), perimeter, centroid, winding orientation (clockwise or counter-clockwise), whether it is convex, and its bounding box. The contains endpoint tests whether a point is inside a polygon, outside it, or exactly on its boundary, using robust ray casting that handles concave shapes correctly. The convex-hull endpoint computes the convex hull of a set of points by Andrew's monotone chain, along with its area and perimeter. It works for any simple polygon, convex or concave. Everything is computed locally and deterministically, so it is instant and private. Ideal for graphics and game development, GIS and mapping, CAD and collision detection, computational geometry, and data visualisation. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is planar polygon geometry; for the area of named shapes (circle, triangle, …) use a geometry API and for geographic GeoJSON area on the earth use a GeoJSON API.

Uptime

100.0%

Latency

161ms

Subs

3,594

Probability distributions and combinatorics as an API. The binomial endpoint gives the probability of exactly k successes in n trials (PMF), the cumulative probability up to k (CDF), and the mean, variance and standard deviation. The poisson endpoint does the same for the Poisson distribution from a rate λ. The normal endpoint computes the z-score, probability density, cumulative probability (CDF) and percentile for a value under a normal distribution with any mean and standard deviation — and runs in reverse, turning a probability into the value (the quantile / inverse CDF) and its z-score. The combinatorics endpoint computes combinations (nCr), permutations (nPr) and factorials with exact big-integer arithmetic. Everything is computed locally and deterministically, so it is instant and private. Ideal for data science and statistics, quality control and A/B-test planning, gaming and gambling odds, risk modelling, and statistics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 5 endpoints. This is probability theory; for descriptive statistics on a dataset use a statistics API and for general expression evaluation use a math API.

Uptime

100.0%

Latency

144ms

Subs

4,509

Camera and optics maths as an API. The depth-of-field endpoint computes the near and far limits of sharp focus, the total depth of field and the hyperfocal distance from a focal length, aperture and focus distance, using the circle of confusion for your sensor format — full-frame, APS-C, Micro Four Thirds, 1-inch, medium format, Super 35 and more, or your own value. The field-of-view endpoint gives the horizontal, vertical and diagonal angle of view for a focal length on a given sensor, plus the crop factor and the 35 mm-equivalent focal length. The exposure endpoint computes the exposure value (EV) from aperture, shutter speed and ISO, and can also solve for the shutter speed or aperture that hits a target EV. Everything is computed locally and deterministically, so it is instant and private. Ideal for photography and videography apps, camera and lens tools, focus-stacking and landscape planning, and teaching exposure and optics. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This computes camera optics; for reading EXIF metadata from photo files use an EXIF API.

Uptime

100.0%

Latency

156ms

Subs

3,044

Classical-mechanics maths as an API. The kinematics endpoint is a full SUVAT solver: give any three of initial velocity (u), final velocity (v), acceleration (a), time (t) and displacement (s) and it computes the rest using the standard constant-acceleration equations. The projectile endpoint takes a launch speed and angle (and an optional launch height and gravity) and returns the horizontal and vertical velocity components, the time to the peak, the maximum height, the total flight time, the range and the impact speed. The free-fall endpoint computes a vacuum fall from a height or for a time, with an optional initial velocity, returning the fall time, distance and impact velocity. Gravity defaults to standard 9.80665 m/s² but can be set for the Moon, Mars or any body. Everything is computed locally and deterministically in SI units, so it is instant and private. Ideal for physics education and homework, engineering and simulation, game and ballistics development, and motion tools. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is motion physics; for planetary data use a planets API and for unit conversion use a unit API.

Uptime

100.0%

Latency

155ms

Subs

4,223

Musical timing maths as an API — turn a tempo into exact times. The durations endpoint gives the length of every note value (whole down to sixty-fourth, plus dotted and triplet variants) at a given BPM, in milliseconds, in hertz, and in samples at your sample rate. The delay endpoint is the producer's note-to-millisecond tool: the delay and reverb times for 1/1 to 1/32 (straight, dotted and triplet) so time-based effects lock to the tempo. The bar endpoint gives the duration of a bar for any time signature. The convert endpoint turns BPM into milliseconds per beat (and back) and names the Italian tempo marking — Largo, Adagio, Andante, Moderato, Allegro, Presto and the rest. Everything is computed locally and deterministically, so it is instant and private. Ideal for DAWs and music-production tools, drum machines and sequencers, delay and echo plug-ins, metronomes, and audio apps. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is tempo and rhythm timing; for notes, intervals, chords and scales use a music-theory API.

Uptime

100.0%

Latency

182ms

Subs

3,054

Strength-training maths as an API. The one-rep-max endpoint estimates your one-rep max from a set of a given weight and reps using five established formulas — Epley, Brzycki, Lander, Lombardi and O'Conner — with their average, and returns a rep-max table showing the estimated weight (and percentage of 1RM) for 1 to 12 reps. The plates endpoint works out exactly which plates to load on each side of a barbell for a target weight, given the bar weight and the plate denominations you have, and tells you whether the target is achievable exactly. The wilks endpoint computes the Wilks (classic) and DOTS relative-strength scores from bodyweight and total lifted, so lifters of different sizes can be compared fairly. Everything is computed locally and deterministically, so it is instant and private. Ideal for gym and lifting apps, powerlifting and strength coaching, workout planners and progression trackers, and fitness wearables. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is strength maths; for BMI, BMR and calories use a health-calculator API and for heart-rate training zones use a heart-rate API.

Uptime

100.0%

Latency

166ms

Subs

4,094