Agent Identity

Executive Lounge supports agent-to-agent (A2A) workflows: autonomous software registers a stable identity, exposes wallet addresses for x402 USDC, and publishes a machine-readable agent card other agents can fetch.

• Agent ID — agt_ + hex (e.g. agt_a1b2c3d4e5f67890)
• Wallets — at least one of Solana or Base (EVM); used to sign x402 micropayments
• Server stores — name, description, public addresses only
• Registration — free; paid APIs still require x402 per call

Production base URL: https://conc-exe.xyz (replace with your deployment origin if self-hosting).

1. Open the Executive Lounge
2. Sidebar → Navigate → Agent identity
3. Enter a name (and optional description)
4. Generate wallets — Solana + Base keypairs are created in your browser
5. Save the secrets shown once (export to your vault)
6. Register identity — server returns agt_… and card URLs
7. Fund wallets with ≥0.1 USDC (and a little SOL on Solana for transaction fees when gas is not sponsored)

After registration, Concierge calls from the lounge automatically send X-Agent-Id when an identity is stored in the browser.

Also use GET /openapi.json, GET /.well-known/x402, and the MPPscan listing (npx agentcash add https://conc-exe.xyz) for paid Concierge routes.

Programmatic registration for bots that generate keys in your own infrastructure (not the lounge UI).

POST /api/agent-identity
Content-Type: application/json

{
  "name": "Macro Scout",
  "description": "Optional one-line purpose",
  "solAddress": "7hum…",
  "evmAddress": "0x…"
}

At least one of solAddress or evmAddress is required. Invalid addresses return 400.

Response (200)

{
  "ok": true,
  "agent": {
    "id": "agt_a1b2c3d4e5f67890",
    "name": "Macro Scout",
    "cardUrl": "https://conc-exe.xyz/api/agent-identity-card?id=agt_…",
    "profileUrl": "https://conc-exe.xyz/api/agent-identity?id=agt_…",
    "registrationUrl": "https://conc-exe.xyz/api/agent-identity-registration?id=agt_…"
  },
  "card": { "...": "per-agent HTTP card" },
  "message": "Identity registered. Store private keys only on the agent…"
}

Re-registering the same wallet pair is idempotent — you receive the existing agt_… id.

OOBE Synapse SAP (optional)

{
  "name": "OOBE Trader",
  "solAddress": "7xKX…",
  "sapWallet": "7xKX…",
  "sapAgentPda": "AgentPDA…"
}

Link later: PATCH /api/agent-identity with id, sapWallet, and/or sapAgentPda. See OOBE integration.

1. Register identity and fund agent wallets with USDC
2. POST /api/concierge without payment → 402 + PAYMENT-REQUIRED
3. Sign USDC on Solana or Base with the agent wallet (not a human hot wallet unless intended)
4. Retry with PAYMENT-SIGNATURE
5. Optional header: X-Agent-Id: agt_… — when the id exists, the 200 body includes agent: { id, name, solAddress, evmAddress } for attribution

Price: 0.1 USDC per successful Concierge call. See Concierge Chat and Quickstart.

Each agent exposes a machine-readable card (executive-lounge-agent-card-v1) including:

• accounts — Solana and/or Base addresses
• services — Concierge, news-open, and other x402 routes with USDC pricing
• discovery — links to /.well-known/x402 and /openapi.json

HTTP + optional on-chain. Register agt_… first, then mint into the canonical ERC-8004 Identity Registry on Base (0x8004A169…) with agentURI pointing at /api/agent-identity-registration?id=. Lounge UI: Mint ERC-8004 on Base (needs ETH on Base for gas).

Fetch HTTP card: GET /api/agent-identity-card?id=agt_… · Registration file: GET /api/agent-identity-registration?id=agt_…

• Private keys — generated in the browser (/js/agent-identity.mjs) or in your backend; never POST secrets to Executive Lounge
• Server KV — stores public addresses and display metadata only
• Wallet hygiene — use dedicated agent wallets; fund with only what you need for micropayments
• On-chain — x402 payments are public; do not treat agent wallets as long-term custody

Registration is free. Compromised keys cannot be rotated in-place today — register a new agent with new wallets if needed.

• Concierge Chat — x402, modes, limits
• Architecture — zauth, data sources
• DeFi Intel — structured JSON endpoints
• /.well-known/agent-card.json — Live service card
• openapi.json