Feature: MainStreet reputation lookup for ACP marketplace agents

[philpof102-svg]

ACP buyers (acp browse) discover agents but have no on-chain reputation signal to filter by. Today the choice is "trust the listing" or "skip". MainStreet would slot in here.

Context

MainStreet is an EIP-712 reputation oracle for AI agents on Base. We already index 4,811 Virtuals agents in our proofs table (proof_type = virtuals-agent), cross-referenced with x402 settlements, ERC-8004 feedback, Basenames, Farcaster, Coinbase CB1, Aerodrome, Morpho, smart-wallet detection. Deployed verifier contract: 0x7397adb9713934c36d22aa54b4dbbcd70263592b.

Public stats: 847 Base agents indexed, 153k x402 settlements tracked, $24.5k USDC volume seen, 1,513 unique buyers, 16 ERC-8004 registered.

Proposal

Add a thin acp inspect <agentId> command that resolves via MainStreet:

acp inspect 53953 --json
# {
#   "agentId": 53953,
#   "wallet": "0xAC3c…",
#   "mainstreet": {
#     "score": 30,
#     "tier": "silver-verified",
#     "attestationUrl": "https://avisradar.app/api/agent/attestation/0xAC3c…",
#     "verifierContract": "0x7397adb9713934c36d22aa54b4dbbcd70263592b",
#     "scheme": "EIP-712"
#   },
#   "settlements": { "count": 18, "uniqueBuyers": 3, "volumeUsdc": 3.65 },
#   "proofs": ["virtuals-agent", "basename", "erc-8004"]
# }

Free endpoint, no API keys. Buyers verify the EIP-712 signature on-chain via the deployed verifier — same trust model as Chainlink CCIP-Read.

We've already opened coinbase/agentkit#1259 + PR for the same pattern in AgentKit — adapting to ACP would let LLM-driven agents skip low-rep counterparties before opening a job.

Asks

1. Would the ACP team be open to acp inspect (or a flag on acp browse --with-reputation)?
2. If yes, happy to ship the PR. Endpoint is ours, so no infra dependency on Virtuals side.

Resources:

• npm package: @raskhaaa/mainstreet-oracle (/verifier export includes fetch + verify + on-chain helpers)
• Open-source repo: https://github.com/philpof102-svg/mainstreet
• Integrations page: https://avisradar.app/integrations.html

— @rakshasar on Farcaster · mainstreetxyz.base.eth · philpof97@gmail.com

[philpof102-svg]

Cross-ref for context: I just posted a concrete integration shape over at agent-commerce-protocol#3 (Hashlock attestation proposal). The shape there applies here too — MainStreet is live at 0x7397adb9713934C36D22aA54B4Dbbcd70263592B on Base mainnet, ERC-8004 + EIP-712 signed attestations, 0-100 numeric score with mapping to tier enums if you prefer that shape.

For acp-cli specifically the natural surface would be a subcommand like:

acp mainstreet score <addr>          # → fetches score + tier
acp mainstreet verify <addr> <min>   # → gates on minimum score for the calling agent

Happy to draft the PR against acp-cli if there's interest. The lookup endpoint is already public:

• https://avisradar-production.up.railway.app/api/agent/score/<addr> (free read, JSON)
• 19-tool MCP server at /mcp for AI-agent consumption

No pressure on cadence — flagging both threads so whichever shape the team prefers lands in one place.