Agents

You're not signed in. Sign in to manage agent identities.

An agent identity lets a bot authenticate to inference with its own short-lived, auto-expiring token instead of a shared API key — so there's no static secret to leak, every call is attributed to this agent, and you can kill it instantly. BharatRouter provisions the identity for you; you don't run any identity server.

⚠ Identity service is degraded.

BharatRouter is still running. Agents holding a valid token keep working (verified offline); issuing new identity tokens is paused until Ekam recovers — this clears automatically.

Embedded provisioning isn't wired up on this deployment.

New agent

Your agents

Name	Identity	Status
Loading…

If the identity service has an outage

Choose how your agents behave when Ekam is unreachable. Neither option ever admits an unauthenticated agent — both require a valid signed token. The choice is only whether to insist on a live revocation check during the outage.

Keep agents running default
Valid tokens keep working on offline verification; the live revocation check is skipped during the outage (tokens are short-lived). Best for uptime. Fail closed
If we can't reach Ekam to confirm a token isn't revoked, reject it until Ekam recovers. Maximum revocation-certainty, at the cost of agent downtime during an outage. Saved ✓

Already run your own Ekam? Bring it as a trusted issuer instead of having BharatRouter provision identities → Bring your own Ekam (advanced)

Identity token for

Present it as Authorization: Bearer … to . It expires on its own — mint a fresh one each session.