API · /catering-api

Catering & Party API

salutare 4,088 Abbonati

Catering- und Partyplanungs-Mathematik als API, lokal und deterministisch berechnet – die Wie-viel-kaufe-ich-Zahlen, mit denen ein Gastgeber oder Caterer eine Personenzahl plant. Der Food-Endpunkt skaliert ein Menü auf die Gästeanzahl und den Appetit: das Hauptprotein mit etwa einem halben Pfund gegartem Fleisch pro Person (leicht 0,33, herzhaft 0,75), jede Beilage mit etwa vier Unzen pro Kopf, sechs Appetizer-Stücke pro Person und eineinhalb Dinner-Brötchen – also benötigen 50 Gäste bei einem Standard-Dinner mit drei Beilagen 25 Pfund Fleisch, 300 Appetizer und 75 Brötchen. Der Drinks-Endpunkt dimensioniert die Bar: etwa ein Getränk pro Gast pro Stunde plus ein Extra in der ersten Stunde, aufgeteilt auf Bier, Wein und Cocktails und umgerechnet in die realen Einheiten, die man kauft – Bier im Kasten (24) und im Fass (~165 Portionen), Wein in der Flasche (~5 Gläser), Spirituosen in der 750-ml-Flasche (~16 Shots) – plus das Eis (etwa 1,5 Pfund pro Gast) und Wasser; eine Party mit 50 Gästen und vier Stunden kommt auf 250 Getränke, 125 Biere (0,76 eines Fasses), 15 Flaschen Wein und 75 Pfund Eis. Alles wird lokal und deterministisch berechnet, also ist es sofortig und privat. Ideal für Eventplanungs-, Catering-, Hospitality- und Party-App-Entwickler, Einkaufslisten- und Personenzahl-Tools sowie Gastgeber-Rechner. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofortig. US-Einheiten; Faustregeln – aufrunden. Live, nichts wird gespeichert. 2 Compute-Endpunkte. Anpassung an die Menge und die Jahreszeit.

api.oanor.com/catering-api
Ottieni una chiave API Prova nel parco giochi → Contatta provider

Specifica leggibile dalle macchine, così gli agenti AI possono integrare questa API.

/api/catering-api/openapi.json
/api/catering-api/llms.txt

Individuazione: GET /api/index.json elenca ogni API.

API salute

salutare
Tempo di attività
100.00%
Sondaggi del server · 24 ore su 24
Latenza media
66 ms
Sondaggi del server · 24 ore su 24
Abbonati
4,088
attiva
Chiamate totali
0
ultimi 7 giorni

Prezzi

Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.

Free

Gratis

  • 6,850 chiamate/mese
  • 2 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 6.850 Aufrufe/Monat
  • 2 req/sec
  • Mengenangaben für Lebensmittel und Getränke
  • Keine Kreditkarte
Accedi per abbonarti

Starter

€3.85 /mese

  • 60,500 chiamate/mese
  • 6 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 60.500 Aufrufe/Monat
  • 6 req/sec
  • Fässer, Weinflaschen, Eis, Appetite
  • E-Mail-Support
Accedi per abbonarti

Pro

€10.80 /mese

  • 247,500 chiamate/mese
  • 15 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 247.500 Aufrufe/Monat
  • 15 req/sec
  • Event- und Einkaufslisten-Pipelines
  • Priority-Support
Accedi per abbonarti

Mega

€34.50 /mese

  • 1,385,000 chiamate/mese
  • 40 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 1.385.000 Aufrufe/Monat
  • 40 req/sec
  • Plattform-Skalierung
  • Dedizierte SLA
Accedi per abbonarti

Costruito da

Correlato APIs

Altro APIs con tag sovrapposti.

Food Cost API

Restaurant food-costing maths as an API, computed locally and deterministically — the menu-engineering and cost-control numbers a kitchen runs on. The recipe endpoint totals a dish from its ingredient line costs (or quantities × unit prices), divides by the yield factor (1 − waste %) so trim and shrinkage raise the true cost, and splits it across the portions to a cost per plate — and against a menu price it returns the food-cost percentage and gross profit. The plate endpoint prices a dish both ways: give a menu price and get the food-cost percentage and markup factor, or give a target food-cost percentage and get the suggested menu price (a 30 % target is a 3.33× markup), plus gross profit, gross margin and, with a labour cost, the prime-cost percentage. The period endpoint turns inventory movement into the cost of goods sold — COGS = opening inventory + purchases − closing inventory — and the food or pour cost percentage against sales, the headline number on every P&L (28–35 % for food, 18–24 % for beverage). Everything is computed locally and deterministically, so it is instant and private. Ideal for restaurant-tech, POS, kitchen-management, catering and hospitality app developers, menu-engineering and recipe-costing tools, and culinary-school training. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. This is food-cost and menu-pricing maths; for unit conversion use a cooking API and for generic margin maths a pricing API.

api.oanor.com/foodcost-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

Draft Beer API

Draft-Beer-Dispenser-Mathematik als API, lokal und deterministisch berechnet – die CO₂-Druck- und Bierleitungszahlen, nach denen ein Hobbybrauer, Kegerator-Besitzer oder eine Bar einen Zapfhahn einstellt. (Dies ist die Ausschankseite; für ABV, Stammwürze und IBU handelt es sich um eine Hobbybrau-Berechnung.) Der Carbonierungs-Endpunkt liefert den Regler-Vordruck, der eine Zielcarbonierung bei Ausschanktemperatur hält, basierend auf der Standard-Volumen-Temperatur-Druck-Regression: 2,5 Volumen CO₂ bei 38 °F benötigen etwa 11 psi, und kälteres Bier hält die gleiche Carbonierung bei niedrigerem Druck – britische Ales liegen bei etwa 1,5–2,0 Volumen, US-Ales bei 2,2–2,7, Lager und Weizen höher. Der Balance-Endpunkt dimensioniert die Bierleitung, sodass das System einen sauberen Kopf ausschenkt, statt zu schäumen oder langsam zu laufen: Leitungslänge = (angelegter Druck − 0,5 × Steigung − Restdruck) ÷ Widerstand der Leitung pro Fuß, wobei die Schwerkraft etwa 0,5 psi pro Fuß Höhenunterschied hinzufügt und etwa 1 psi am Hahn verbleibt – also 12 psi ohne Steigung bei 3/16-Zoll-Vinyl (≈3 psi/ft) ergeben etwa 3,7 Fuß, während schmalere oder breitere Schläuche alles ändern. Alles wird lokal und deterministisch berechnet, daher ist es sofortig und privat. Ideal für Hobbybrau-, Kegerator-, Bar-, Brauerei-Ausschank- und Getränke-App-Entwickler, Zapfanlagen- und Fehlerbehebungstools sowie Gastronomie-Software. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofortig. Nur Ausschankseite. Live, nichts gespeichert. 2 Compute-Endpunkte.

api.oanor.com/draftbeer-api

Knife Sharpening API

Knife-sharpening maths as an API, computed locally and deterministically — the bevel and angle numbers a sharpener, cook or knifemaker sets a stone to. It uses the symmetric V-edge model: the bevel endpoint takes the blade thickness and a per-side (or inclusive) angle and returns the bevel face width = (thickness ÷ 2) ÷ sin(per-side angle), with the inclusive angle as twice the per-side — so a 2 mm blade ground at 15° per side has a 3.86 mm bevel and a 30° edge, and at a 40° inclusive (20° per side) a 2.92 mm bevel. The angle endpoint runs it in reverse for the marker (Sharpie) method: colour the edge, take one stroke, measure the shiny bevel, and per-side angle = asin((thickness ÷ 2) ÷ bevel width) tells you the angle you are actually holding. The recommend endpoint gives sensible inclusive-angle ranges by use — about 12–17° for razors, 20–30° for Japanese kitchen knives, 30–40° for Western chef’s and EDC, 40–50° for outdoor and hard use, 45–65° for axes — and converts any chosen inclusive angle to per-side and back. Everything is computed locally and deterministically, so it is instant and private. Ideal for knife, kitchen, EDC, bushcraft, woodworking and sharpening app developers, sharpening-jig and edge-geometry tools, and maker software. Pure local computation — no key, no third-party service, instant. Symmetric V-edge model, mm and degrees. Live, nothing stored. 3 compute endpoints.

api.oanor.com/knifesharp-api

Domande frequenti

Risposte rapide su prezzi, quote e integrazione.

Come ottengo una chiave API per Catering & Party API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Catering & Party API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Catering & Party 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 Catering & Party API?
Catering & Party API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €3.85 / 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.
Catering & Party API è conforme al GDPR?
Tutte le richieste a Catering & Party 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/catering-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/catering-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/catering-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/catering-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.

Accedi

Nuova discussione

/ 4000

📌 Fissato 🔒 Bloccato

·

· ·

/ 4000

🔒 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.

Accedi

Apri nuovo ticket

Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.

  • Nessun ticket per questa API.

Abbonamento attivo: le chiamate possono iniziare subito.

Invia la tua prima richiesta —

Abbonamento attivo: copia uno snippet e avvia la tua prima chiamata.