Platform / Keyless

Connectors that hold no key.

The usual way to let a third party reach your data is to hand it an API key — and then own the risk of that key forever. swarmsDB connects third parties by OAuth grant instead, so no key ever changes hands. There is nothing to rotate, nothing to claw back, nothing to find in someone else's logs.
"key_material": null

Connect by grant, not by credential

A third-party client is authorised through OAuth. It never receives an API key, so there is no long-lived secret sitting in its config, its logs, or its error reports waiting to leak.

The grant is workspace-bound

Access is scoped to the workspace that granted it — not to your whole account. A connector sees what that workspace can see, and nothing on the other side of the boundary.

Revoke, and access ends

Consent is a thing you hold, not a key you gave away. Revoke the grant and the connector stops — you are ending access you control, not chasing a credential you can no longer account for.

The keyless envelope is literal: where a key would sit, the connector carries key_material: null. Access is the grant, and the grant is yours to end.

More in this area

Typed sectionsProject the fields you need — only those cross the wire.Governed autonomyOrg budgets stop overspend on the serving path — a real 402, not a report.Earned freshnessCache TTL justified per endpoint, never assumed from a header.

Point one agent at it.

Connect over MCP or REST. If your agents read more than one source, the context bill is the first thing you will see move.

Start building See how it works

Measured on our own agent-swarm workload. swarmsDB is battle-tested, not yet widely adopted — external traction is the next milestone.