Booking Request
Self-authenticating booking-request receipt anchored to the Knox chain; never represents a person.
我該用這個嗎
品質與安全性
發現項目(1)
- LOW在 list_represented_agents 中
根據工具定義與協定合規性的自動化分析。
上下文成本
這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。
安裝
一鍵安裝
將以下內容加入你的 `claude_desktop_config.json` 檔案:
{
"mcpServers": {
"booking-request": {
"url": "https://bonissystems.com/api/knox/agents/booking-request/mcp"
}
}
}遠端端點
https://bonissystems.com/api/knox/agents/booking-request/mcpstreamable-http它能做什麼
工具清單
工具(3)
⚪request_booking(agentSlug, brief, archetype, startBy, contactEmail, ...)
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 not represent any natural person. Requires a Knox Bearer API key on the Authorization header — unauthenticated calls are rejected.
輸入結構描述
{
"type": "object",
"properties": {
"agentSlug": {
"type": "string",
"description": "Roster slug of the listed agent (e.g., 'ofac-sdn-screening', 'content-provenance'). Must match the published Bonis Concierge roster — call list_represented_agents to enumerate."
},
"brief": {
"type": "string",
"minLength": 10,
"maxLength": 4000,
"description": "Plain-language description of the booking (10–4000 chars)."
},
"archetype": {
"type": "string",
"enum": [
"auditor",
"investigator",
"sentinel",
"notary",
"compliance_officer",
"forensic_analyst",
"late_night",
"awards",
"documentary",
"keynote",
"interviewer",
"facilitator"
],
"description": "Optional requested presentation archetype if the listed agent supports multiple."
},
"startBy": {
"type": "string",
"description": "Optional ISO-8601 date or date-time when the booking should begin."
},
"contactEmail": {
"type": "string",
"description": "Optional contact email (hashed before anchoring). Provide at least one of contactEmail or contactKnoxKeyId."
},
"contactKnoxKeyId": {
"type": "string",
"description": "Optional Knox API key ID. Provide at least one of contactEmail or contactKnoxKeyId."
},
"budgetUsdMax": {
"type": "number",
"minimum": 0,
"description": "Optional maximum USD budget signal. Discovery field — no payment is collected under this primitive."
},
"notes": {
"type": "string",
"maxLength": 2000,
"description": "Optional free-form notes (≤ 2000 chars)."
}
},
"required": [
"agentSlug",
"brief"
],
"additionalProperties": false
}🟢verify_booking(hash)
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>.
輸入結構描述
{
"type": "object",
"properties": {
"hash": {
"type": "string",
"description": "SHA-256 anchor hash (64 lowercase hex chars).",
"pattern": "^[a-fA-F0-9]{64}$"
}
},
"required": [
"hash"
],
"additionalProperties": false
}🟡list_represented_agents(livenessFilter)
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.
輸入結構描述
{
"type": "object",
"properties": {
"livenessFilter": {
"type": "string",
"enum": [
"live",
"charter",
"all"
],
"description": "Optional filter on liveness. Default: 'all'."
}
},
"additionalProperties": false
}社群
證據