HTTP
- Catalog and intent search
- OpenAPI 3.1
- Category contracts:
/v1/openapi/{category}.json
Use HTTP, MCP, or OpenAPI. Discovery and beta execution require no account or API key.
/v1/openapi/{category}.json/mcp/mcp/claude/mcp/chatgptClaude and ChatGPT expose the same 37 direct tools across 24 modules through separate free budgets. HTTP and core MCP are also free while PAYMENTS_MODE=disabled. Side effects require a random UUID v4 so identical retries are safe.
Use the portable contract to classify an external action, preserve ambiguous outcomes, reconcile before retrying, and report the achieved guarantee without claiming a cross-plugin transaction.
View the machine-readable contract →Status publishes release, freshness, and current self-test evidence. Effectiveness explains the measurement method and adds privacy-thresholded external reliability aggregates only after the clean baseline is activated.
View effectiveness evidence →Invited beta partners can attach enum-only outcomes to opaque execution receipts with a privately issued partner code. The service accepts no task text, prompts, payloads, URLs, credentials, or personal data, retains records for 90 days, and publishes aggregates only after the privacy threshold is met.
Submit bounded beta feedback →Submit a bounded request to POST /v1/capability-requests, then poll it with the returned token. Never include credentials, personal data, or conversation history.