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 30.45% of live MCP servers use OAuth (source: arxiv 2605.22333). 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%) (source: AI Invest agent-identity forecast, 2026). Non-human identities already represent 47% of all identities in many enterprises (source: C1 identity research, 2026).

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 low milliseconds after warm cache (benchmark-dependent), 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 low-milliseconds verification (benchmark-dependent)
• MCP OAuth module — OAuth 2.1-aligned flows for MCP servers
• SDKs — lime-agents-sdk (Python, PyPI) and lime-sites-sdk for site integrations

How it works

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.

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; the signing private keys stay with LIME Core.

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.

Verify in milliseconds

Consumers fetch JWKS with caching, validate iss, aud, exp, and signature. JWKS-backed verification completes in low milliseconds after warm cache (benchmark-dependent) — 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("550e8400-e29b-41d4-a716-446655440000")
        print(result.status)
        tools = await agent.list_tools(MCP_URL)
        print(len(tools))
    finally:
        await agent.aclose()

asyncio.run(run())

Key features

One-step onboarding

Register, verify email, create agent — minutes, not quarters.

Local JWKS verification

Standard JWT verification at agent scale with cache-friendly JWKS.

MCP OAuth

OAuth 2.1 baseline for MCP; avoid raw API keys on tools.

Free tier

Start building without procurement; scale when you need enterprise controls.

Headless-first

Built for agents and automation, not browser redirects.

Open SDKs

Python on PyPI today; patterns documented for other runtimes.

We built LIME because only 30.45% of live MCP servers use OAuth (source: arxiv 2605.22333) — and the remaining majority deserve better than copied API keys in .env files.

Why now

Three forces converge in 2026:

Agent explosion

The AI agent market CAGR near 50% through 2033 (source: AI Invest agent-identity forecast, 2026). Agent identity and security submarkets add billions more. Budget and risk committees are asking how agents are identified — not just what model they run.

MCP won the integration debate

Anthropic, Microsoft, Okta, Figma, Asana, Atlassian, Linear, Supabase, and others ship MCP support. Catalogs list 28,000+ MCP servers (source: directory listings, 2026). Enterprise Managed Authorization stabilizes auth in the MCP spec. LIME ships as an MCP OAuth provider.

Identity vendors catch up — slowly

Ping, Descope, and C1 launch headless agentic identity hubs. 95% of organizations report agents executing IT tasks autonomously (source: C1 identity research, 2026). Private rounds in agent identity platforms hit 15–30× revenue multiples. RSA 2026 framed this as the start of the Agentic Identity era.

• Agent identity market: $182.9B by 2033 (CAGR ~49.6%; source: AI Invest agent-identity forecast, 2026)
• 75–85% of organizations deploying or piloting AI agents
• 26% of organizations view AI agents as an identity threat (source: Regula identity survey, 2026) — cryptographic passports reduce that risk

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

Who is LIME for?

Developers shipping AI agents

Need signed identity without bolting OAuth onto headless workers.

Platforms orchestrating many agents

Need JWKS, scoped passports, and consistent verification across services.

MCP server builders

Want OAuth 2.1-aligned auth instead of static keys; align with spec direction.

Security and platform engineers

Need non-human identity that compliance teams can reason about: cryptographic proof, not shared secrets in chat.

What's next

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

Get your agent passport

The agent identity market is heading toward $182B by 2033 (source: AI Invest agent-identity forecast, 2026). MCP is the integration layer. OAuth alone does not fit headless agents. Cryptographic passports are the emerging standard — and LIME is ready for production experiments today.

Register free at lime.pics

Read the docs

Links

• register: https://lime.pics/register/
• docs: https://lime.pics/docs/
• github: https://github.com/Mawyxx
• pypi: https://pypi.org/project/lime-agents-sdk/
• /mcp-oauth/

Sources

Sources: AI Invest, MCP ecosystem surveys, Gartner, Forrester/Identiverse, Forbes & IETF APS, C1 Future of Identity, MCP Community/EMA, Windsor Drake, Regula, World Economic Forum.