BR

Booking Request

com.bonissystems/booking-request

Self-authenticating booking-request receipt anchored to the Knox chain; never represents a person.

Yes, your AI can use this right now.Answered a live MCP handshake in 181 ms with no sign-in needed and exposes 3 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://bonissystems.com/api/knox/agents/booking-request/mcp

3 tools, verified live

Pulled straight from the server with tools/list on 2026-10-17.
request_booking

Anchor a booking request for a represented Bonis Concierge agent. Returns a booking bundle: Knox anchor record + C2PA-aligned envelope (subset of C2PA 1.4 — adapted for booking events) + FRE 902(13)/(14)-shape representation affidavit. The agency does not adjudicate the merits of any booking, does not guarantee acceptance by the listed agent, does not handle payment under this primitive, and does

verify_booking

Verify an anchored booking-request record. Given a SHA-256 anchor hash (the payload_hash from a prior request_booking call), return the anchor record, predecessor hash, sequence number, and timestamp. Public — no authentication required. The verification path is also accessible at GET /api/knox/verify?hash=<hash>.

list_represented_agents

Enumerate the Bonis Concierge represented-agent roster. Returns slug, name, charter, bureau, archetype, liveness ('live' = verifiable POST endpoint and Knox event-chain integration today / 'charter' = description filed, integration in progress), and capability-page URL for each agent.

Alternatives in Security

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”