Brine salt for water
API · /fermentation-api
Vegetable Fermentation API
Vegetable lacto-fermentation maths as an API, computed locally and deterministically — the salt numbers a fermenter weighs sauerkraut, kimchi and pickles by. (Vegetables, not meat — for cure and nitrite that is a separate calculation.) Salt is the whole game: too little and the wrong microbes win, too much and the ferment stalls. The salt endpoint does the dry-salt method for shredded veg, salt = vegetable weight × percent, with about 2 % being the classic sauerkraut and kimchi target — so a kilo of cabbage takes 20 grams — and it bands the result from low-and-fast to a near salt-cure. The brine endpoint sizes a submerged ferment, salt = water weight × percent where the percent is of the water as recipes state it (1 ml water ≈ 1 g), so a litre at 5 % needs 50 grams for a standard sour pickle, 3.5 % for a milder one; it also reports the salinity as a percent of the total solution. The salinity endpoint converts the two ways the same brine is expressed — percent of water versus percent of total — so a 5 %-of-water brine reads about 4.76 % on a refractometer. Everything is computed locally and deterministically, so it is instant and private. Ideal for fermentation, homesteading, recipe and food app developers, ferment-calculator and batch tools, and culinary software. Pure local computation — no key, no third-party service, instant. Grams and ml. Live, nothing stored. 3 compute endpoints.
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 80 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 3,771
- attiva
- Chiamate totali
- 0
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 6,920 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 6.920 Aufrufe/Monat
- 2 req/sec
- Trockensalz + Sole + Salzgehalt
- Keine Kreditkarte
Starter
€4.21 /mese
- 56,400 chiamate/mese
- 6 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 56.400 Aufrufe/Monat
- 6 req/sec
- Prozentbänder, % Wasser vs. Gesamt
- E-Mail-Support
Pro
€11.66 /mese
- 231,200 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 231.200 Aufrufe/Monat
- 15 req/sec
- Ferment-calculator & Batch-Pipelines
- Priority-Support
Mega
€36.78 /mese
- 1,347,000 chiamate/mese
- 40 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1.347.000 Aufrufe/Monat
- 40 req/sec
- Plattform-Skalierung
- Dedizierte SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Egg Incubation API
Egg-incubation maths as an API, computed locally and deterministically — the hatch timeline, conditions and brooder numbers a hatchery or backyard chicken-keeper raises a clutch by. The hatch endpoint turns the set day (day 0) into the schedule by species: it knows the incubation period — chicken 21 days, duck 28, quail 17, goose 30, turkey 28, Muscovy 35 and more — and gives the lockdown day, about three days before hatch, when you stop turning the eggs, raise the humidity and leave the lid shut; pass a custom incubation_days for anything else. The conditions endpoint gives the targets: a forced-air incubator at 99.5 °F (still-air a degree or two higher at the top of the eggs), with humidity around 45–55 % through incubation and 65–75 % at lockdown so the membrane stays soft. The brooder endpoint schedules the chicks after they hatch — 95 °F under the lamp in week one, dropping 5 °F a week until they reach room temperature around 70 °F and are feathered enough to leave it. Everything is computed locally and deterministically, so it is instant and private. Ideal for poultry, hatchery, homesteading and farm app developers, incubation-timer and brooder tools, and 4-H / education software. Pure local computation — no key, no third-party service, instant. Guidance — candle the eggs and watch the chicks. Live, nothing stored. 3 compute endpoints.
api.oanor.com/incubation-api
Chicken Coop API
Backyard-chicken housing maths as an API, computed locally and deterministically — the coop, run and fixture numbers a flock keeper builds to. The space endpoint sizes the housing from the flock and the breed: about 4 ft² of coop floor per standard hen (2 for bantams, 5 for heavy breeds) plus roughly 10 ft² of run each, so ten standard hens want a 40 ft² coop and a 100 ft² run — and given a coop width it returns the length, or zero run for birds that free-range and only roost inside. The fixtures endpoint covers the inside: one nest box per three to four hens (they share and queue, so ten hens need three), 8–12 inches of roost bar per bird (ten birds ≈ 8.3 feet), about 4 inches of linear feeder space each, and a waterer per eight or so birds. Crowding is the root of pecking, disease and mess, so every figure rounds up and more space is always better; roosts should sit higher than the nest boxes so the birds don’t sleep — and soil — in them. Everything is computed locally and deterministically, so it is instant and private. Ideal for homesteading, backyard-poultry, farm and smallholding app developers, coop-planner and flock-management tools, and self-sufficiency software. Pure local computation — no key, no third-party service, instant. US units, rules of thumb. Live, nothing stored. 2 compute endpoints. For feed quantities use a different API.
api.oanor.com/chickencoop-api
Home Canning API
Home-canning maths as an API, computed locally and deterministically — the altitude adjustments that keep a batch of preserves safe, the numbers a canner, homesteader or recipe app processes a jar by. Because water boils cooler the higher you are, every tested sea-level recipe has to run longer or hotter, and this API does that arithmetic. The waterbath endpoint applies the USDA boiling-water-bath and steam-canner rule: for a base process of 20 minutes or less add 5, 10, 15 or 20 minutes by altitude band, and for more than 20 minutes add 10, 20, 30 or 40 — so a 15-minute pickle recipe at 4,000 feet processes 25 minutes, and a 30-minute one runs 50. The pressure endpoint adjusts the canner: a dial gauge gains 1 psi per 2,000 feet, turning an 11 psi recipe into 12, 13, 14 or 15, while a weighted gauge simply steps from 10 psi up to 1,000 feet to 15 above it, since it only has 5/10/15 settings. The boilingpoint endpoint gives the underlying reason — water boils about 1.84 °F lower per 1,000 feet, so 5,000 feet boils at 202.8 °F instead of 212. Everything is computed locally and deterministically, so it is instant and private. Ideal for canning, food-preservation, homesteading, recipe and kitchen app developers, preserving-calculator and pantry tools, and cooking-class software. Pure local computation — no key, no third-party service, instant. USDA tables — always follow a tested recipe. Live, nothing stored. 3 compute endpoints.
api.oanor.com/canning-api
Grain Bin API
Grain-Bin-Speichermathematik als API, lokal und deterministisch berechnet – die Scheffel- und Gewichtszahlen, mit denen ein Landwirt oder Elevator die Lagerkapazität bemisst. Der Bushels-Endpunkt misst ein rundes Silo: Grundfläche × Korntiefe ergibt Kubikfuß, und ein Kubikfuß fasst etwa 0,8036 Scheffel, sodass ein 18-Fuß-Silo, das 20 Fuß gefüllt ist, etwa 4.090 Scheffel fasst – und Getreide, das zu einem Kegel aufgehäuft ist, addiert einen Kegel von (1/3) × Grundfläche × Spitzenhöhe, sodass eine 4-Fuß-Spitze etwa 270 weitere Scheffel hinzufügt. Der Weight-Endpunkt wandelt Scheffel in Gewicht um, basierend auf dem Standard-Testgewicht der Ernte – Mais und Sorghum bei 56 Pfund pro Scheffel, Weizen und Sojabohnen 60, Hafer 32, Gerste 48 – also wiegen diese 4.090 Scheffel Mais 229.040 Pfund, etwa 114,5 US-Tonnen oder 104 Tonnen; übergeben Sie ein gemessenes Testgewicht für leichtes oder schweres Getreide. Alles wird lokal und deterministisch berechnet, daher ist es sofortig und privat. Ideal für Entwickler von Apps für Landwirtschaft, Getreideheber, Farmmanagement und Agrartechnologie, für Speicherkapazitäts- und Inventar-Tools sowie Erntesoftware. Reine lokale Berechnung – kein API-Key, kein Drittanbieterdienst, sofortig. US-Einheiten (Fuß, Scheffel, Pfund). Live, nichts wird gespeichert. 2 Compute-Endpunkte.
api.oanor.com/grainbin-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Vegetable Fermentation API?
Qual è il limite di velocità di Vegetable Fermentation API?
Quanto costa Vegetable Fermentation API?
Posso cancellare l'abbonamento in qualsiasi momento?
Vegetable Fermentation 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/fermentation-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/fermentation-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/fermentation-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/fermentation-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.