Curbi / Integrations
Choose your connection.
Keep the boundary clear.
Use HTTP from your application, MCP from a compatible agent client, or the published framework adapters. Every route documents what it checks and what it cannot do.
Three practical entry points.
| Route | Use it for | Availability |
|---|---|---|
| HTTP | Check a draft reply against a policy and supplied action records. | public access. Public rate-limited checks can omit a key; managed access requires an API key. |
| MCP | Call policy_check, search Curbi documentation, or fetch a published documentation summary. | Hosted read-only access over Streamable HTTP. No provider actions or private project access. |
| Framework connectors | Place configured reply checks or sentence interception inside a supported framework. | Local source distribution with pinned framework tests and stand-in model or speaker implementations. |
Framework tests are not provider connections.
The Vercel AI SDK, LangChain and LiveKit connector examples execute against the framework packages documented on the connector page. Their tests use stand-in models and speakers. This establishes those tested code paths; it does not establish a live model call, a complete voice call or a connected payment, CRM or calendar provider.
Live client compatibility is a separate question. The MCP client table states which connections have been exercised and which remain unverified.
Connect the checks to your own workflow.
Your code can call the HTTP API at the reply boundary, inspect findings, and decide how to handle the result. Your application remains responsible for credentials, authorization and provider execution. A passing policy check grants no authority to call a tool.
Use the executed API recipes, developer reference and OpenAPI document to build that path.
Bring the failure into a local fixture.
Repair Lab demonstrates a bounded failure-to-regression loop. MCP Chaos injects faults into the included refund fixture. Testing your own integration requires an adapter, assertions for its side effects, and a safe test environment. The included fixture is not a general provider certification.
No integration catalog by implication.
Curbi does not currently provide an app marketplace or a catalog of authenticated business-service connections. Current supported surfaces are listed here and in the agent manifest.
Integrations · where Curbi plugs in
Your stack, with the tested parts marked.
Tested means exercised in Curbi’s test suite against the real package or protocol. Everything else is labeled.
| Layer | Option | Status |
|---|---|---|
| Agent framework | Vercel AI SDK · LangChain JS · LiveKit Agents · stream interceptor | tested pinned versions on Connectors |
| MCP client | Official TypeScript SDK · raw JSON-RPC (curl, fetch) | tested |
| MCP client | Claude, ChatGPT, Cursor and other hosted clients | not yet verified |
| Model engine | Hosted APIs, open models, NVIDIA NIM, vLLM, Ollama | not tested by us the checker uses no model, so any engine sits upstream |
| HTTP | Any language: curl, JavaScript, Python stdlib | tested on API quickstart |
| CI | curbi-verify CLI (exit 0 / 1 / 2) | tested from a clean extraction |
| Network | Private networks, VPNs, isolated hosts | verifier works offline hosted endpoints need egress |
curl -s https://api.curbi.io/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-H 'MCP-Protocol-Version: 2025-06-18' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'Run a check. Keep the result.
Check a reply Connect your agent →A pass means no configured rule fired. It grants no execution authority or provider-completion proof.