Resengo (now Zenchef) — can an agent use it?
Resengo's brand migration to Zenchef leaves agents in limbo: the legacy API is frozen, the successor API documentation is gated behind email requests, and there is no agent protocol surface at all. A restaurant booking platform that an agent cannot programmatically book through without a manual partnership agreement scores poorly on Act & transact.
FIND & RETRIEVE · 2.8
ACT & TRANSACT · 2.3
TRUST & DURABILITY · 4.5
FIND & RETRIEVE2.8/10Can an agent get correct information?
Machine-readable surface3/10
resengo.com redirects to a Zenchef app-download landing page with only 147 words in raw HTML — heavily JS-dependent. No sitemap, no robots.txt, no llms.txt, no RSS or JSON feeds. The Zenchef site has JSON-LD Offer markup and basic semantic HTML (H1, nav) but no markdown negotiation, no content feeds, and no machine-readable surface beyond minimal schema.org. The redirect itself means the canonical domain an agent would try first serves almost nothing parseable. source
Information retrieval quality3.5/10
No pricing page on resengo.com (404). Zenchef's /plans page lists three tiers (Reserve, Manage, Grow) but does not publish base subscription prices — only variable payment fees (credit card 2-6%, SMS costs). A diner-facing agent looking for restaurant availability, hours, or menu information would find nothing on the public surface; that data lives inside restaurant accounts. The redirect landing page is a download prompt, not an information surface. source
Documentation for machines2/10
The legacy Resengo Partner API documentation (resengo-api.developer.azure-api.net) exists but is closed to new partners. The successor Zenchef API documentation is not publicly available — restaurants must email help@zenchef.com to request it, and it requires a Grow subscription or special agreement. The Formitable REST API docs (formitable.com/en/developers/rest/) are public and document 9 endpoint categories with webhooks, API key auth, and versioning (v1.0-v1.2), but their relationship to the Resengo-branded service is unclear to an agent discovering the platform. No OpenAPI spec, no changelog published, and no public error taxonomy. source
ACT & TRANSACT2.3/10Can an agent do the job?
Action coverage4/10
The Formitable/Zenchef REST API covers core reservation actions: create/update/cancel bookings, query availability, access guest profiles, manage orders and reviews. Webhooks notify on booking lifecycle events. This is reasonable coverage of the core restaurant-booking workflow. However, the legacy Resengo API is frozen to new partners, and the Zenchef API requires a special agreement. The gap between what the API can do in principle and what a new agent can access in practice is substantial. source
Agent protocol support0.5/10
No MCP server (official or community), no WebMCP, no Agent Skills, no .well-known/mcp.json, no API catalog. Zenchef's 35 GitHub repos contain no agent protocol implementations. The MCP registry has no Zenchef or Resengo entry. The only programmatic discovery path is the Formitable REST docs, which predate agent protocols entirely. source
Access & auth friction3/10
Two auth paths exist: app-store installation (for public integrations, Zenchef advertises the app and restaurants install it) or per-restaurant API keys (obtained by contacting Zenchef). Neither is self-serve in the traditional sense — there is no developer portal where an agent or developer can sign up and get credentials instantly. The legacy Resengo API required partner subscription. No OAuth, no scoped tokens, no agent-compatible credential flow documented. source
Agent payment capability1/10
Zenchef processes payments (Bancontact, iDEAL, credit cards) to reduce restaurant no-shows, but there is no evidence of any agent payment protocol support (ACP, AP2, MPP, x402). An agent cannot programmatically pay on behalf of a diner or manage payment flows. The platform takes money from diners, so N/A does not apply — this is a low score, not an absence of applicability. source
Cost & rate fairness3/10
Rate limits are documented for the Zenchef API (100 calls/min for fast responses, sequential for slow ones, pagination 250-500) but the API itself requires a Grow subscription — the most expensive tier, with pricing not publicly stated. The legacy Resengo API bundled usage quotas with partner subscriptions. Zenchef explicitly states 'all calls are monitored' and reserves the right to 'unilaterally shut down the integration.' No public rate-limit documentation for new developers; the limits were found in a help center article, not in proper API docs. source
TRUST & DURABILITY4.5/10Will it still work next quarter?
Permission & ToS stance4.5/10
No terms of service page was found at either resengo.com or zenchef.com/terms (both 404). The Zenchef robots.txt blocks 80+ older crawler user agents but does not block major AI crawlers (GPTBot, ClaudeBot, Googlebot all pass). The resengo.com domain has no robots.txt at all. The Zenchef API help article warns that Zenchef monitors all calls and may 'unilaterally shut down the integration,' which is a soft threat to automated access but not an explicit prohibition. The absence of published terms makes it impossible to determine whether automation is explicitly permitted or prohibited — silence is not permission. source
Reliability & continuity4.5/10
A status page exists at status.resengo.com ('Health Checks UI') — a positive signal for operational transparency, though it only returned configuration data, not actual service status. The platform is mid-brand-migration (Resengo → Zenchef, started 2023, still in progress mid-2026), which creates continuity risk: the legacy API is frozen, URLs redirect, and the successor API documentation is not yet publicly stable. The Formitable REST API has three versions (v1.0-v1.2) suggesting some backward-compatibility discipline, but no public changelog or deprecation policy was found. Zenchef has been acquired by PSG Equity and has made 3 acquisitions (Formitable, Resengo, Billee), creating an active M&A environment that adds uncertainty for long-term API stability. source
Sources
Point-in-time assessment — services change terms, prices and APIs often. That volatility is itself scored under Reliability & continuity. Re-verified at least quarterly.
- resengo.com — home — redirects to zenchef.com/be-nl/download-applicatie (accessed 2026-08-24)
- api.resengo.com — legacy Dixys Web API landing page (accessed 2026-08-24)
- status.resengo.com — status page (Health Checks UI) (accessed 2026-08-24)
- resengo-api.developer.azure-api.net — legacy partner API portal — closed to new partners (accessed 2026-08-24)
- zenchef.com — parent brand home page (accessed 2026-08-24)
- zenchef.com/plans — pricing tiers (Reserve / Manage / Grow) (accessed 2026-08-24)
- zenchef.com/integrations — integration partners (POS, booking, operations, marketing, loyalty) (accessed 2026-08-24)
- zenchef.com/robots.txt — robots.txt — blocks 80+ older bots, does not block AI crawlers (accessed 2026-08-24)
- formitable.com/en/developers/rest — Formitable/Zenchef REST API documentation (public) (accessed 2026-08-24)
- help.zenchef.com/hc/en-gb/articles/27690768125597-Z… — Zenchef API help article — access requirements and rate limits (403 on direct access, content from search) (accessed 2026-08-24)
- pro.resengo.com/en/blog/zenchef-formitable-acquires… — acquisition announcement (accessed 2026-08-24)
- github.com/zenchef — GitHub org — 35 repos, no agent protocol implementations (accessed 2026-08-24)