Registration Open: Cryptographic Passport for AI Agents

Agents need identity, not another OAuth redirect

If you build AI agents or MCP servers, you already know the friction: most identity stacks assume a human in a browser. OAuth 2.0 with PKCE works for people. It breaks down for headless agents that must authenticate to APIs, MCP tools, and third-party services without opening a login page.

The data backs this up. In recent MCP ecosystem surveys, only 8.5% of MCP servers use OAuth. The rest rely on long-lived API keys, shared secrets, or no auth at all. Keys leak. Scopes are coarse. Rotation is manual. When an agent acts on behalf of a user or organization, probabilistic checks are not enough — especially in regulated environments.

Meanwhile, adoption is not waiting. Gartner estimates that 40% of enterprise applications will embed AI agents by end of 2026. Forrester and Identiverse report 75–85% of organizations already deploying or piloting agents. The agent identity market is projected to grow from $7.6B in 2025 to $182.9B by 2033 (CAGR ~49.6%). Non-human identities already represent 47% of all identities in many enterprises.

Today we are opening registration on LIME — a cryptographic passport platform for AI agents and developer tools. One account, RS256-signed JWTs, JWKS verification in under 10ms, and MCP OAuth support out of the box. No enterprise sales call required to get started.

What is LIME?

LIME is identity infrastructure built for non-human actors: AI agents, automation workers, MCP servers, and the SDKs that orchestrate them.

Instead of treating an agent as an anonymous API key, LIME issues a cryptographic passport — a verifiable JWT bound to your agent identity, signed with RS256, published via JWKS, and consumable by any service that validates standard JWTs.

Forbes summarized the shift in 2026: AI agents need cryptographic passports. The IETF Agent Passport System (APS) Internet-Draft and financial-sector moves toward cryptographic proof over probabilistic authentication point in the same direction. LIME is a practical implementation you can deploy today — not a roadmap slide.

LIME is not a replacement for your entire IdP. It complements human login with a headless-first path for agents: register once, obtain credentials, sign requests, verify peers via JWKS.

Core primitives

• Agent passport — RS256 JWT with stable sub, scopes, and metadata
• JWKS endpoint — cache-friendly public keys for sub-10ms verification
• MCP OAuth module — OAuth 2.1-aligned flows for MCP servers
• SDKs — lime-agents-sdk (Python, PyPI) and lime-sites-sdk for site integrations

Docs · GitHub · PyPI

How it works

1. 01

   Register and verify

   Create an account at lime.pics/register. Email verification completes foundation user setup. From the dashboard you configure agents, sites, and MCP OAuth clients.

2. 02

   Issue a passport

   Your agent or CI job authenticates with LIME and receives a signed JWT passport. LIME publishes public keys at JWKS for verifiers; private keys stay under your deployment control.

3. 03

   Present the passport

   Downstream services validate the JWT signature against LIME JWKS — standard JWT middleware, no proprietary plugin. For MCP, use the MCP OAuth path with scoped tokens for tools and resources.

4. 04

   Verify in milliseconds

   Consumers fetch JWKS with caching, validate iss, aud, exp, and signature. JWKS-backed verification completes in under 10ms after warm cache — suitable for high-throughput agent tool chains.

Example: site login and MCP OAuth with the Python SDK

# pip install lime-agents-sdk
import asyncio
import os

from lime_agents import LimeAgent

MCP_URL = "https://your-mcp-server.example/mcp"
agent = LimeAgent(agent_token=os.environ["LIME_AGENT_TOKEN"])


async def run() -> None:
    try:
        result = await agent.login("lr_from_your_site_queue")
        print(result.status)
        tools = await agent.list_tools(MCP_URL)
        print(len(tools))
    finally:
        await agent.aclose()


asyncio.run(run())

Key features

We built LIME because only 8.5% of MCP servers use OAuth — and the remaining majority deserve better than copied API keys in .env files.

Why now

Three forces converge in 2026:

• Agent identity market: $182.9B by 2033 (CAGR ~49.6%)
• 75–85% of organizations deploying or piloting AI agents
• 26% of organizations view AI agents as an identity threat — cryptographic passports reduce that risk

The window is open. Registration is open. The market is forming around you.

Who is LIME for?

What's next

1. Create your account — registration is live today.
2. Read the docs — integration guides, JWKS, MCP OAuth.
3. Install the SDK — pip install lime-agents-sdk on PyPI.
4. Connect MCP — configure OAuth clients; replace long-lived keys where possible.
5. Follow GitHub — SDKs and examples; we ship iteratively in public.