API Marketplace

Wi-Fi channel maths as an API, computed locally and deterministically from the standard channel-numbering formulas. The channel endpoint returns the centre frequency of a Wi-Fi channel on the 2.4, 5 or 6 GHz band — the band is auto-detected from the channel number or can be given explicitly (2.4 GHz: 2407 + 5·channel, with channel 14 at 2484; 5 GHz: 5000 + 5·channel; 6 GHz: 5950 + 5·channel). The frequency endpoint does the reverse, returning the nearest channel and band for a centre frequency in MHz or GHz. The overlap endpoint reports whether two channels overlap at a chosen channel width (two channels overlap when their centre-frequency separation is less than the width) and gives the recommended non-overlapping set — the classic 1, 6 and 11 on 2.4 GHz at 20 MHz. Everything is computed locally and deterministically, so it is instant and private. Channel availability is regulated and varies by country. Ideal for networking and Wi-Fi tools, site-survey and IoT apps, and router and access-point configuration software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is Wi-Fi channel mapping; for general wavelength/frequency and photon energy use a wavelength API.

Tempo di attività

100.0%

Latenza

81ms

Abbonati

4,228

Matemáticas de notas de un solo curso como API, calculadas local y determinísticamente — los cálculos cotidianos de "qué necesito en el final" para estudiantes. El endpoint needed calcula la puntuación requerida en el examen final (o cualquier componente restante) para alcanzar una nota objetivo general, a partir de la nota actual y el peso que tiene el final, e indica si el objetivo es alcanzable o ya está asegurado. El endpoint projected da la nota general con la que terminarías para una puntuación hipotética en el final. El endpoint average calcula el promedio ponderado de componentes calificados a partir de una lista simple de puntuación:peso (como 90:40,80:60), e informa el peso total y restante para que puedas ver cuánto del curso aún no está calificado. Los porcentajes van de 0 a 100 y los pesos aceptan tanto un porcentaje (30) como una fracción (0.3). Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Ideal para aplicaciones de estudiantes y estudio, herramientas de gestión de aprendizaje, y sitios de tutoría y educación. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada se almacena. 3 endpoints. Esta es la mecánica de notas de un solo curso; para un promedio de notas de varios cursos con horas de crédito, usa una API de GPA.

Tempo di attività

100.0%

Latenza

78ms

Abbonati

4,933

Staircase geometry as an API, computed locally and deterministically. The calc endpoint takes the total rise (floor-to-floor height) and works out the number of steps, the exact riser height, the tread depth, the total run, the stringer (hypotenuse) length and the stair angle, and checks the result against building-code limits and the Blondel comfort rule (2 × riser + tread ≈ 24–25 in). The check endpoint validates a given riser and tread against typical US IRC limits — maximum riser 7.75 in, minimum tread 10 in — and reports the angle and comfort. The stringer endpoint returns the stringer length and angle from a total rise and total run. Dimensions are handled internally in inches but accept inches, centimetres, millimetres and metres. Everything is computed locally and deterministically, so it is instant and private. Code limits are typical US IRC values — always confirm your local building code. Ideal for construction and carpentry tools, deck and home-improvement apps, and architecture and CAD software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is staircase geometry; for paint, tile and concrete quantities use a construction-calculator API and for roof pitch use a roofing API.

Tempo di attività

100.0%

Latenza

73ms

Abbonati

3,995

Antenna length maths as an API, computed locally and deterministically. The dipole endpoint gives the total and per-leg length of a half-wave dipole for a frequency, in metres, feet, inches and centimetres, applying a velocity factor (about 0.95 for wire) and also reporting the classic 468 ÷ f(MHz) feet rule of thumb. The quarterwave endpoint gives the element length of a quarter-wave vertical or monopole, with the 234 ÷ f(MHz) rule. The element endpoint computes the length of an element at any fraction of a wavelength — full-wave, half-wave, quarter-wave, fifth-wave, five-eighths or a custom fraction. Frequencies accept Hz, kHz, MHz and GHz, and the velocity factor is configurable. Everything is computed locally and deterministically, so it is instant and private. These are starting lengths: real antennas need trimming and tuning for the lowest SWR, as end effects and surroundings shift the resonant length. Ideal for amateur-radio and RF tools, antenna and IoT design, and electronics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is antenna geometry; for general wavelength, frequency and photon energy use a wavelength API.

Tempo di attività

100.0%

Latenza

75ms

Abbonati

3,063

Electromagnetic-wave maths as an API, computed locally and deterministically. The convert endpoint converts between wavelength and frequency (λ = c ÷ f) and also reports the period, the wavenumber, the photon energy and the part of the spectrum — optionally for light travelling in a medium of a given refractive index, where the wavelength scales by 1/n while the frequency stays the same. The energy endpoint gives the photon energy in joules, electron-volts and kilo-electron-volts from a wavelength or frequency (E = h·f = h·c ÷ λ). The band endpoint classifies a wavelength or frequency into the electromagnetic spectrum — radio, microwave, infrared, visible, ultraviolet, X-ray or gamma — and adds the ITU radio sub-band (ELF through EHF) and the approximate colour for visible light. Frequencies accept Hz/kHz/MHz/GHz/THz and wavelengths m/cm/mm/µm/nm/pm/ångström. Everything is computed locally and deterministically, so it is instant and private. Ideal for RF and antenna tools, optics and photonics, spectroscopy and lab software, physics and astronomy education, and amateur radio. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is electromagnetic-wave physics; for general unit conversion use a unit-conversion API.

Tempo di attività

100.0%

Latenza

77ms

Abbonati

3,007

Blood-type compatibility as an API, covering the ABO and Rh(D) systems, computed locally and deterministically. The compatibility endpoint says whether a given donor can give to a given recipient, for both red blood cells and plasma — the red-cell rule being that the donor's antigens must be a subset of the recipient's (Rh included), and plasma being the reverse and ignoring Rh. The info endpoint describes a blood type: the antigens it carries, the antibodies in its plasma, every type it can receive red cells from and donate red cells to, who it can give plasma to, whether it is a universal red-cell donor (O−), universal red-cell recipient (AB+) or universal plasma donor (AB), and its approximate US population frequency. The donors endpoint lists every compatible donor type for a recipient, for red cells or plasma. Blood types are accepted in many forms (O-, O neg, AB positive, …). Everything is computed locally and deterministically, so it is instant and private. This is educational only — real transfusion requires laboratory cross-matching and clinical judgement, and it is not medical advice. Ideal for medical-education and first-aid apps, blood-donation and health tools, and quiz and reference sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is ABO/Rh compatibility; for a drug reference database use a drug API.

Tempo di attività

100.0%

Latenza

74ms

Abbonati

4,209

Matemáticas del metabolismo de la cafeína como API, calculadas local y determinísticamente con un modelo de decaimiento de primer orden (exponencial). El endpoint de nivel calcula cuánta cafeína permanece en el cuerpo después de un tiempo dado desde una dosis y una vida media (aproximadamente 5 horas por defecto), en miligramos y porcentaje, y cuánto tiempo hasta que caiga a un umbral elegido. El endpoint de línea de tiempo devuelve una curva de decaimiento hora por hora y el tiempo hasta que la cafeína sea "segura para dormir" — por debajo de un umbral (50 mg por defecto) — útil para calcular un límite de café antes de acostarse. El endpoint de fuentes proporciona el contenido típico de cafeína de bebidas comunes (café filtrado, espresso, té, bebidas energéticas, cola y más) para una sola bebida, o totaliza una lista como dos cafés y una cola. Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Esto es solo informativo: la vida media real de la cafeína varía ampliamente entre personas (aproximadamente 3–7 horas, y mucho más larga durante el embarazo o con ciertos medicamentos) — no es consejo médico. Ideal para aplicaciones de café, sueño y bienestar, rastreadores de bebidas energéticas y hábitos, y herramientas de cuantificación personal. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 3 endpoints. Esto es farmacocinética de la cafeína; para una base de datos de referencia de medicamentos, use una API de medicamentos.

Tempo di attività

100.0%

Latenza

78ms

Abbonati

3,652

Fencing material estimating as an API, computed locally and deterministically. The posts endpoint works out the number of fence sections, line posts and rails for a run from its length and the post spacing, plus the total rail length. The pickets endpoint computes how many pickets or boards a length needs from the picket width and the gap between boards (set the gap to zero for a privacy fence). The materials endpoint produces a full bill of materials in one call — posts, rails, pickets and the concrete for the post holes, in cubic feet and metres and in 80 lb pre-mix bags — from the fence dimensions and the hole size and post depth. Everything is computed locally and deterministically, so it is instant and private. These are estimates: allow extra for waste, gates and corner posts, and follow your local building code for post depth and footing size. Picket width and gap are in inches; length can be feet, yards or metres. Ideal for fencing contractors and estimators, DIY and home-improvement tools, and landscaping and quoting software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is fencing materials; for paint, tile and concrete use a construction-calculator API and for mulch and gravel use a landscaping API.

Tempo di attività

100.0%

Latenza

82ms

Abbonati

3,191

Matemáticas de dimensionamiento de HVAC como API, calculadas local y determinísticamente a partir de factores estándar de regla general. El endpoint de refrigeración estima la carga del aire acondicionado para una habitación — en BTU por hora, toneladas de refrigeración y kilovatios — a partir del área del piso (en pies cuadrados o metros, o largo × ancho) usando una línea base de aproximadamente 20 BTU/h por pie cuadrado, con ajustes por el número de ocupantes, una cocina, exposición solar y altura del techo. El endpoint de calefacción estima la carga de calefacción a partir del área y una zona climática (templada a muy fría) o un BTU personalizado por pie cuadrado. El endpoint de conversión convierte entre BTU por hora, toneladas de refrigeración, kilovatios y vatios (una tonelada = 12,000 BTU/h ≈ 3.517 kW). Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Estas son estimaciones de regla general al estilo EnergyStar — se recomienda un cálculo de carga Manual J adecuado que tenga en cuenta el aislamiento, las ventanas y el clima local para una instalación real. Ideal para herramientas de HVAC y mejoras del hogar, guías de dimensionamiento de aires acondicionados y calefactores, aplicaciones de hogar inteligente y energía, y cotizaciones para contratistas. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 3 endpoints. Esto es dimensionamiento de HVAC; para el costo de funcionamiento de electrodomésticos, use una API de costo de energía.

Tempo di attività

100.0%

Latenza

75ms

Abbonati

4,645

Pipe-flow maths as an API, computed locally and deterministically. The flow endpoint relates the three quantities of pipe flow — volumetric flow rate, fluid velocity and pipe diameter — through the continuity relation Q = A·v (with A = π/4·D²): give any two and it returns the third, with the flow rate expressed in litres per second and minute, cubic metres per hour, US gallons per minute and cubic feet per minute, plus the velocity and the pipe cross-section. The reynolds endpoint computes the Reynolds number from velocity, diameter and the fluid (water, air, oil and more, or a custom kinematic viscosity) and classifies the flow as laminar, transitional or turbulent. The convert endpoint converts a flow rate between litres per second and minute, cubic metres per hour, US gallons per minute, cubic feet per minute and per second. Everything is computed locally and deterministically, so it is instant and private. It is computed in SI internally; Reynolds uses the kinematic viscosity at about 20°C. Ideal for plumbing and HVAC tools, pump and irrigation sizing, process and fluid-engineering software, and hydraulics calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is fluid flow in pipes; for plain volume or unit conversion use a unit-conversion API.

Tempo di attività

100.0%

Latenza

74ms

Abbonati

4,789

Firewood maths as an API, computed locally and deterministically. The volume endpoint turns a wood-stack's length, height and depth (in feet or metres) into its volume in cubic feet and cubic metres, full cords, face cords and steres — a full cord being 128 cubic feet (a 4×4×8 ft stack) and a face cord being an 8×4 ft stack by the piece (log) length. The convert endpoint converts a quantity between cords, face cords, steres, cubic metres and cubic feet, using the piece length for the face-cord relationship. The heat endpoint estimates the heating value of a number of cords by wood species — returning the millions of BTU and the equivalent gallons of heating oil, therms of natural gas and kilowatt-hours — from a built-in table of typical seasoned-wood values (oak, hickory, maple, ash, birch, pine and more) or a custom figure. Everything is computed locally and deterministically, so it is instant and private. Heat values are typical seasoned figures (around 20% moisture) and vary with species, dryness and stove efficiency. Ideal for firewood sellers and delivery tools, heating and homestead apps, and forestry and woodlot calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is firewood volume and energy; for general volume or unit conversion use a unit-conversion API.

Tempo di attività

100.0%

Latenza

82ms

Abbonati

4,795

Bicycle gearing maths as an API, computed locally and deterministically. The gear endpoint takes a chainring and cog tooth count and a wheel size and returns every common gearing metric: the gear ratio, gear inches (the classic measure — ratio times wheel diameter in inches), the gain ratio (Sheldon Brown's crank-length-aware measure), the development or rollout (metres travelled per crank revolution), and the road speed at a chosen cadence in km/h and mph. The speed endpoint converts between a gear-and-cadence and road speed in either direction — the speed at a cadence, or the cadence needed for a target speed. The table endpoint builds a gear chart: give one or more chainrings and a cassette of cogs and it returns a matrix of gear inches, development, gain ratio or ratio for every combination — ideal for visualising a drivetrain. Wheel size can be a preset (700x25c, 26-inch, 29er and more) or an exact rolling circumference in millimetres, and crank length is configurable for the gain ratio. Everything is computed locally and deterministically, so it is instant and private. Ideal for cycling apps and bike-fit tools, drivetrain and gear-ratio planners, and bike-shop and component sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is bicycle gearing; for cycling power, FTP and training zones use a cycling API.

Tempo di attività

100.0%

Latenza

73ms

Abbonati

4,493

Bolt and fastener torque maths as an API, using the standard short-form relation T = K · D · F — torque equals the nut factor times the bolt diameter times the clamp load (preload). The torque endpoint computes the tightening torque, in newton-metres, foot-pounds, inch-pounds and kilogram-force metres, from the bolt diameter, the target clamp load and a nut factor — given directly or chosen from a condition preset (dry, lubricated, zinc-plated, galvanized, waxed and more). The preload endpoint solves the inverse: the clamp load a given torque produces on a bolt of a given diameter and friction. The convert endpoint converts a torque value between newton-metres, foot-pounds, inch-pounds and kilogram-force metres. Everything is computed locally and deterministically, so it is instant and private. The K·D·F short form is an estimate that depends heavily on friction — it is engineering guidance only, so always follow the manufacturer's torque specification. Ideal for mechanical, automotive and aerospace tools, maker and assembly apps, maintenance and field-service software, and engineering calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is fastener torque; for wire gauge and resistance use a wire-gauge API and for Ohm's law use an electronics API.

Tempo di attività

100.0%

Latenza

76ms

Abbonati

4,977

Unit-price and best-value maths as an API — the supermarket "which is cheaper" calculation, computed locally and deterministically and entirely currency-agnostic. The unit endpoint normalises a pack price to a price per standard unit: from a price, a pack size and its unit (and an optional multipack count) it returns the price per kilogram, per 100 g and per pound for weight; per litre, per 100 ml and per fluid ounce for volume; or per item for counted goods — plus the price per pack item for multipacks. The compare endpoint takes several pack options as a simple list (such as "3@500g,5@1kg,4.5@750g"), ranks them cheapest-per-unit first, names the best value and reports the percentage saving versus the most expensive. The convert endpoint turns a unit price given in one basis (for example per pound) into the other bases for its measure. Everything is computed locally and deterministically, so it is instant and private. Options being compared must share a measure (all weight, all volume or all count). Ideal for shopping and grocery apps, price-comparison and deal sites, budgeting tools, and retail and procurement software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is unit-price comparison; for profit margin and markup use a margin API.

Tempo di attività

100.0%

Latenza

81ms

Abbonati

3,777

Matemáticas de costo de electricidad como una API, calculadas local y determinísticamente y completamente independientes de la moneda. El endpoint de costo calcula el uso de energía y el costo de funcionamiento de un electrodoméstico a partir de su potencia (vatios o kilovatios), las horas de uso por día y una tarifa por kilovatio-hora, devolviendo los kilovatios-hora y el costo por día, semana, mes y año, con una cantidad opcional de dispositivos idénticos. El endpoint de comparación enfrenta dos electrodomésticos: calcula el costo anual de energía de cada uno, el ahorro del más eficiente y, dado el precio de compra adicional del mejor modelo, el período de recuperación en años y meses. El endpoint de conversión relaciona vatios, horas y kilovatios-hora: proporciona dos y devuelve el tercero, más el costo a una tarifa. Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Los kilovatios-hora equivalen a la potencia en kilovatios multiplicada por las horas, y el costo equivale a los kilovatios-hora multiplicados por la tarifa; los meses usan 365/12 días. Ideal para aplicaciones de ahorro de energía y hogar inteligente, comparación de electrodomésticos y herramientas minoristas, paneles de sostenibilidad y software de presupuestos. Cálculo local puro: sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 3 endpoints. Esto son matemáticas de costo de energía; para capacidad de batería y tiempo de funcionamiento, use una API de batería.

Tempo di attività

100.0%

Latenza

76ms

Abbonati

4,490

American Wire Gauge maths as an API, computed locally and deterministically from the AWG definition. The awg endpoint takes a gauge — an integer, or 0/00/000/0000 (1/0–4/0) — and returns the conductor diameter (millimetres, inches, mils), the cross-section area (mm², kcmil and circular mils), the DC resistance per kilometre and per 1000 feet for copper and aluminium, and a typical ampacity. The convert endpoint finds the nearest standard AWG for a given cross-section area, diameter or kcmil, and also reports the exact non-integer gauge. The voltage-drop endpoint computes the round-trip voltage drop and power loss for a wiring run from the gauge (or area), length, current and conductor material, with the percentage drop and the voltage left at the load. Everything is computed locally and deterministically, so it is instant and private. Resistances are at 20°C; ampacity figures are typical guidance only — real installations are governed by the NEC/IEC tables for the conductor, insulation and conditions. Ideal for electrical and electronics tools, maker and hobby projects, solar and automotive wiring, and AV and installation planning. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is wire-gauge physics; for Ohm's-law voltage/current/resistance use an electronics API and for resistor colour bands use a resistor API.

Tempo di attività

100.0%

Latenza

80ms

Abbonati

3,499

Pizza and bread dough maths as an API, built on baker's percentages — where the flour is always 100% and every other ingredient is expressed as a percentage of the flour weight. The dough endpoint computes a full recipe in grams (flour, water, salt, yeast, oil and sugar) from a target quantity — either a number of dough balls and a ball weight, a total dough weight, or a flour weight — together with a hydration and salt/yeast percentages, or a built-in style preset (Neapolitan, New York, Detroit, Sicilian, focaccia, ciabatta, baguette, sandwich). The hydration endpoint converts between flour, water and hydration percentage and classifies the dough from stiff to extremely wet. The presets endpoint returns the common dough styles as baker's percentages with typical ball weights. Everything is computed locally and deterministically, so it is instant and private. The yeast figure is instant dry yeast (use roughly three times as much fresh). Ideal for recipe and baking apps, pizzeria and bakery tools, meal-planning and kitchen-scale integrations, and food blogs. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is dough formulation by baker's percentage; for ingredient volume-to-weight and oven-temperature conversion use a cooking API.

Tempo di attività

100.0%

Latenza

84ms

Abbonati

3,002

Lighting design maths as an API, computed locally and deterministically. The room endpoint works out how many lumens a room needs from its area and a target illuminance — given directly in lux or chosen from a room-type preset (living, kitchen, office, workshop and more) — and, optionally, how many fixtures at a given lumen output and how many watts at a given lamp type. The lux endpoint converts between lux, footcandles and lumens over an area, so you can find the illuminance from a light output and a room size or vice versa. The efficacy endpoint relates lumens, watts and luminous efficacy (lumens per watt): give any two — or a lamp-type preset such as incandescent, halogen, CFL or LED — and it computes the third. Everything is computed locally and deterministically, so it is instant and private. It is a lumen-method estimate: target levels are typical guidance (EN 12464 / IES) and a full design would add room and utilisation factors. Ideal for lighting and electrical tools, interior-design and home apps, retrofit and energy-saving calculators, and smart-home planning. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is illumination maths; for Ohm's-law electrical quantities use an electronics API.

Tempo di attività

100.0%

Latenza

79ms

Abbonati

4,612

Roofing geometry as an API, computed locally and deterministically. The pitch endpoint converts a roof pitch between every common form — rise-over-run (such as 6:12), the angle in degrees, the percent slope, and the slope multiplier (the factor that turns a flat footprint into the real sloped area). The rafter endpoint computes the rafter length from the horizontal run and the pitch — that is, the hypotenuse √(run² + rise²) — with an optional overhang projected along the slope. The area endpoint computes the true sloped roof area from the building footprint (entered directly or as length × width) and the pitch, adds a wastage allowance, and reports the number of US roofing squares and shingle bundles needed. Everything is computed locally and deterministically, so it is instant and private. Lengths are unit-agnostic — use consistent units — while the squares and bundles figures assume US roofing squares of 100 square feet, so pass the footprint in square feet for those. Ideal for roofing contractors and estimators, construction and DIY tools, solar-install planning, and quoting software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is roof geometry; for paint, tile, concrete and brick quantities use a construction-calculator API.

Tempo di attività

100.0%

Latenza

79ms

Abbonati

4,431

Screen and display pixel-density maths as an API, computed locally and deterministically. The ppi endpoint computes the pixels per inch of a display from its resolution and diagonal size — along with the pixels per centimetre, the dot pitch in millimetres, the diagonal in pixels, the total pixels and megapixels, the simplified aspect ratio, and the physical width and height. The size endpoint does the inverse: from a resolution and a known PPI it works out the physical dimensions and diagonal in inches and centimetres. The retina endpoint analyses a display at a viewing distance: it computes the pixels per degree, says whether the display is effectively "retina" (pixels indistinguishable to 20/20 vision, around 60 pixels per degree), and gives the distance at which it becomes retina. Everything is computed locally and deterministically, so it is instant and private. Ideal for display and monitor tools, AV and signage planning, UI and responsive-design work, and hardware comparison sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is screen pixel density; for print resolution and image-to-print sizing use a DPI API.

Tempo di attività

100.0%

Latenza

83ms

Abbonati

3,799

Matemática de faixas de imposto progressivo (marginal) como uma API. Você fornece a tabela de faixas, então funciona para qualquer país, ano ou tabela de imposto e nunca fica desatualizado, e é totalmente independente de moeda. O endpoint de imposto recebe uma renda e uma tabela de pares limite:taxa (com uma dedução padrão opcional) e retorna o imposto total, a renda após o imposto, as taxas efetiva e marginal, e um detalhamento por faixa mostrando exatamente quanto é tributado em cada nível. O endpoint reverso resolve o problema inverso — a renda bruta necessária para receber um valor líquido alvo na mesma tabela — por bissecção. O endpoint de faixas valida e normaliza uma tabela em níveis rotulados (adicionando um nível de 0% a partir de zero e marcando a faixa superior aberta). Tudo é calculado localmente e deterministicamente, então é instantâneo e privado. Ele modela apenas a tabela que você fornece — inclua quaisquer abatimentos, créditos ou sobretaxas nas faixas ou na dedução você mesmo — e não é aconselhamento fiscal. Ideal para ferramentas de folha de pagamento e RH, calculadoras de salário e oferta, aplicativos fintech e de orçamento, e qualquer produto que mostre o salário líquido. Cálculo local puro — sem chave, sem serviço de terceiros, instantâneo. Ao vivo, nada armazenado. 3 endpoints. Esta é a matemática de imposto progressivo em uma tabela que você fornece; para conversão de período de salário bruto, use uma API de folha de pagamento e para empréstimos e juros, use uma API de calculadora financeira.

Tempo di attività

100.0%

Latenza

80ms

Abbonati

4,769

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.

Tempo di attività

100.0%

Latenza

79ms

Abbonati

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.

Tempo di attività

100.0%

Latenza

74ms

Abbonati

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.

Tempo di attività

100.0%

Latenza

78ms

Abbonati

4,862