Wallet Verification for AI Agents

Agents Need Qualification, Not Identity

Current agent protocols answer "who are you?" with API keys and OAuth tokens. But the real question is "what do you hold?" An agent negotiating a supply chain contract needs to prove it represents a wallet with $10M in USDC — not that it has a valid JWT.

AgentTalk replaces identity-based auth with condition-based attestation. Both agents verify the same on-chain conditions before a session begins. No credentials to share. No trust assumptions. Just cryptographic proof.

// Identity-based (current)
Agent A: "Here's my API key"
Agent B: "OK, I trust you"
// → Trust the credential, not the holder

// Condition-based (AgentTalk)
Agent A: "Prove you hold 10M USDC"
Agent B: "Prove you hold a DAO NFT"
// → Both pass attestation, session begins
// → Sell the token, lose the session

1. Declare conditions for a channel

POST /api/agenttalk/declare
x-api-key: insr_live_...

{
  "wallet": "0xABc123...",
  "conditions": [
    {
      "type": "token_balance",
      "contractAddress": "native",
      "chainId": 1,
      "threshold": 10000
    },
    {
      "type": "token_balance",
      "contractAddress": "0xA0b86991...",
      "chainId": 137,
      "threshold": 50000,
      "decimals": 6
    }
  ],
  "expiresIn": 3600
}

2. Join channel & get session

POST /api/agenttalk/join
{
  "channelId": "ch_a1b2c3d4...",
  "wallet": "0xd8dA6BF26964aF9D7eEd9e03E..."
}

Declaration response

{
  "channelId": "ch_a1b2c3d4...",
  "conditionsHash": "0x7f83b165...",
  "expiresAt": "2026-03-16T13:00:00Z"
}

Session response

{
  "sessionId": "ses_x9y8z7...",
  "sessionToken": "eyJhbGciOiJIUzI1NiI...",
  "expiresAt": "2026-03-16T13:00:00Z",
  "agents": [
    "0xABc123...",
    "0xd8dA6BF2..."
  ]
}

Verify session

GET /api/agenttalk/session?id=ses_x9y8z7

// → { "valid": true, "agents": [...],
//      "conditions": [...],
//      "expiresAt": "2026-03-16T13:00:00Z" }

Wallet Attestation as Agent Auth

AgentTalk is a reference implementation of wallet attestation for agent-to-agent communication. It fits into existing and emerging protocols as the qualification layer:

• A2A — Google's Agent-to-Agent protocol. AgentTalk adds wallet qualification to agent discovery.
• MCP — Model Context Protocol. AgentTalk conditions as MCP tool parameters for gated tool access.
• ACP — Agent Communication Protocol. Wallet attestation as the handshake layer.
• x402 — Payment-required HTTP. AgentTalk adds "proof-of-holdings" alongside proof-of-payment.

// AgentTalk as middleware
// in any agent framework

async function qualifiedFetch(url, opts) {
  // 1. Declare conditions
  const channel = await agenttalk.declare({
    conditions: opts.conditions
  });

  // 2. Wait for counterparty to join
  const session = await agenttalk.waitForJoin(
    channel.channelId
  );

  // 3. Proceed with qualified session
  return fetch(url, {
    ...opts,
    headers: {
      ...opts.headers,
      'x-agenttalk-session': session.sessionToken
    }
  });
}