Ekam blog
API clients, test runners, CI jobs and MCP tools now act on their own — and they all authenticate with the same long-lived, unscoped, un-revocable key. Here's what a real agent identity unlocks for a developer platform and the users who live inside it.
Every agent-identity system tells you who an agent is. None tell you what it cost. Ekam fuses identity with inference metering — per agent, per owner, and across a delegation chain — so the token that authorizes a call also accounts for it.
AI agents are about to outnumber human users. They authenticate with shared, long-lived API keys that can't be scoped, attributed, or revoked. For India to build AI the world trusts, agents need real identity — and a control plane that lives under our own law.
An Ekam token is an ES256 JWT your gateway verifies in-process against a cached JWKS — no network call to authorize a request. Here's the architecture, the exact checks, and the measured numbers.
Every endpoint below is live in open beta. Copy a curl, get a working result. From governing an MCP server to a kill-switch drill — concrete use cases, not slideware.
A model gateway hands out one shared key and hopes for the best. BharatRouter swapped that for verifiable, revocable, human-rooted agent identity — here's the architecture and what it gains.