Tell us what your agents need to reach. Name the app and the action.

An app, a REST API, a model provider or a remote MCP server. Tell us the vendor and what your agent needs to do there, like “create a refund” or “close a ticket”. Obol decides how it connects, and that decides what a receipt can prove. This form never asks for a password, token or key.

Connector request

What should Obol cover?

REST API

If every action is one bounded HTTP request, it can be imported from its OpenAPI file and reviewed action by action. You can already add your own API this way in the dashboard.

MCP server

You can already bring your own MCP server: Obol applies the same rules and keeps a record of each call. The server makes its own vendor request, so the record is labelled untrusted.

Model provider

A model endpoint behind /v1. Obol makes the request itself with your own provider key, so tokens and estimated cost are metered on your key.

The gate runs on the effect first. A production destructive tool, or an official or high-risk connector, is never federated, whichever way it arrives.

This form does not want a credential. No token, key, or client secret belongs in any box above — pasting one here would be a mistake, and we would have to ask you to rotate it. A vendor credential reaches Obol only through the vault, on an authenticated connection.

No date, no SLA, no queue position — we don't have those.

What happens to this request

The gate runs before anything else
A production destructive tool, or an official or high-risk connector, is never federated: it becomes a connector Obol runs itself, making the vendor request with your credential from the vault. Everything else in the long tail is mapped to a catalog broker.
Broker routes are mapped, not self-serve yet
The catalog maps 2,037 more apps reachable through your own Nango or Composio account, and activation is not self-serve yet. When it opens, it runs on your own broker account and OAuth client — never a pooled one — and a broker never mints a receipt, assigns evidence trust, enforces a policy decision or supplies an idempotency key.
The tier fixes what a receipt can prove
Every tool carries a required EffectSpec, and the receipt names the evidence class it earned.
Native
Gateway-observed: Obol makes the request itself, so a receipt can carry the vendor's own status and upstream id.
Federated
Broker-attested at best, never verified: a third party makes the call, so a receipt records what the broker reported, not what Obol observed.

It may already be on the map.

The catalog freeze maps 2,152 connectors — 115 reviewed packs Obol would run itself and 2,037 reached through a broker — projected into 321 capabilities.

That is coverage, not a list of what you can connect today. Today you can connect GitHub, Slack, Stripe and HubSpot, plus web search, code sandboxes and browsers, or bring your own MCP server or API. Browse the map before you ask for a new provider.

Native: Obol holds the vendor credential.
Federated: Your own broker account holds the credential. Activation is not self-serve yet.

Browse the coverage map

Tell us what your agents need to reach. Name the app and the action.

It may already be on the map.

Help us measure what works.