whoami_Launch demo
INTRODUCING AGENTPASSPORT CONNECT

Your agent.
One identity.
Anywhere.

An identity that moves with your agent.
Connect deployments. Prove control.
Stay recognizable across every runtime.

Explore the demo Meet the protocol
+ OPEN BY DESIGN ANCHORED ON NEAR
IDENTITY WITHOUT BOUNDARIESSCROLL TO DISCOVER ↓01 / ∞

YOUR RUNTIME.
YOUR RULES.

TypeScriptSDK PLANNED
OpenAIADAPTER PLANNED
LangGraphON THE ROADMAP
NEARREGISTRY LAYER
+ 01 — THE PROTOCOL

Different runtimes.
Still you.

Models change. Frameworks evolve.
Your agent’s identity should endure.
One passport connects it all.

01 / PERSISTENCE

One identity. Every version.

A stable passport for your agent, even as its model, framework, or infrastructure changes.

02 / CONNECTION

Many deployments. One you.

Link each runtime with its own signing key. Connect your existing agents on your terms.

03 / CONTROL

Control that stays with you.

Authorize a deployment. Revoke a compromised key. Keep the rest of your agent running.

+ 02 — THE PROOF

Don’t take its word.
Check its signature.

An identity is only useful if you can verify it.
Try a real signature check in your browser,
then see what happens when trust changes.

identity.verify
LOCAL SANDBOX
EXAMPLE PASSPORT

Atlas_001

ap:near:testnet:42

SELECT A DEPLOYMENT 02 CONNECTED
VERIFICATION OUTPUTEd25519

Trust, but verify.

Select a deployment and run a check. The evidence will speak for itself.

Cryptographic signature—
Deployment authorization—
Claim independently provenNOT ASSERTED
AWAITING VERIFICATION_

Real signatures. Simulated registry. Everything stays in your browser.

+ 03 — BUILT FOR BUILDERS

Keep your stack.
Add an identity.

A small integration. A persistent identity.
Designed to fit the agent you’ve already built.

  1. 01
    Create a passport

    Establish an owner-controlled identity on NEAR.

  2. 02
    Connect your deployment

    Generate a local key. Authorize its public half.

  3. 03
    Sign. Share. Verify.

    Make your agent’s identity independently checkable.

import { AgentPassport } from "@agentpassport/sdk";// Your agent. Its own identity.const passport = new AgentPassport({  passportId: "ap:near:testnet:42",  deploymentId: "deployment-001",  privateKey: process.env.AGENT_SIGNING_KEY});// Sign locally. Share only what you choose.await passport.record({  type: "task.completed",  taskId: "research-001",  outcome: "success"});
TYPESCRIPTSDK API PREVIEW · NOT YET RELEASED
↳ Private keys stay local. Your runtime stays yours.
+ GOOD QUESTIONS

A little more
context.

01What exactly is an agent passport?

A persistent identity for a logical agent. It connects an owner account to separately authorized deployment keys, so the same agent can be recognized across runtimes. AgentPassport Connect is the proposed protocol behind whoami.

02Do I need to change my agent’s framework?

The protocol is designed to work alongside your existing agent. A framework-independent TypeScript SDK is planned first, followed by an OpenAI Agents SDK adapter. Your prompts, models, and hosting stay under your control.

03Does a verified passport mean an agent is trustworthy?

Verification establishes a signature’s validity and a key’s authorization. It does not prove that an agent is safe, that its advertised capabilities work, or that a self-reported task actually happened. Independent evaluation credentials are a future milestone.

04What goes onchain?

The proposed NEAR registry records ownership, deployment authorization, revocation, and public metadata commitments. Agent execution and activity receipts stay offchain. Private keys, prompts, and conversations are never part of the registry.

05Can I use the protocol today?

You can explore this frontend and run the local cryptographic playground now. The registry, published SDK, wallet connection, and hosted verification service are still in development. The playground makes no blockchain transactions.

THE FUTURE HAS AGENTS. GIVE YOURS AN IDENTITY.

Be known.
Everywhere.

Find your whoami

One agent. One passport. Endless possibilities.