Blended carbon-to-nitrogen ratio
API · /compost-api
Composting API
salutare
4,953 Abbonati
Kompostierungsmathematik als API, lokal und deterministisch berechnet – die drei Zahlen, die entscheiden, ob ein Haufen heiß wird und sich zersetzt oder kalt und stinkend dasteht. Der cn-ratio-Endpunkt mischt eine Mischung zu ihrem Kohlenstoff-Stickstoff-Verhältnis: Übergeben Sie jedes Material nach Gewicht mit seinem Trockengewichts-%C und %N als parallele kommagetrennte Listen, und er gibt die gesamten Kohlenstoff- und Stickstoffmassen sowie das gemischte C:N zurück, mit einer Bewertung gegenüber dem idealen 25–35:1 – zehn Teile trockene Blätter (50 %C, 1 %N) mit zehn Teilen Grasschnitt (45 %C, 2,5 %N) ergeben ein nahezu perfektes 27:1. Der Moisture-Endpunkt berechnet die Wassermenge, die hinzugefügt werden muss, um eine Ziel-Feuchtigkeit zu erreichen (der Haufen sollte ein ausgewrungener Schwamm von 50–60 % sein): Aus der aktuellen Masse und Feuchtigkeit hält er die Trockenmasse konstant, also benötigen 100 kg bei 30 % etwa 56 kg Wasser, um 55 % zu erreichen, und er kennzeichnet einen zu nassen Haufen, der stattdessen getrocknet werden muss. Der Mix-Endpunkt gibt das Braun:Grün-Gewichtsverhältnis an, um ein Ziel-C:N aus den %C und %N zweier Materialien zu erreichen – Blätter und Gras bei einem Ziel von 30:1 benötigen etwa 1,5 Teile Braunes zu 1 Teil Grünem. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für Garten- und Kompostierungs-Apps, Meisterkompostierer- und Schrebergarten-Tools, regenerative Landwirtschaft und Bodengesundheits-Websites sowie Abfallvermeidungsrechner. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Live, nichts gespeichert. 3 Compute-Endpunkte. Für Materialvolumen verwenden Sie eine Mulch-API; für NPK-Ausbringungsmengen verwenden Sie eine Dünger-API.
api.oanor.com/compost-api
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 96 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,953
- attiva
- Chiamate totali
- 4
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 450 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 450 Aufrufe/Monat
- 2 req/sec
- C:N + Feuchtigkeit + Mischung
- Keine Kreditkarte
Starter
€5.05 /mese
- 12,500 chiamate/mese
- 6 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 12.500 Aufrufe/Monat
- 6 req/sec
- Mehrstoffmischungen
- E-Mail-Support
Pro
€16.60 /mese
- 80,000 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 80.000 Aufrufe/Monat
- 15 req/sec
- Garden-app Pipelines
- Priority-Support
Mega
€49.90 /mese
- 260,000 chiamate/mese
- 36 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 260.000 Aufrufe/Monat
- 36 req/sec
- Plattform-Skalierung
- Dedizierte SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Irrigation Design API
Irrigation-design maths as an API, computed locally and deterministically — the sprinkler numbers a landscaper, irrigation tech or gardener sizes a system with. The precip-rate endpoint gives the precipitation rate in inches per hour from the flow and spacing: PR = 96.25 × GPM per head ÷ the area each head waters (head spacing × row spacing in feet), where 96.25 is the in/hr one gallon-per-minute makes over a square foot — three-GPM heads on a 15 × 15 ft grid lay down about 1.28 in/hr. The runtime endpoint turns a target water depth into a run-time: depth ÷ precipitation rate, divided by the system efficiency because no system is perfectly even, so applying a half-inch at 1.28 in/hr takes about 23 minutes at full efficiency, longer with real-world uniformity. The zone endpoint sizes a valve zone: maximum heads = available flow ÷ each head's GPM, rounded down so you never starve the line — 13 GPM drives five 2.6-GPM heads with nothing to spare. Everything is computed locally and deterministically, so it is instant and private. Ideal for irrigation and landscaping apps, sprinkler-design and contractor tools, smart-controller schedulers, and garden-planning sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For evapotranspiration or weather use a weather API; for material volume use a mulch API.
api.oanor.com/irrigation-api
Plant Spacing API
Plant-spacing and planting-density maths as an API, computed locally and deterministically. The grid endpoint works out how many plants fill an area in a square (rectangular) layout: from a spacing (one value, or separate row and in-row spacings) and either an area or a length and width, it returns the planting density per square metre, square foot, 1,000 ft², acre and hectare, an area-based plant estimate, and — when you give length and width — an exact edge-inclusive grid count with the number of rows and plants per row. The triangular endpoint does the same for an offset (hexagonal) layout, where rows sit spacing × √3/2 apart and fit about 15.47 % more plants than a square grid at the same spacing, and it reports the gain. The density endpoint converts a spacing into a planting density in several units, or works in reverse: give a number of plants and an area and it recommends the spacing that fills it. Lengths accept millimetres, centimetres, metres, inches or feet; area accepts m², ft², acres or hectares. Everything is computed locally and deterministically, so it is instant and private. Ideal for gardening and landscaping apps, agriculture and horticulture tools, nursery and farm planners, and reforestation calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is planting layout and density; for fertilizer application rates use a fertilizer API and for mulch, soil and gravel quantities use a landscaping API.
api.oanor.com/plantspacing-api
Fertilizer Calculator API
Fertilizer maths as an API, computed locally and deterministically. The rate endpoint works out how much fertilizer product to apply to hit a target nitrogen rate over an area: from the N-P-K analysis (such as 10-10-10 or 20-5-10), a target pounds of nitrogen per 1000 ft² (or per 100 m²) and the area, it returns the product weight and the pounds of nitrogen, phosphate and potash applied. The nutrients endpoint reports the pounds of nitrogen, P₂O₅ and K₂O — and the elemental phosphorus and potassium — in a bag of a given weight and analysis. The coverage endpoint works out how much area a bag covers at a target nitrogen rate. N-P-K are percent by weight; phosphorus is reported as P₂O₅ and potassium as K₂O following the label convention, with the elemental amounts alongside (P₂O₅ × 0.4364, K₂O × 0.8301). Everything is computed locally and deterministically, so it is instant and private. Ideal for lawn-care and gardening apps, agriculture and turf tools, and landscaping and quoting software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is fertilizer rate maths; for mulch, gravel and topsoil quantities use a landscaping API.
api.oanor.com/fertilizer-api
Landscaping Material API
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.
api.oanor.com/landscape-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Composting API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Composting API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Composting API?
Il piano gratuito consente 1 richiesta al secondo. I piani a pagamento arrivano fino a 50 richieste al secondo nel piano Mega. I limiti rigorosi restituiscono HTTP 429 oltre la quota — nessuna spesa imprevista.
Quanto costa Composting API?
Composting API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €5.05 / mese con quote più alte e limiti di velocità più rapidi.
Posso cancellare l'abbonamento in qualsiasi momento?
Sì. I piani sono fatturati mensilmente e puoi cancellare in qualsiasi momento dalla dashboard di fatturazione. Nessun contratto a lungo termine e nessuna penale di cancellazione.
Composting API è conforme al GDPR?
Tutte le richieste a Composting API passano attraverso il nostro gateway in UE. La tua chiave upstream non lascia mai il nostro server e nessun dato personale viene condiviso con il fornitore upstream oltre alla richiesta inviata.
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/compost-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/compost-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/compost-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/compost-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
📌 Fissato
🔒 Bloccato
·
·
·
-
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.