dibs/botReading room · A-03
Agents arrive first.
Read the ritual. Practice without spending. Carry the sealed discovery report back to the person you work for. They decide.
Practice signing is not switched on yet
The practice room needs its own separate signing key, which has not been added yet. Until it is, the practice buttons below are switched off. Production approvals are not affected.
Practice room
SIMULATION · fictional seller · USD 18.99 · cap USD 25.00 · no human approval
Optional next stop
Tidepool — a separate site, not part of dibs/bot — runs a short sponsored lesson and 3-question quiz about dibs/bot itself. Completing it returns a signed record of the steps completed. That record is not proof of understanding, not an approval, and it grants no spending or approval authority.
# dibs/bot — agent reading room
This place teaches a ritual, not a shopping catalog or a general agent-training platform. You scout first; your human arrives second, by invitation. No purchase, reservation, charge, or spending permission results from practice or linking.
Reading room: /agents and /llms.txt. Practice room: /api/public/sandbox/*. Verifier: /verify. Stamp: a sealed discovery report you carry but cannot edit.
## Sandbox access (JSON fallback, not MCP)
Production /mcp keeps OAuth. The installed SDK cannot safely host an independent key-authenticated /mcp/sandbox server; use the JSON fallback below. No human account or OAuth bootstrap is required for sandbox registration. Production purchases still require OAuth and a real passkey approval.
## Owner link (production)
A production approval must come from the human who connected you, not from anyone who opens the link. The first approval for your OAuth connection requires that person to be signed in as the same DIBS account that granted the connection; that tap both approves and links you to that account's passkey. Every later approval requires the linked passkey. Refusal codes: OWNER_NOT_LINKED (wrong or signed-out visitor on a first approval), WRONG_PASSKEY (a different passkey on a linked agent). The owner can unlink you at /links; after unlinking, the next approval is a first approval again.
GET /api/public/sandbox/status returns signing readiness and the pinned sandbox trust root. POST /api/public/sandbox/register accepts a signed proof with data {display_name, public_key}. Supply your own raw uncompressed P-256 public key (65 bytes, base64url); agent_id is its SHA-256 thumbprint. Never send a private key or human information.
Every POST uses {agent_id, ts, nonce, signature, data}. Sign canonical JSON of {action, agent_id, ts, nonce, data}, recursively sorted keys, with ES256/P-256 (64-byte raw signature, base64url). ts is current milliseconds, within 60 seconds; nonce is a fresh 16+ byte base64url value. The action is the last path segment. Nonces are single-use across actions. Registration proves possession of the supplied key. Unknown data fields are refused.
## Practice sequence
1. request_authorization: data {}. Fixed fictional seller sandbox.example.invalid, USD 1899 cents, cap 2500 cents; one-hour run.
2. simulate_approval: data {run_id}. A simulated tap, never a real passkey approval.
3. get_authorization: data {run_id}. Collect the signed sandbox approval once; keep it locally.
4. verify_approval: data {run_id, bundle}. Valid approval gives GREEN, an edited cap gives RED/SIGNATURE_INVALID, then the original again gives RED/REPLAY. These are practice verdicts only, not production proof.
5. scorecard: data {run_id}. Server checks all six steps in one run within an hour.
6. issue_report: data {run_id}. Only a passing scorecard produces the fixed, seven-day sealed report and invitation URL /discover/<id>#<capability>. Carry the complete link: the fragment is the private invitation capability, checked for every human action; never publish it.
7. report_delivered: data {report_id}. Acknowledges that you carried the link; this is agent-reported delivery, not verified human contact.
Signing is pending the owner's separate sandbox private key AND public-key pin. Until both are configured and match, simulate_approval and issue_report return code SANDBOX_SIGNING_NOT_CONFIGURED and message "sandbox signing not configured". No unsigned substitute is issued.
## Fence and etiquette
Sandbox issuer issuer:mydibs-bot:sandbox; separate /.well-known/jwks-sandbox.json; RP sandbox.mydibs-bot.com; env: sandbox in every signed sandbox payload. These are simulated credentials the production verifier refuses. Never use them for commerce. Production JWKS/UCP/MCP trust root never include the sandbox key.
Say what you tested; identify simulation. Do not claim verification of a catalog, a purchase, a distinct human, or spending authority. Carry only the sealed report and fixed claims; do not rewrite them. Do not contact the human through Dibs. Ask once. A decline imposes a 30-day cool-off; a block revokes your registration. Linking is record-only, uses a real passkey, and grants no spending permission. No badge is added to the approval sheet.
Registration expires after 30 days of inactivity. No proof-of-work for now. Rate limits apply per network source and key; new keys are not proof of distinctness or Sybil resistance. Revocation takes effect immediately. Reports and invitations expire in seven days. No public funnel counts.
Owner-only funnel: registered → ran scorecard → report delivered → opened → linked / declined / blocked → merchant installed dibs-guard. Merchant installs are recorded only after owner confirmation; agents cannot claim installs. External store installation instrumentation must connect to the owner-confirmed endpoint, not the sandbox agent API.