Publishing your connector
The product principle, enforced end to end: the service proposes, you review and approve — nothing ships without sign-off.
The pipeline
- Review. Every proposed tool sits in your review queue with its name,
description, parameters, and any findings. Edit freely, then approve.
- Eval. Run the eval harness until it passes.
Auth-protected tools need a brokered credential or they fail loudly.
- Release. Cutting a release freezes the tool snapshot, signs it, and
drops it in the staging channel. Releases are immutable.
- Promote to prod. Staging is for testing; production is gated. Promoting
requires certification (see below) — the console shows a checklist of exactly what's missing and how to fix it.
Releases live in two channels, staging and prod, addressable as version aliases. Invoking against staging never touches prod traffic.
The certification gate
A prod release must be certified: the latest completed eval run passed the certification criteria, with per-item actions when it didn't. Attempting to promote an uncertified release returns promotion_blocked naming the gaps. Write tools can certify too — the safety suite carries write-safety scenarios, so mutating connectors are judged, not blocked.
What you publish
| Output | How it works |
|---|---|
| MCP server (Claude) | A hosted Streamable-HTTP server per project: tools/list from the frozen snapshot, tools/call executing your tools. Authenticate with a gateway key. A dependency-free stdio bridge is available as a build-time artifact for enterprise deployments. |
| OpenAI artifacts (ChatGPT / GPT developers) | Per release: a function-calling tool-schema array plus a GPT-Actions-compatible OpenAPI document (operations carry x-openai-isConsequential from effect classes). GPT calls execute against the same release via the gateway. |
Deprecated releases refuse downloads; the manifest and tool snapshots never carry credential material.
Rollback and release hygiene
- Rollback deprecates a release in place — terminal, audit-logged. The
data plane refuses deprecated releases and names the previous approved release as the fallback. One action reverts what's served.
- Export / delete your data any time: a project export is one JSON file
with specs, tools, eval history, releases, and telemetry; deletion is hard, immediate, owner-only, and leaves only an audit tombstone.
Next: Operate — telemetry, drift, and day-to-day running.