API Marketplace

Matemática de Gerenciamento de Valor Agregado (EVM) como uma API, calculada local e deterministicamente — os controles de custo e cronograma de projetos usados em PMP, PRINCE2 e contratação governamental. O endpoint de métricas recebe o orçamento na conclusão (BAC), valor planejado (PV), valor agregado (EV) e custo real (AC) — ou um percentual concluído e percentual planejado do BAC — e retorna a variação de custo (CV = EV−AC), variação de cronograma (SV = EV−PV), os índices de desempenho de custo e cronograma (CPI = EV/AC, SPI = EV/PV), o percentual concluído e gasto, e uma leitura em linguagem simples de acima/abaixo do orçamento e adiantado/atrasado no cronograma. O endpoint de previsão projeta o término: a estimativa na conclusão por três métodos padrão (BAC/CPI quando a tendência de custo continua, AC + orçamento restante, e o custo e cronograma AC + (BAC−EV)/(CPI·SPI)), a estimativa para concluir (ETC), a variação na conclusão (VAC) e o índice de desempenho para concluir (TCPI) para atingir o orçamento original ou o EAC. Um CPI de 0,875 em um orçamento de 1000 prevê um estouro de 1143. Tudo é calculado local e deterministicamente, portanto é instantâneo e privado. Ideal para desenvolvedores de aplicativos de gerenciamento de projetos, PMO, construção, aeroespacial e contratação, painéis de projetos e ferramentas de relatórios de valor agregado, e treinamento PMP/PRINCE2. Cálculo local puro — sem chave, sem serviço de terceiros, instantâneo. Ao vivo, nada armazenado. 2 endpoints de computação. Este é o controle de projetos de valor agregado; para matemática de fluxo de caixa de empréstimos ou VPL, use uma API financeira.

Tempo di attività

100.0%

Latenza

82ms

Abbonati

4,782

Six Sigma和質量工程數學作為API，在本地確定性地計算——質量計劃背後的過程能力和缺陷數學。能力端點接受過程均值、標準差以及上規格限和/或下規格限，返回Cp = (USL−LSL)/6σ和Cpk = min((USL−μ)/3σ, (μ−LSL)/3σ)，以及Cpu、Cpl和來自正態尾部的預期DPMO和良率——中心化Cpk為1.33是經典的過程能力目標。dpmo端點將缺陷數、單位數和機會數（或良率）轉換為每百萬機會缺陷數、良率和過程西格瑪水平，使用傳統的1.5σ長期偏移——著名的六西格瑪3.4 DPMO，以及3000 DPMO對應約4.25西格瑪。yield端點將每步良率滾動為滾動通過良率Π(良率ᵢ)——單位無缺陷通過每一步的概率——以及標準化良率和每單位總缺陷數，也可以從DPU開始。正態尾部來自精確的erfc，西格瑪水平來自精確的反向正態。所有計算都在本地確定性地進行，因此即時且私密。非常適合質量工程、製造、精益六西格瑪和過程改進應用開發者、SPC和能力研究工具，以及綠帶/黑帶培訓。純本地計算——無需密鑰、無第三方服務、即時。實時，不存儲任何內容。3個計算端點。這是能力和DPMO數學；對於一般描述性統計，請使用統計API。

Tempo di attività

100.0%

Latenza

72ms

Abbonati

4,281

Reliability-engineering maths as an API, computed locally and deterministically — the availability, MTBF and failure maths behind SLAs and dependable systems. The availability endpoint converts between MTBF and MTTR, a target availability and the SLA "nines": give it a mean time between failures and a mean time to repair and it returns the availability A = MTBF/(MTBF+MTTR) and the downtime per year, month, week and day; give it a number of nines and it returns the budget — three nines (99.9 %) is 8.76 hours of downtime a year, five nines (99.999 %) just 5.26 minutes. The reliability endpoint computes the probability a unit survives a mission time under the exponential model R(t) = e^(−λt) with its constant hazard λ = 1/MTBF, or the Weibull model R(t) = e^(−(t/η)^β) — β below one for infant mortality, one for random failures, above one for wear-out — returning the reliability, failure probability, hazard rate and the mean life η·Γ(1+1/β). The system endpoint combines component reliabilities into a system: series (the weakest link, ΠRᵢ), parallel redundancy (1−Π(1−Rᵢ)) or k-of-n voting. Everything is computed locally and deterministically, so it is instant and private. Ideal for SRE, DevOps, hardware-reliability, safety-engineering and SLA-planning app developers, uptime-budget and redundancy-design tools, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. This is reliability and availability maths; for queue wait-times use a queueing API and for live uptime checks use a monitoring service.

Tempo di attività

100.0%

Latenza

78ms

Abbonati

4,656

Scuba-diving and gas-planning maths as an API, computed locally and deterministically. The nitrox endpoint takes an oxygen fraction and returns the maximum operating depth (MOD) for a ppO2 limit (1.4 working, 1.6 contingency), and, for a given depth, the oxygen partial pressure, the equivalent air depth (EAD), whether the mix is within its limit and the best mix for that depth — EAN32 has a MOD of 33.75 m at 1.4 and an EAD of 24.4 m at 30 m. The gas endpoint plans breathing gas from a surface air consumption (SAC/RMV) rate: it scales consumption to depth (consumption = SAC × (1 + depth/10)), gives the litres a planned dive needs and the cylinder duration on the available gas down to a reserve, and can derive your SAC from a logged dive's pressure drop, cylinder size and time. The pressure endpoint gives the ambient pressure and the partial pressure of every gas at depth, plus the equivalent narcotic depth (END) for any blend including trimix — helium is non-narcotic, so it cuts narcosis. Metric throughout: depth in metres of sea water, where 10 m ≈ 1 bar. Everything is computed locally and deterministically, so it is instant and private. Ideal for dive-planning, dive-log, freediving and scuba-training app developers, nitrox and trimix calculators, and dive-education tools. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. This is dive-planning maths, not a decompression-model NDL — always cross-check with tables or a dive computer.

Tempo di attività

100.0%

Latenza

80ms

Abbonati

4,595

Casino game maths as an API, computed locally and deterministically — exact house edge, expected value and return-to-player, never a simulation. The roulette endpoint takes a wheel variant (European single-zero or American double-zero) and a bet type (straight, split, street, corner, six-line, column, dozen, red/black, odd/even, high/low, or the American basket) and returns the win probability, the payout, the expected value per unit staked and the house edge — the famous 2.70 % on every European bet, 5.26 % on American (7.89 % on the basket), and 1.35 % when the European la-partage rule is applied to even-money bets. The craps endpoint gives the exact 36-outcome dice maths for the pass line (1.41 %), don't pass (1.36 %, with its 12-push), the field (2.78 % when 12 pays 3:1) and any seven (16.67 %). The bet endpoint is fully generic: give any win probability and payout and it returns the expected value, house edge, return-to-player and the standard deviation of a unit bet — perfect for keno, slots, scratch cards or a custom wager. Everything is computed locally and deterministically, so it is instant and private. Ideal for gaming-analytics, responsible-gambling, casino-education and odds-comparison app developers, advantage-play and bankroll tools, and probability teaching. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. This is the game-odds maths; for Texas Hold'em hand equity use a poker API and for converting betting prices use an odds API.

Tempo di attività

100.0%

Latenza

75ms

Abbonati

3,692

Baseball sabermetrics as an API, computed locally and deterministically — turn raw counting numbers into the rate stats that actually rank players. The batting endpoint takes at-bats, hits, doubles, triples, home runs, walks, hit-by-pitch and sacrifice flies and returns the batting average (H/AB), on-base percentage ((H+BB+HBP)/(AB+BB+HBP+SF)), slugging percentage (total bases/AB), OPS (on-base plus slugging), isolated power (SLG−AVG) and, when strikeouts are supplied, BABIP — a classic .300/.366/.530 line comes straight out. The pitching endpoint takes innings pitched, earned runs, hits, walks, strikeouts and home runs and returns the earned run average (9·ER/IP), WHIP ((BB+H)/IP), strikeouts and walks per nine innings, the strikeout-to-walk ratio and FIP, the fielding-independent pitching estimator (13·HR + 3·(BB+HBP) − 2·K)/IP + constant. Innings pitched is a true decimal, with an exact "outs" input for the 6.1/6.2 box-score convention. Everything is computed locally and deterministically, so it is instant and private. Ideal for fantasy-baseball, sports-analytics, sabermetrics and box-score app developers, scouting and stat-line tools, and teaching material. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 compute endpoints. This computes the stats from your numbers; for live scores, standings, teams and players use a sports-data API.

Tempo di attività

100.0%

Latenza

77ms

Abbonati

4,180

Real-estate investment maths as an API, computed locally and deterministically — the property-analysis layer a loan calculator leaves out. The cap-rate endpoint gives the net operating income and capitalization rate of a rental from its price, gross rent, vacancy allowance and operating expenses (NOI = gross rent × (1 − vacancy) − expenses; cap rate = NOI / price), plus the gross rent multiplier — the unlevered view a buyer compares deals on. The cash-flow endpoint adds financing: from a down payment (amount or percent), interest rate and term it amortizes the mortgage, then returns the monthly payment, annual debt service, the property cash flow, the cash-on-cash return (annual cash flow ÷ cash invested), the debt-service-coverage ratio (DSCR = NOI ÷ debt service, the figure lenders underwrite to) and the loan-to-value. The metrics endpoint runs the quick screening ratios investors filter on — the 1 % rule (monthly rent ≥ 1 % of price), gross rental yield, gross rent multiplier and price per square foot. Money in, ratios out, in one consistent currency. Everything is computed locally and deterministically, so it is instant and private. Ideal for proptech, real-estate-investment, rental-analysis and landlord app developers, deal-screening and underwriting tools, and personal-finance dashboards. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. This is property-investment analysis; for pure loan amortization use a loan API and for DCF/NPV use an investment-appraisal API.

Tempo di attività

100.0%

Latenza

73ms

Abbonati

4,266

Collatz 猜想（"3n+1" 或冰雹问题）作为一个 API，在本地确定性地计算。给它任意正整数，序列端点返回完整的冰雹路径——每一步，偶数减半，奇数乘以 3 加 1（3n+1）——以及总停止时间（到达 1 所需的步数）和序列达到的峰值。从 6 开始，路径为 6, 3, 10, 5, 16, 8, 4, 2, 1——八步，峰值为 16；著名的长起始数 27 需要 111 步，峰值高达 9232 然后下降。steps 端点仅返回停止时间和峰值高度，不返回整个路径，用于快速批量扫描大攀升和长尾的位置。所有算术运算使用任意精度整数，因此即使小起始数膨胀到数百万，峰值也保持精确，并且安全上限确保每个请求有界。接受高达一百万亿的起始数。所有计算在本地确定性地进行，因此即时且私密。非常适合数学教育、数论、娱乐数学和谜题应用开发者、序列和冰雹可视化工具，以及关于算术中最著名未解决问题教学材料。纯本地计算——无需密钥，无需第三方服务，即时。实时，不存储任何内容。2 个计算端点。这是专门的 Collatz/3n+1 序列；对于质因数分解或 GCD，请使用数论 API。

Tempo di attività

100.0%

Latenza

75ms

Abbonati

4,833

Birthday-paradox and collision-probability maths as an API, computed locally and deterministically. The probability endpoint computes the chance that at least two of n people share a birthday among d equally likely days, P = 1 − Π(1 − i/d), evaluated in log space for accuracy — the famous result that just 23 people give about a 50.7 % chance, 50 people about 97 % and 70 people about 99.9 %. The people-needed endpoint inverts it: the smallest group size to reach a target probability (23 for 50 %, 57 for 99 %), with the √(2·d·ln(1/(1−p))) approximation. The collision endpoint generalises the birthday bound to any space — pass a number of buckets or a hash size in bits — and returns the collision probability P ≈ 1 − e^(−n²/2d), the rule behind hash collisions and UUID-uniqueness estimates, where a 50 % chance needs roughly 1.177·√d items. Days and buckets default to 365. Everything is computed locally and deterministically, so it is instant and private. Ideal for probability-education, security, cryptography, hashing, data-engineering and statistics app developers, collision-risk and birthday-problem tools, and teaching material. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is the birthday/collision probability; for full distributions use a probability API.

Tempo di attività

100.0%

Latenza

80ms

Abbonati

4,858

Advanced 3D-solid geometry as an API, computed locally and deterministically — the shapes a basic geometry calculator leaves out. The cone-frustum endpoint gives the volume V = (π·h/3)·(R² + R·r + r²), the slant height √(h² + (R−r)²) and the lateral and total surface area of a truncated cone, the shape of buckets, lampshades and hoppers. The torus endpoint gives a doughnut’s volume 2π²·R·r² and surface area 4π²·R·r from its centre-to-tube and tube radii. The ellipsoid endpoint gives the exact volume (4/3)π·a·b·c and a Knud-Thomsen surface-area approximation accurate to better than 1.1 %. The platonic endpoint returns the volume and surface area of any of the five Platonic solids — tetrahedron, cube, octahedron, dodecahedron and icosahedron — from the edge length, using the exact golden-ratio coefficients (a unit icosahedron has volume 2.1817 and surface area 8.6603). Use a consistent length unit and get area and volume out. Everything is computed locally and deterministically, so it is instant and private. Ideal for engineering, CAD, 3D-modelling, architecture, manufacturing and maths-education app developers, volume-and-area and packaging tools, and simulation software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. These are the advanced solids; for sphere, cube, cylinder, cone and 2D shapes use a general geometry API.

Tempo di attività

100.0%

Latenza

80ms

Abbonati

3,185

Music-theory maths as an API, computed locally and deterministically over the twelve-tone chromatic scale. The interval endpoint gives the number of semitones and the interval name between two notes — C to G is seven semitones, a perfect fifth. The transpose endpoint shifts one or more notes up or down by a number of semitones, so C E G transposed up seven becomes G B D and a negative value transposes down. The chord endpoint returns the notes of a chord from a root and a type — major, minor, diminished, augmented, the sevenths (major7, minor7, dominant7, diminished7, half-diminished7), sixths, suspended, add9, ninth and power chords — so C major is C E G and C7 is C E G B♭. The scale endpoint returns the notes of a scale from a root and a mode — the major and three minor scales, the seven church modes, the major and minor pentatonics, blues, whole-tone and chromatic — so C major is C D E F G A B and A natural-minor is A B C D E F G. Notes use C, C#, D♭ … B, and accidental=flat spells with flats. Everything is computed locally and deterministically, so it is instant and private. Ideal for music-education, ear-training, songwriting, DAW-plugin, notation and instrument app developers, chord-and-scale tools, and practice software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is pitch-class theory; for the actual frequency of a note use a music-note API.

Tempo di attività

100.0%

Latenza

83ms

Abbonati

4,147

Phonetic and fuzzy string-matching maths as an API, computed locally and deterministically. The soundex endpoint computes the American Soundex code of a word — the first letter followed by three digits that encode its consonant sounds, ignoring case and non-letters and applying the vowel-reset and adjacent-duplicate rules — so Robert and Rupert both code to R163, Smith and Smyth to S530, and the classic tricky cases Ashcraft (A261), Tymczak (T522) and Pfister (P236) come out right. The levenshtein endpoint computes the edit distance between two strings (the minimum insertions, deletions and substitutions, optionally case-sensitive) and a 0–100 % similarity, so kitten → sitting is three edits and about 57 % similar. The compare endpoint combines both: it reports whether two strings share a Soundex code (sound alike) and their Levenshtein similarity (spelled alike), and flags a likely match when the codes agree or the similarity is at least 80 %. Everything is computed locally and deterministically, so it is instant and private. Ideal for data-deduplication, CRM, fuzzy-search, autocomplete, genealogy and data-cleaning app developers, name-matching and record-linkage tools, and search software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is phonetic and edit-distance matching; for full-text search use a search API.

Tempo di attività

100.0%

Latenza

76ms

Abbonati

4,783

Validação do formato do número de identificação de IVA da UE como uma API, calculada localmente e deterministicamente. O endpoint validate recebe um número de IVA, remove espaços, pontos e hífens, lê o prefixo de duas letras do país e verifica o restante do corpo em relação à estrutura oficial do estado-membro — os nove dígitos da Alemanha, o U-mais-oito da Áustria, os nove dígitos-B-dois dos Países Baixos, o prefixo de dois caracteres mais nove dígitos da França, os onze dígitos da Itália, e assim por diante para todos os 27 países da UE mais a Irlanda do Norte (XI), usando corretamente EL para a Grécia em vez de GR. Retorna se o formato é válido, o país e o padrão esperado, de modo que DE123456789 e ATU12345678 passam, enquanto um número alemão com apenas oito dígitos ou um prefixo dos EUA é rejeitado. O endpoint format consulta o padrão de IVA esperado para qualquer código de país ou lista todos os suportados. Esta é uma verificação de estrutura offline — um formato válido não prova que o número está registrado, para o qual é necessária uma consulta VIES ao vivo. Tudo é calculado localmente e deterministicamente, portanto é instantâneo e privado. Ideal para desenvolvedores de aplicativos de comércio eletrônico, faturamento, contabilidade, checkout B2B e conformidade fiscal, ferramentas de validação e integração de campos de IVA e software financeiro. Computação local pura — sem chave, sem serviço de terceiros, instantâneo. Ao vivo, nada armazenado. 2 endpoints. Isto valida o formato do número de IVA; para taxas de IVA, use uma API de IVA/impostos.

Tempo di attività

100.0%

Latenza

77ms

Abbonati

3,731

US bank ABA routing-number (routing transit number) validation as an API, computed locally and deterministically. The validate endpoint checks a nine-digit routing number with the official ABA checksum — 3·(d1+d4+d7) + 7·(d2+d5+d8) + (d3+d6+d9) must be a multiple of ten — ignoring hyphens and spaces, and reads the first two digits as the Federal Reserve routing symbol to name the district (01–12 are the twelve Federal Reserve Banks from Boston to San Francisco, 21–32 are thrift institutions); JPMorgan Chase’s 021000021 validates and resolves to the Federal Reserve Bank of New York, and a number with a wrong check digit is rejected. The checkdigit endpoint computes the ninth check digit from the first eight so the whole number passes. It also returns the institution identifier (digits 5–8) and the check digit. Everything is computed locally and deterministically, so it is instant and private. Ideal for fintech, banking, ACH, payroll, payment and accounting app developers, bank-account-form validation and onboarding tools, and US payment software. This is the checksum and routing-symbol structure only — it does not confirm a live bank. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 endpoints. For SWIFT/BIC codes use a BIC API and for IBANs an IBAN API.

Tempo di attività

100.0%

Latenza

71ms

Abbonati

3,929

Validação e análise de código de identificação empresarial SWIFT/BIC como uma API, calculada local e deterministicamente. O endpoint validate verifica se um código segue a estrutura BIC ISO 9362 — quatro letras para a instituição, um código de país ISO de duas letras, um código de localização de dois caracteres e um código de filial opcional de três caracteres, totalizando oito ou onze caracteres — ignorando espaços e convertendo a entrada para maiúsculas, e confirma que o código do país é reconhecido; DEUTDEFF (Deutsche Bank, Frankfurt) é um BIC de sede válido de oito caracteres e DEUTDEFF500 é um BIC de filial válido de onze caracteres. O endpoint parse divide um BIC em seus componentes de instituição, país, localização e filial, informa se é uma sede ou filial (filial XXX ou nenhum significa a sede) e lê o status a partir do segundo caractere do código de localização — 0 para um código de teste/não SWIFT, 1 para um participante passivo e 2 para faturamento reverso. Um BIC não possui soma de verificação, portanto esta é uma validação estrutural. Tudo é calculado local e deterministicamente, sendo instantâneo e privado. Ideal para desenvolvedores de aplicativos fintech, bancários, de pagamento, KYC, tesouraria e contabilidade, ferramentas de código SWIFT e identificador bancário, e fluxos de integração. Cálculo local puro — sem chave, sem serviço de terceiros, instantâneo. Ao vivo, nada armazenado. 2 endpoints. Isto valida e analisa um BIC; para validação de número de conta IBAN, use uma API IBAN.

Tempo di attività

100.0%

Latenza

79ms

Abbonati

3,614

ISBN validation and conversion as an API, computed locally and deterministically. The validate endpoint detects whether a code is an ISBN-10 or an ISBN-13, ignores hyphens and spaces, and verifies the check digit — ISBN-10 with the mod-11 scheme whose last character may be the letter X (for 10), and ISBN-13 with the weighted 1-3-1-3 mod-10 scheme — so 0-306-40615-2 and 978-0-306-40615-7 both validate while a wrong check digit is rejected. The checkdigit endpoint computes the trailing check digit for a 9-digit ISBN-10 stem or a 12-digit ISBN-13 stem (and recomputes it for a full code). The convert endpoint converts between the two forms: an ISBN-10 becomes an ISBN-13 by prefixing 978 and recomputing the check, and a 978-prefixed ISBN-13 converts back to ISBN-10 (979-prefixed codes have no ISBN-10 equivalent). Everything is computed locally and deterministically, so it is instant and private. Ideal for publishing, library, bookstore, catalogue, e-commerce and metadata app developers, ISBN-validation and barcode tools, and inventory systems. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is ISBN-specific validation and conversion; for generic Luhn/Verhoeff check digits use a check-digit API.

Tempo di attività

100.0%

Latenza

74ms

Abbonati

3,609

UTM ↔ geographic coordinate conversion as an API, computed locally and deterministically on the WGS84 ellipsoid. The from-latlon endpoint projects a latitude and longitude into the Universal Transverse Mercator grid — returning the zone (1–60), the hemisphere, the latitude band letter, and the easting and northing in metres — using the Snyder/USGS Transverse Mercator series, which is accurate to a few millimetres within a zone; New York (40.7128, −74.0060) maps to zone 18N at about 583960 E, 4507351 N, and the canonical 45°N on a central meridian gives a northing of exactly 4982950.40 m. The to-latlon endpoint inverts it, recovering the latitude and longitude from a zone, hemisphere, easting and northing. Each zone is 6° of longitude wide with a 500000 m false easting on its central meridian and a 10000000 m false northing in the southern hemisphere. Latitude is valid from −80° to 84°. Everything is computed locally and deterministically, so it is instant and private. Ideal for GIS, surveying, mapping, geospatial, drone-mapping and location app developers, coordinate-conversion and grid-reference tools, and spatial software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 endpoints. This is UTM on WGS84; for the polar regions use UPS and for an EPSG-code lookup use an EPSG API.

Tempo di attività

100.0%

Latenza

77ms

Abbonati

3,487

Conversão do alfabeto fonético da OTAN como uma API, computada localmente e deterministicamente. O endpoint spell transforma qualquer texto no alfabeto de ortografia radiotelefônica internacional usado pela aviação, militares, serviços de emergência e centrais de atendimento — letras tornam-se Alfa, Bravo, Charlie e assim por diante (sem distinção entre maiúsculas e minúsculas), dígitos usam as formas ICAO (Niner para nove), espaços são marcados e caracteres desconhecidos passam — então SOS torna-se “Sierra Oscar Sierra” e ABC123 torna-se “Alfa Bravo Charlie One Two Three”. O endpoint decode reverte o processo, transformando uma string de palavras fonéticas de volta nos caracteres originais e aceitando variantes ortográficas comuns (Alpha ou Alfa, X-ray ou Xray, Juliet ou Juliett, Nine ou Niner), sinalizando quaisquer palavras que não reconhece. Tudo é computado localmente e deterministicamente, portanto é instantâneo e privado. Ideal para desenvolvedores de aviação, rádio, telecom, centrais de atendimento, suporte ao cliente, acessibilidade e aplicativos de voz, ferramentas de soletração e leitura, e sistemas IVR. Computação puramente local — sem chave, sem serviço de terceiros, instantâneo. Ao vivo, nada armazenado. 2 endpoints. Este é o alfabeto de ortografia da OTAN/ICAO; para código Morse, use uma API Morse.

Tempo di attività

100.0%

Latenza

73ms

Abbonati

4,924

Matemática de DNA-oligo e PCR-primer como uma API, computada local e deterministicamente. O endpoint tm calcula a temperatura de fusão de uma sequência de primer de três maneiras: a regra de Wallace 2·(A+T) + 4·(G+C) para oligos curtos de até 13 nt, a fórmula GC de Marmur–Wallace 64.9 + 41·(nGC − 16.4)/N para sequências mais longas, e a ajustada por sal 81.5 + 0.41·%GC − 675/N + 16.6·log10[Na+] para uma dada concentração de sódio, e recomenda o método correto para o comprimento — um ATGCATGC de oito bases derrete a 24 °C por Wallace, um primer de 20 bases com 50% GC a cerca de 51.8 °C por Marmur. O endpoint gc-content relata as porcentagens de GC e AT, as contagens por base e o peso molecular de fita simples. O endpoint reverse-complement retorna o complemento, o reverso e o complemento reverso de uma fita. As sequências usam A/C/G/T (insensível a maiúsculas/minúsculas, espaços em branco ignorados) e [Na+] está em mol/L. Tudo é computado local e deterministicamente, então é instantâneo e privado. Ideal para desenvolvedores de aplicativos de biologia molecular, biotecnologia, PCR, design de primers, bioinformática e automação de laboratório, calculadoras de oligo e primer, e software LIMS. Fórmulas de estimativa para design de primers, não um substituto para a termodinâmica de vizinhos mais próximos. Computação puramente local — sem chave, sem serviço de terceiros, instantâneo. Ao vivo, nada armazenado. 3 endpoints. Esta é a temperatura de fusão de oligo; para frequências alélicas de genética populacional, use uma API de genética.

Tempo di attività

100.0%

Latenza

77ms

Abbonati

3,544

Population-dynamics maths as an API, computed locally and deterministically. The exponential endpoint applies the Malthusian model N(t) = N0·e^(r·t) — unbounded growth at a constant continuous rate r — and returns the projected population, the growth factor and the doubling time; a population of 100 growing at r = 0.05 per period reaches about 165 after ten periods. The logistic endpoint applies the bounded model N(t) = K/(1 + ((K−N0)/N0)·e^(−r·t)), where growth slows as the population approaches the carrying capacity K and is fastest at the inflection point N = K/2; starting from 10 toward a capacity of 1000 at r = 0.5, the population is about 600 after ten periods and levels off near 1000. The doubling-time endpoint gives ln2/r for a continuous rate, or the Rule-of-70 quick estimate for a percentage growth per period. The rate and time share one period (years, days, generations). Everything is computed locally and deterministically, so it is instant and private. Ideal for biology, ecology, demography, conservation, education and simulation app developers, population-projection and carrying-capacity tools, and modelling software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is population growth; for disease spread use an epidemiology API and for population-genetics allele frequencies a genetics API.

Tempo di attività

100.0%

Latenza

77ms

Abbonati

3,733

Epidemiology-basics maths as an API, computed locally and deterministically. The herd-immunity endpoint computes the herd-immunity threshold HIT = 1 − 1/R0 — the immune fraction of a population at which an outbreak can no longer sustain itself — from the basic reproduction number R0, and adjusts for an imperfect vaccine by dividing by its efficacy, so a disease with R0 = 3 needs about 67 % immune (74 % vaccinated with a 90 %-effective vaccine) while measles at R0 ≈ 15 needs about 93 %. The r-effective endpoint computes the effective reproduction number Re = R0 · susceptible fraction and flags whether the epidemic is growing (Re > 1) or shrinking. The final-size endpoint solves the final-epidemic-size equation Z = 1 − e^(−R0·Z) for the eventual attack rate of an unmitigated SIR epidemic — about 80 % at R0 = 2. The doubling-time endpoint gives the case-doubling time from a growth rate, or from R0 and the serial interval. Fractions are 0–1 and percentages are derived. Everything is computed locally and deterministically, so it is instant and private. Ideal for public-health, epidemiology-education, dashboard, science-communication and outbreak-planning app developers, herd-immunity and reproduction-number tools, and health software. Simple compartmental relations for education and planning, not a substitute for full epidemiological modelling. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is epidemiology basics; for population-genetics Hardy-Weinberg use a genetics API.

Tempo di attività

100.0%

Latenza

74ms

Abbonati

3,980

Matemáticas de componentes de viento en pista de aviación como una API, calculadas local y determinísticamente. El endpoint de componentes descompone el viento superficial en las dos partes que importan a los pilotos para el despegue y aterrizaje: el componente de viento cruzado perpendicular a la pista, viento·sin(θ), y el componente de viento de frente (o de cola) a lo largo de ella, viento·cos(θ), donde θ es el ángulo entre la dirección del viento y el rumbo de la pista — proporcione la pista como un rumbo o un designador del 01 al 36, más la dirección y velocidad del viento, y devuelve el viento cruzado con el lado desde el que sopla (izquierda o derecha), el viento de frente o de cola, y el ángulo de desviación; viento 30° fuera del morro a 20 nudos es un viento cruzado de 10 nudos y un viento de frente de 17,3 nudos. El endpoint de viento máximo lo invierte: la mayor velocidad total del viento antes de que se exceda un límite de viento cruzado dado en un ángulo de viento, límite / |sin θ|. Las direcciones están en grados (el viento es de DONDE VIENE) y la unidad de velocidad es la que usted proporcione (nudos, m/s). Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Ideal para desarrolladores de aplicaciones de aviación, pilotos, entrenamiento de vuelo, bolsa de vuelo electrónica, drones y aplicaciones de información meteorológica, herramientas de selección de pista y límite de viento cruzado, y software de cabina. Cálculo puramente local — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 2 endpoints. Esto es geometría de viento en pista; para la velocidad del sonido y el número Mach use una API de Mach y para la densidad de la atmósfera estándar una API de atmósfera estándar.

Tempo di attività

100.0%

Latenza

81ms

Abbonati

4,067

Design-proportion maths as an API, computed locally and deterministically. The divide endpoint splits a length by the golden section, the division beloved of artists and designers in which the whole is to the longer part as the longer is to the shorter, both ratios equal to φ = (1+√5)/2 ≈ 1.618 — so 100 splits into a 61.8 longer segment and a 38.2 shorter one — and can also extend a single segment to its larger or smaller golden partner. The rectangle endpoint gives the other side and the area of a golden rectangle from either side, the shape that leaves a smaller golden rectangle when you remove a square. The scale endpoint builds a modular (typographic) scale — base · ratio^step across a range of steps up and down — for harmonious type sizes and spacing, taking a numeric ratio or a named musical one such as minor-third (1.2), major-third (1.25), perfect-fourth (1.333) or golden (φ); a 16-base major-third scale gives 16, 20, 25, 31.25 and so on. Lengths are unit-agnostic. Everything is computed locally and deterministically, so it is instant and private. Ideal for graphic-design, web-design, UI, typography, layout and architecture app developers, type-scale and proportion tools, and design systems. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is proportion and scale; for pixel-density and print sizing use a PPI/DPI API.

Tempo di attività

100.0%

Latenza

80ms

Abbonati

4,978

Cut-list maths for woodworking and material cutting as an API, computed locally and deterministically. The cuts endpoint computes how many pieces of a target length come from one stock length once the saw kerf — the width of material each cut removes — is accounted for, using pieces = floor((stock + kerf)/(piece + kerf)) since the final cut leaves no kerf, and returns the used length, the leftover offcut, the waste percentage and the total kerf loss; a 2400 mm board cut into 300 mm pieces with a 3 mm kerf yields 7 pieces with a 282 mm offcut, not the 8 you would expect ignoring the blade. The boards endpoint works out how many stock lengths a job of a given quantity needs and how many spare pieces are left over. The yield endpoint reports the overall material efficiency — total piece length divided by total stock length — for a whole cutting job. All lengths share one consistent unit (mm, cm or inches). Everything is computed locally and deterministically, so it is instant and private. Ideal for woodworking, carpentry, metal-fabrication, contractor, maker and shop-software developers, cut-list and offcut calculators, and material-ordering tools. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is single-length (1D) cut optimisation; for loose-material volume use a mulch/volume API.

Tempo di attività

100.0%

Latenza

79ms

Abbonati

4,044