Skip to content
MCP server

Booking Request

By bonissystemsAll Bonissystems servers

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

First seen 2 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.

1
Directories
Collected by InvokeRank
3
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
-
GitHub stars
No repository data

Tools

ToolDescriptionBehaviour
list_represented_agentsEnumerate 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.Not declared
request_bookingAnchor 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 not represent any natural person. Requires a Knox Bearer API key on the Authorization header — unauthenticated calls are rejected.Not declared
verify_bookingVerify 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>.Not declared

Directory listings

DirectoryListingTierFirst seen
Official MCP RegistryBooking Request-2 Oct 2026
Booking Request MCP server | InvokeRank