Espresso ratio
API · /coffee-api
Coffee Brewing API
Coffee brewing maths as an API, computed locally and deterministically. The ratio endpoint works out a brew recipe from any two of the coffee dose, the water and the brew ratio — water = coffee × ratio — and reports the third value, the ratio as 1:N, the number of cups and whether the recipe sits around the SCA "golden ratio" of about 1:16–1:17. The espresso endpoint does the same for espresso from any two of the dose, the yield and the brew ratio (yield = dose × brew ratio), labelling the shot ristretto, normale or lungo. The extraction endpoint computes the extraction yield, EY% = (beverage mass × TDS%) ÷ dose, from the dose, the brewed beverage mass (or the water, estimating the mass the grounds retain) and the measured total dissolved solids, then classifies the brew as under-extracted, ideal or over-extracted and weak through very strong against the SCA brewing control chart. Masses are in grams, water in grams or millilitres. Everything is computed locally and deterministically, so it is instant and private. Ideal for specialty-coffee, café, brewing-scale and recipe app developers, pour-over and espresso tools, and barista training. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is coffee brewing maths; for cooking-unit conversions use a cooking API and for caffeine intake use a caffeine API.
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 88 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,853
- attiva
- Chiamate totali
- 32
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 3,000 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 25,435 calls/month
- 2 req/sec
- Ratio + espresso + extraction
- No credit card
Starter
€4.00 /mese
- 40,000 chiamate/mese
- 5 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 36.75k calls/month
- 8 req/sec
- Golden ratio, brew control chart
- Email support
Pro
€11.00 /mese
- 250,000 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 401.5k calls/month
- 20 req/sec
- Café & recipe-app pipelines
- Priority support
Mega
€35.00 /mese
- 1,500,000 chiamate/mese
- 40 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 2.05M calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Coffee Roasting API
Coffee-roasting maths as an API, computed locally and deterministically — the roast-profile numbers a home or specialty roaster tracks batch to batch. The loss endpoint works the weight-loss relationship from any two of the green weight, the roasted weight and the loss percentage: weight loss % = (green − roasted) / green × 100, so 1 kg of green dropping to 840 g is a 16 % loss, a 15 % target leaves 850 g, and to bag 800 g of roasted you charge 952 g of green (roasted ÷ (1 − loss%)). Light roasts shed about 12–14 %, medium 15–17 %, dark 18–20 %. The development endpoint computes the development time and the Development Time Ratio (DTR) from the total roast time and the first-crack time — DTR = (total − first crack) / total × 100, with most roasters aiming for roughly 20–25 %; times accepted as seconds or mm:ss. Everything is computed locally and deterministically, so it is instant and private. Ideal for coffee-roasting, roastery, specialty-coffee and roast-logging app developers, profile and batch tools, and roasting education. Pure local computation — no key, no third-party service, instant. Weights in grams, times in seconds or mm:ss. Live, nothing stored. 2 compute endpoints. This is roast-profile maths; for brewing ratios use a coffee-brewing API.
api.oanor.com/coffeeroast-api
API de Calculadora de Cafeína
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.
api.oanor.com/caffeine-api
Homebrewing API
Homebrewing maths as an API, computed locally and deterministically. The abv endpoint computes the alcohol by volume from the original and final gravity — both the simple (OG − FG)·131.25 estimate and a more accurate high-gravity formula — along with the apparent and real attenuation and the calories per 12 oz serving. The gravity endpoint converts freely between specific gravity, degrees Plato and Brix (the three ways brewers and winemakers measure dissolved sugar) and reports the gravity points. The ibu endpoint computes hop bitterness in International Bitterness Units by the Tinseth formula from the hop alpha-acid percentage, the weight, the boil time, the batch volume and the wort gravity, returning the utilization and the alpha-acid concentration too. Gravities are specific gravity such as 1.050, hop weight in grams, boil time in minutes and volume in litres. Everything is computed locally and deterministically, so it is instant and private. Ideal for homebrew, craft-beer, cidery and winemaking app developers, recipe and batch tools, and brewing education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is brewing maths; for a brewery directory use a beer API and for coffee brew ratios a coffee API.
api.oanor.com/brewing-api
OCR API
Extraiga texto de imágenes mediante reconocimiento óptico de caracteres en ocho idiomas (inglés, alemán, francés, español, italiano, portugués, neerlandés y turco). Obtenga el texto completo reconocido con una puntuación de confianza promedio y recuentos de palabras y líneas, o resultados a nivel de palabra donde cada palabra lleva su propia confianza y cuadro delimitador para un procesamiento consciente del diseño. Proporcione una imagen mediante URL pública, base64 o un cuerpo de solicitud binario sin procesar; las imágenes grandes se reducen automáticamente antes del reconocimiento para mantener las respuestas rápidas, y un motor cálido mantiene baja la latencia después del inicio. Cálculo puro del lado del servidor (Tesseract, sin terceros ascendentes, sin costo de nube por llamada). Ideal para digitalizar documentos y recibos, leer texto de fotos y capturas de pantalla, accesibilidad y automatización de entrada de datos.
api.oanor.com/ocr-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Coffee Brewing API?
Qual è il limite di velocità di Coffee Brewing API?
Quanto costa Coffee Brewing API?
Posso cancellare l'abbonamento in qualsiasi momento?
Coffee Brewing API è conforme al GDPR?
Scegli un endpoint dall'elenco a sinistra per visualizzarne i dettagli e provarlo.
Frammenti di codice
Iscriviti per ottenere una chiave API, quindi chiama qualsiasi percorso sotto il tuo slug.
curl https://api.oanor.com/coffee-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/coffee-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/coffee-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/coffee-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Valutazioni
Accedi per votare.
Nessuna recensione ancora.
Discussione
Fai domande, condividi consigli, ricevi risposte dal provider e dagli altri sviluppatori. Pubblico — chiunque può leggere.
Accedi per scrivere o rispondere.
AccediNuova discussione
·
-
Risposta del provider
🔒 Discussione bloccata — non si può più rispondere.
-
·
- Nessuna discussione — inizia tu.
Supporto
Supporto privato 1:1 con il provider — fatturazione, integrazione, account. Solo tu e il team del provider vedete questi thread.
Accedi per aprire un ticket di supporto.
AccediApri nuovo ticket
Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.
-
·
Urgente - Nessun ticket per questa API.