Obol is a control plane for agent traffic. Connect models and MCP tools through one virtual key, apply policies before calls execute, and review audit trails and receipts with explicit evidence classes. Keep your agent runtime and vendor accounts. Obol verifies agent tool calls with webhooks and read back for writes. Invitation-only: request early access at tryobol.dev.
Hey Product Hunt, Iām Marlon, maker of Obol.
As agents gain access to real systems, teams need control over what they can do. Obol puts identity, policy, routing, and audit in the path of model and tool calls.
Point your agent at one MCP endpoint, authenticate with an Obol virtual key, and connect your own vendor accounts. Vendor credentials stay at the gateway. Policies determine what can execute, with approvals for sensitive actions when required by policy.
Receipts identify their evidence class: native routes can carry gateway-observed evidence; federated results are not gateway-observed proof.
You keep your agent runtime, vendor accounts, and vendor bills.
Obol is invitation-only. Request early access at https://tryobol.dev.
Which action would you want your agent to ask permission for first?
Docs: https://docs.tryobol.dev
Youtube Video: https://youtu.be/mcToSU94MSs