Supported integration boundary

Distinguish supported partner interfaces from internal product routes and connected-service implementation details.

Supported now

• Public restaurant website pages produced by Semperi
• Machine-readable restaurant discovery files documented here
• Partner integrations explicitly provisioned and documented by the Semperi team

Not a public contract

• Operator-dashboard network requests
• Internal oRPC operations
• Database schemas or direct database access
• Fleksa, payment-provider, POS, or other connected-service credentials
• Undocumented webhooks or callback routes

Before an integration is supported

Semperi and the partner must agree on authentication, tenant scope, read/write permissions, approval behavior, idempotency, rate limits, error handling, versioning, test data, and incident ownership.