Corbits

Build leading AI solutions with Corbits libraries.

Control planes, messaging APIs, Agents SDK, web search, and file search, with identity, grants, and signed records for every agent.

Read the docs

Agents you can identify, scope, and audit ready for production.

“We get way better results from our agents running on Corbits than any other system.”
VP Engineering, 100+ engineer organization
  1. Each agent runs as its own principal, so every action traces back to it.

    finance-agentsupport-agentresearch-agent
  2. Allow, deny, or ask rules scoped to a role or principal, checked before an action runs.

    allow read ledger/*

    deny read hr/*

    ask send email/*

  3. Every call is signed. If the record can't be written, the session stops.

    record: hub unreachable

    buffer: brief

    session: stopped

Every action is signed and scoped.

Trace which grant allowed it and which agent it belongs to.

corbits / record

Open platform

  • finance-agentallow · read · ledger/*signed
  • finance-agentdeny · read · hr/*denied
  • support-agentask · send · email/*awaiting approval
  • research-agentallow · call · web.searchsigned

FAQs

Does it work with agents on other frameworks?
They can route calls through Corbits for routing, central keys, and cost attribution. Identity, grants, and the signed record come with agents running on Corbits.
How are permissions written?
As grant rows: allow, deny, or ask, over resource and action patterns, scoped to a role or principal.
What happens if the record can't be written?
The session buffers briefly, then stops. Actions don't run unrecorded.

Libraries built to grow with every agent, tool, or colleague.

Read the docs