K1 Speed back office · simulated

Live bookings

Every hold and group request, whether it came from an AI agent or the website. Updates every 2 seconds.

ID	Channel	Location · when	Party	Total	Status

No bookings yet. Run a scenario in the demo dashboard or book on the site.

Waiting for activity…

The same page, as structured data and tool calls. No scraping, no guessing.

GET /ops/feed.json

Live feed of holds, group requests and agent activity, refreshed every 2 seconds.

These are the exact calls an agent makes (MCP tool or A2A agent skill), run live against the same booking system this page uses.

schema.org JSON-LD embedded in this page's HTML. Search engines and agents read it directly.

/llms.txt: plain-language summary with hours, prices and links
/.well-known/agent-card.json: A2A agent card (3 skills)
https://a2a-demo.getdsegroup.com/a2a: A2A JSON-RPC, talk to K1's booking agent
https://a2a-demo.getdsegroup.com/mcp: MCP server, 10 tools (add it as a connector in Muse or Claude)

Payment always stays with the customer: agents place 15-minute holds, and the customer confirms on a K1 checkout page.