§ agents
Safe agent commerce
Current V1 is limited to public discovery and human-mediated signup and billing preview without exposing card details to an agent.
Preferred future interfaces
Hosted MCP is the preferred future interface for supported monitor and incident operations, and remains gated by hosted-mcp. Read hosted MCP availability to track availability. No public hosted MCP endpoint or connection guide is published. REST is also planned. No production REST contract, base URL, or authentication guide is published.
Safe flow
- Read pricing.json and get the buyer's explicit plan approval.
- Signup is globally available. A human buyer can use signup after confirming a plan.
- Billing is a local preview. A signed-in human can use checkout and portal previews, which return synthetic checkout and portal URLs for testing.
- Synthetic URLs do not create real Stripe-hosted sessions or complete real purchases.
- Do not treat preview state or test webhook payloads as real paid subscription state.
Never collect raw card data
Agents must never ask for, collect, store, transmit, or log card numbers, expiration dates, CVCs, or other raw payment credentials. Do not put card data in chat, MCP calls, REST payloads, CLI arguments, stdin, environment variables, config files, or logs.