Launching in New York
Any assistant can find and reserve a table at a Tadka restaurant through one open protocol: MCP, REST, llms.txt and OpenAPI.
OAuth sign-in as the diner. Search, availability, booking, cancel, waitlist.
Open read-only directory and restaurant detail. CORS enabled.
Plain-text directory any model can read at crawl time.
Machine-readable spec for function-calling agents.
The problem
Reservation sites block automated traffic, so agents fall back to brittle scraping.
A sanctioned, documented interface built for agents to call.
Most restaurants have no public endpoint an assistant can transact against.
Restaurants go live in two minutes and become bookable by every agent.
Agents acting in parallel collide on the same table.
Every reservation is checked and written in one transaction against live capacity.
A table booked by an agent never reaches the host stand.
Signed webhooks push every booking; inbound sync holds seats taken elsewhere.
Quickstart
Settings → Connectors → Add custom connector, paste the address, sign in and approve.
https://tadka.xyz/mcpRead the open directory without authentication.
curl "https://tadka.xyz/api/public/v1/restaurants?city=New%20York"For restaurants
No setup fee, no monthly charge, no commission during launch.
Add your details, seating times and covers. Self-serve.
Partner dashboard with live refresh, or straight into your POS.