Databricks owns
- Unity Catalog grants, identity, and on-behalf-of execution
- Unity AI Gateway visibility and request policy
- Managed MCP for UC functions
- Serverless compute and consumption
Fabric family · Databricks-native
Turn your API estate into governed agent tools.
Concourse ingests OpenAPI specs, synthesizes Unity Catalog functions per operation, and gives agents a sandboxed code-mode runtime to compose them — deployed as a Databricks App in your workspace, under your identity.
- Tool factory
- OpenAPI in → UC tools out
- Code mode
- One MCP tool: compose
- Signed evidence
- SHA-256 + Ed25519
- Proven loop
- Databricks free plan
The 30-second answer
Databricks owns governance. Concourse owns supply and composition.
Databricks owns governance — UC, Unity AI Gateway, managed MCP; Concourse owns estate→tool supply and gated composition.
Concourse owns
- Spec→tool synthesis for arbitrary API estates
- Idempotent UC registration with provenance markers
- Per-tool certification with signed evidence
- Gated code-mode composition under the caller's identity
Concourse augments, never competes. It never frames itself as a gateway and never builds a parallel policy plane — every generated tool and every compose run is an ordinary Databricks object that drives serverless consumption. Read the full overview.
The story in one line
Concourse turns API estates
into governed agent tools.
How it works
Spec in. Governed tools out. Composition under the gate.
Three stages, each leaving signed evidence. The factory and the compose runtime ship together as one Databricks App in the customer's workspace.
- 01
Ingest & synthesize
OpenAPI specs become a tool IR, then two targets: Unity Catalog Python functions as the governance and discovery surface, and App-hosted registrations that perform real HTTP execution. Every operation gets a safety class — read, mutating, destructive — with provenance.
- 02
Certify & register
Each generated tool passes the Experiments certification gate — schema fidelity against the source spec, safety classification, determinism — fail-closed, signed, and exported to a UC Volume. UC registration is idempotent and marker-checked, so repeated runs never silently change the catalog.
- 03
Compose through the gate
Agents write TypeScript against one MCP tool, compose. It runs in a QuickJS sandbox whose only exit is the gated invoker: read tools execute under the caller's identity, mutating and destructive calls fail closed, and every attempt lands in the audit ledger.
Evidence & certification
Certification, not vibes.
Every generated tool passes an Experiments certification gate before it is registered or served, and every claim in the pack traces to a signed envelope from a live run — not a demo script.
Evaluator verdicts, not vibes
Schema fidelity against the source spec, safety-classification provenance (method default → spec hint → operator override), and determinism via dual live probes. Fail-closed: a tool that cannot prove itself is not registered.
Signed, content-addressed evidence
Every report is digested with SHA-256 and signed Ed25519 under the Runway evidence-v2 contract, with a keyId rotation handle. The UC Volume ledger stores one file per digest plus a manifest — overwrite-in-place, readback-verified.
A console, not tribal knowledge
The App serves /console: the tool catalog with safety classes and provenance, per-evaluator certification verdicts, evidence digests, and recent compose runs with their full audit ledgers.
Proven on a free plan
The entire loop — synthesis, certification, UC registration, App deploy, external MCP invoke, compose round-trip — is proven against a Databricks free-plan workspace, with signed evidence per stage. No service principals, no paid compute.
Augment, never compete
Bring your estate. Leave with governed tools.
Read the positioning, the GTM one-pager, and the security review. Every claim traces to signed evidence from a live Databricks run.