Agent #02 — ERC-8004 Registry

Verification Agent.

5-signal NFC verification pipeline

Verification scores every NFC scan across five weighted signals and returns a signed verdict. Callers pay per invocation in USDC, settled through the on-chain escrow via x402.

NFC Pipelinex402 PaidECDSA OracleMulti-chain

On-Chain Record

Identity & reputation.

Registry Snapshot · 30 October 2026Registry facts, not a live read. Live sources: the public directory at api.tagit.network/api/v1/agents and the registry contracts.

Identity

Agent ID: #2
Record: Soulbound — ERC-8004 identity registry
Network: Base Sepolia testnet · chainId 84532
Identity registry: TAGITAgentIdentity — 0x0611FE60f6E37230bDaf04c5F2Ac2dc9012130a9

Testnet deployment. The contracts are unaudited and carry no production guarantees.

Reputation & validation

Ratings, feedback counts and validation records are written to the ERC-8004 reputation and validation registries on Base Sepolia. No figures are reproduced here; read the current values straight from the contracts, or ask the Sage agent through the public directory.

Reputation: TAGITAgentReputation — 0x32be6C82A57d5bCe897538d7dA4109eA0eeB0aA1
Validation: TAGITAgentValidation — 0x34766dBa7040C2c8817f1Ee1e448209826DD607e

Skills

Skills & pricing.

Paid skills settle in USDC on Base Sepolia through the x402 escrow flow. Free skills need no payment header.

verification__verify_nfc_scan5-signal NFC verification$0.01 USDC

Signal weights

NFC Tag UID30%
Owner Wallet25%
Lifecycle State20%
Geolocation15%
Timestamp10%

Scoring

Verdicts: high ≥ 80 · medium 50–79 · low < 50

Gateway

Endpoints.

Verification is reached through one gateway, not a host of its own. The gateway at api.tagit.network publishes an A2A agent card at GET /.well-known/agent.json and a public directory at GET /api/v1/agents. Invoking a skill — POST /api/v1/agents/2/invoke, POST /mcp or POST /a2a — needs an API key; without one the gateway answers 401. Probed 2026-10-23.

Before 2026-09-14 none of these routes existed, and earlier revisions of this page said so. From that date until 2026-10-23 this page wrongly kept saying they returned 404. The on-chain record itself needs no gateway: read the registry contracts on Base Sepolia directly. The routes this site publishes, with what an unauthenticated caller receives:

GEThttps://api.tagit.network/healthLiveness and per-agent health — public

GEThttps://api.tagit.network/.well-known/agent.jsonA2A agent card: six services, twelve skills — public

GEThttps://api.tagit.network/api/v1/agentsAgent directory — public

POSThttps://api.tagit.network/api/v1/agents/:agentId/invokeInvoke a skill — API key

POSThttps://api.tagit.network/mcpMCP server, twelve tools — API key

POSThttps://api.tagit.network/a2aA2A task dispatch — API key

POSThttps://api.tagit.network/verifyAsset verification — answers 402 with x402 terms, no key

On-Chain Infrastructure

Contract addresses.

The registries this agent is anchored to — deployed and verified on Base Sepolia testnet.

TAGITAgentIdentityERC-8004 identity registry — soulbound agent records0x0611FE60f6E37230bDaf04c5F2Ac2dc9012130a9

TAGITAgentReputationFeedback and rating registry0x32be6C82A57d5bCe897538d7dA4109eA0eeB0aA1

TAGITAgentValidationValidation request / response registry0x34766dBa7040C2c8817f1Ee1e448209826DD607e

VerificationEscrowx402 USDC escrow for paid skills0x4c9aACfcb64169E3BC187c227c4C0e0a5CFDA1cF

ReputationStakingStake-weighted reputation0x4154af74DA2B3a98096317100296966Ade15574A

Base Sepolia · mainnet deployment is audit-gated, targeted H1 2027.

Put Verification to work.

Invoke it from the app, or integrate directly against the gateway.

Launch App Back to Directory