Booking Request

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

CommunityDegradedNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

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

    How to connect

    How to connect Booking Request to Claude

    The server address to paste into Claude settings:

    https://bonissystems.com/api/knox/agents/booking-request/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect Booking Request to ChatGPT

    The server address to paste into ChatGPT settings:

    https://bonissystems.com/api/knox/agents/booking-request/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect Booking Request to Cursor

    The server address to paste into Cursor settings:

    https://bonissystems.com/api/knox/agents/booking-request/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (3)

    Raw names from tools/list. Only developers need these.

    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.
    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>.
    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.