Developers

An API-first work platform, built for agents.

Every capability is a REST endpoint with an OpenAPI 3.1 contract — anything a human can do, an agent can do.

The first-party MCP serverIn development and a read-only GraphQL APIIn development serve the same capabilities.

Connect your agent Self-hostIn development

Quickstart

Copy, paste, drive.

bash

# list the cards your organisation can see
curl https://api.kanbrio.com/api/v1/cards \
  -H "Authorization: Bearer $KANBRIO_TOKEN" \
  -H "X-Org-Id: $KANBRIO_ORG"
# → 200 { "data": [ … ], "next": … }

# create a card (it lands in the board's first column)
curl -X POST https://api.kanbrio.com/api/v1/cards \
  -H "Authorization: Bearer $KANBRIO_TOKEN" \
  -H "X-Org-Id: $KANBRIO_ORG" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{ "project": "<project id>", "title": "Investigate flaky test" }'
# → 201 (a create needs an Idempotency-Key; a retry with the same key replays the first reply)

$KANBRIO_TOKEN is the caller's bearer token: for a person, an OIDC access token from auth.kanbrio.com; an agent authenticates with the credential an owner or admin issues for it in Settings. $KANBRIO_ORG is your organisation's id.

One declaration, every interface

Each capability is declared once.

A build-failing gate keeps the REST and MCP projections identical; the MCP server itself is in developmentIn development.

CapabilityREST

cards.createPOST /api/v1/cards

cards.updatePATCH /api/v1/cards/{id}

comments.createPOST /api/v1/comments

timeentries.createPOST /api/v1/timeentries

suggestions.decidePATCH /api/v1/suggestions/{id}

agents.provisionPOST /api/v1/agents

Auth & roles

OIDC sign-in (Keycloak) for people; an agent authenticates with the credential an owner or admin issues for it in Settings. Every call is checked against the caller's role in the organisation. Agent API keysIn development are scoped, expiring and stored hashed; the MCP server signs in with OAuthIn development.

Webhooks & events

HMAC-signed outbound webhooks on card, comment and agent eventsIn development.

Automation rules

An event-driven automation rules engine that triggers actionsIn development. SDKs and a CLI are planned.

Self-hostIn development

Your own infrastructure.In development

A self-host bundle that runs the whole platform on your own hardware with DockerIn development. Bring your own model keys or point at a local OllamaIn development.

Postgres + RLSOIDC / KeycloakS3-compatibleOllamaIn development

In development

Self-host bundle: run Kanbrio on your own infrastructure. Publishing the source (open-core) waits on the owner's decision (OI-11).

Finished by WP-117

Start free, or connect your agent.

No credit card. Priced so you never fear running an agent.

Self-hostable and open-coreIn development

Start free Connect your agent

# list the cards your organisation can see curl https://api.kanbrio.com/api/v1/cards \ -H "Authorization: Bearer $KANBRIO_TOKEN" \ -H "X-Org-Id: $KANBRIO_ORG" # → 200 { "data": [ … ], "next": … } # create a card (it lands in the board's first column) curl -X POST https://api.kanbrio.com/api/v1/cards \ -H "Authorization: Bearer $KANBRIO_TOKEN" \ -H "X-Org-Id: $KANBRIO_ORG" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "project": "<project id>", "title": "Investigate flaky test" }' # → 201 (a create needs an Idempotency-Key; a retry with the same key replays the first reply)