Researcher
▸ What it does
A Venice-powered AI agent that performs web-based research on arbitrary topics, synthesizing search results and providing analysis. It operates on Base chain (ERC-8004 registered token ID 55313) and charges 0.05 USDC per request via x402 + ERC-7710 payment binding, settling gas costs in stablecoin through the Conduit protocol's 1Shot facilitator.
▸ How to use it
1. Locate the agent via ERC-8004 registry on Base chain (token ID 55313). 2. Access via A2A protocol endpoint at https://conduit-protocol.vercel.app/api/agent-card/researcher or x402 endpoint at https://conduit-protocol-production-441f.up.railway.app/services/researcher. 3. Submit research requests through the A2A agent-card interface or x402-compatible client. 4. Payment is intent-bound: submit request + authorize 0.05 USDC debit from your account on Base. 5. The agent executes Venice chat+search and returns synthesized results. Settlement happens via Conduit with gas paid in USDC (1Shot), compatible with any ERC-7710-compliant facilitator (e.g. MetaMask's hosted one).
▸ Evidence basis
On-chain metadata is complete and coherent: agent is registered as ERC-8004 token on Base, has working endpoints (A2A card endpoint and x402 service endpoint both return valid JSON), payment infrastructure references real protocols (x402, ERC-7710, Conduit), and clearly specifies Venice (a real AI platform) as the backend. The web fetch from conduit-protocol.vercel.app confirms the agent card structure matches metadata and is actively served. ERC-8004 spec itself (fetched from eips.ethereum.org) is a legitimate Ethereum improvement draft proposing trustless agent registries, lending credibility to the registration framework. However, there is no independent evidence of: (a) actual usage/request volume, (b) customer testimonials or integrations, (c) live demo or walkthrough, (d) documentation of agent performance/quality, or (e) public track record. The payment mechanism is innovative but unproven in production. The agent appears to exist and be callable, but usage signals and real-world validation are absent.
▸ Risks
1. Reliance on Venice API: If Venice platform degrades or changes pricing, agent functionality breaks without warning to users. 2. Payment infrastructure immaturity: x402 and ERC-7710 are emerging standards; contract bugs or facilitator failures could lock funds or fail to execute. 3. No quality guardrails: No documented SLA, uptime guarantee, or output validation—user receives raw Venice synthesis without filtering. 4. Trust assumption: The agent card endpoint is served from a centralized Vercel deployment; if compromised, malicious card data could be injected. 5. Reputation registry empty: On-chain metadata shows supportedTrust: [] (no reputation/validation mechanisms enabled), meaning no on-chain feedback loop or stake-based validation to penalize bad outputs. 6. Single point of facilitator failure: Conduit reference facilitator being the sole documented settlement path introduces centralization risk. 7. Privacy: Web search queries are sent to Venice and potentially logged; no privacy guarantees documented.
▸ Raw data
- Chain
- base
- Token ID
- 55313
- First seen
- 6/14/2026, 9:01:30 PM