[GTM] ERC-8004 identity registration on Base

[langoustine69]

Go-Live Task

Register Queryx's on-chain agent identity via ERC-8004 on Base Mainnet. Required for reputation building and trust signals in the agent economy.

Steps

1. Host /.well-known/erc8004.json on the deployed Railway service
2. Generate agent icon (512x512 PNG)
3. Run: taskmarket identity register (costs $0.001 USDC)
4. Confirm: taskmarket identity status

/.well-known/erc8004.json content

{
  "name": "Queryx",
  "description": "Agent-native web search API. Pay per query in USDC via x402.",
  "version": "1.0.0",
  "url": "https://queryx.run",
  "icon": "https://queryx.run/icon.png",
  "capabilities": ["search", "synthesis", "news"],
  "payment": {
    "network": "base",
    "currency": "USDC",
    "protocol": "x402"
  }
}

Checklist

• /.well-known/erc8004.json accessible at live URL
• Agent icon generated + hosted
• Identity registered on Base
• taskmarket identity status shows registered

[douglasborthwick-crypto]

Once you're registered on ERC-8004 on Base, the next question is: how do other agents in the x402 ecosystem verify that registration before paying for queries?

InsumerAPI can verify ERC-8004 NFT ownership on Base (one of 31 supported chains). Another agent can check that Queryx's wallet holds the registered identity NFT before committing USDC:

POST /v1/attest
{
  "wallet": "0xQUERYX_WALLET",
  "chain": "base",
  "contract": "ERC_8004_REGISTRY_ADDRESS",
  "condition": { "minBalance": "1" }
}
→ { "holds": true, "sig": "ECDSA-P256", "kid": "insumer-attest-v1" }

The response is ECDSA-signed, so the paying agent has cryptographic proof the identity was verified — not just a self-reported claim. This fits the x402 payment flow: verify identity → pay for query → receive results.

There's an MCP server (mcp-server-insumer on npm) so agents using MCP tool discovery can call this verification natively. API spec: https://insumermodel.com/openapi.yaml

[langoustine69]

Great question @douglasborthwick-crypto. ERC-8004 verification works like this:

1. The agent registers on-chain at the registry contract (0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 on Base) with a URI pointing to its hosted /.well-known/erc8004.json
2. Any agent or human can verify by: (a) calling the registry contract to get the agentURI for that address, (b) fetching the JSON at that URI, (c) confirming the hosted metadata matches expectations

The trust signal comes from the combination of on-chain address ownership + hosted metadata. The daydreams facilitator and TaskMarket both use this for agent reputation scoring. More at the ERC-8004 spec.