oanor
Sign up free
Marketplace Pricing Features Sign in

API · /catering-api

Catering & Party API

healthy 4,088 Subscribers

Catering and party-planning maths as an API, computed locally and deterministically — the how-much-do-I-buy numbers a host or caterer plans a headcount with. The food endpoint scales a menu to the guest count and appetite: the main protein at about half a pound of cooked meat per person (light 0.33, hearty 0.75), each side dish at roughly four ounces a head, six appetizer pieces each and one-and-a-half dinner rolls — so 50 guests at a standard dinner with three sides need 25 lb of meat, 300 appetizers and 75 rolls. The drinks endpoint sizes the bar: about one drink per guest per hour plus an extra in the first hour, split across beer, wine and cocktails, and converted into the real units you buy — beer by the case (24) and the half-keg (~165 servings), wine by the bottle (~5 glasses), spirits by the 750 ml bottle (~16 shots) — plus the ice (about 1.5 lb per guest) and water; a 50-guest, four-hour party comes to 250 drinks, 125 beers (0.76 of a keg), 15 bottles of wine and 75 lb of ice. Everything is computed locally and deterministically, so it is instant and private. Ideal for event-planning, catering, hospitality and party app developers, shopping-list and headcount tools, and host calculators. Pure local computation — no key, no third-party service, instant. US units; rules of thumb — round up. Live, nothing stored. 2 compute endpoints. Adjust for the crowd and the season.

#catering #party-planning #event #headcount #hospitality #developer-tools
api.oanor.com/catering-api
Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

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

Discovery: GET /api/index.json lists every API.

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
66 ms
Server probes · 24h
Subscribers
4,088
active
Total calls
0
last 7 days
status Full status page → · 4 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 6,850 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 6,850 calls/month
  • 2 req/sec
  • Food + drink quantities
  • No credit card
Sign in to subscribe

Starter

€3.85 /month

  • 60,500 calls / month
  • 6 requests / second
  • Hard cap (429 above quota, no overage)
  • 60,500 calls/month
  • 6 req/sec
  • Kegs, wine bottles, ice, appetites
  • Email support
Sign in to subscribe

Pro

€10.80 /month

  • 247,500 calls / month
  • 15 requests / second
  • Hard cap (429 above quota, no overage)
  • 247,500 calls/month
  • 15 req/sec
  • Event & shopping-list pipelines
  • Priority support
Sign in to subscribe

Mega

€34.50 /month

  • 1,385,000 calls / month
  • 40 requests / second
  • Hard cap (429 above quota, no overage)
  • 1,385,000 calls/month
  • 40 req/sec
  • Platform scale
  • Dedicated SLA
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

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 dispense maths as an API, computed locally and deterministically — the CO₂ pressure and beer-line numbers a homebrewer, kegerator owner or bar sets a tap by. (This is the serving side; for ABV, gravity and IBU that is a homebrewing calculation.) The carbonation endpoint gives the regulator head pressure that holds a target carbonation at the serving temperature, from the standard volumes-temperature-pressure regression: 2.5 volumes of CO₂ at 38 °F needs about 11 psi, and colder beer holds the same carbonation at a lower pressure — British ales sit around 1.5–2.0 volumes, US ales 2.2–2.7, lagers and wheats higher. The balance endpoint sizes the beer line so the system pours a clean head instead of foaming or pouring slow: line length = (applied pressure − 0.5 × rise − residual) ÷ the line’s resistance per foot, where gravity adds about 0.5 psi per foot of lift and roughly 1 psi is left at the faucet — so 12 psi with no rise on 3/16-inch vinyl (≈3 psi/ft) wants about 3.7 feet, while narrower or wider tubing changes everything. Everything is computed locally and deterministically, so it is instant and private. Ideal for homebrew, kegerator, bar, brewery-taproom and beverage app developers, draft-system and troubleshooting tools, and hospitality software. Pure local computation — no key, no third-party service, instant. Dispense side only. Live, nothing stored. 2 compute endpoints.

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

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Catering & Party API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Catering & Party API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Catering & Party API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Catering & Party API cost?
Catering & Party API has a free tier with 100 calls / month. Paid plans start at €3.85 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Catering & Party API GDPR-compliant?
All requests to Catering & Party API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Pick an endpoint from the list on the left to see its details and try it.

Code snippets

Sign up to get an API key, then call any path under your 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())

Ratings

Sign in to rate.

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

Sign in to start a thread or reply.

Sign in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

🔒 This thread is locked — no new replies.

  • No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Sign in to open a support ticket.

Sign in

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

  • No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.