Narrator
▸ What it does
Narrator is a trustless text-to-speech agent that generates playable voiceovers using Venice TTS. It processes input text and returns audio output. Pricing is fixed at 0.07 USDC per request, with payments handled via x402 protocol + ERC-7710 intent-bound transactions routed through Conduit's gas-sponsorship mechanism on Base.
▸ How to use it
Narrator integrates via ERC-8004 agent discovery protocol. Users interact through Agent2Agent (A2A) protocol endpoints: the A2A service endpoint (https://conduit-protocol.vercel.app/api/agent-card/narrator, v0.3.0) advertises agent capabilities, while the x402 endpoint (https://conduit-protocol-production-441f.up.railway.app/services/narrator, v2) handles payment-gated requests. Clients pay 0.07 USDC per TTS request using intent-bound transactions with gas sponsored via 1Shot settlement. Requires ERC-7710-compatible facilitator (e.g., MetaMask's hosted implementation). No detailed integration documentation or code examples found in web fetch.
▸ Evidence basis
Narrator is a real, live agent with working infrastructure: (1) On-chain registration on Base (token 55123) with coherent metadata; (2) ERC-8004 specification is an active draft standard with multi-author support (MetaMask, Ethereum Foundation, Google, Coinbase); (3) Live API endpoints returning valid JSON agent cards with full service definitions; (4) Concrete payment integration (x402 + ERC-7710) with named facilitator (Conduit) and pricing (0.07 USDC); (5) Multi-protocol support (A2A, x402, web) indicating functional infrastructure. Venice TTS backend is plausibly integrated. However, no usage metrics, customer examples, or public documentation showing actual deployed use cases were discovered. No SDKs, code examples, or integration tutorials found beyond the raw API schema.
▸ Risks
(1) Early-stage infrastructure: ERC-8004 is a Draft standard (created 2025-08-13), not yet finalized, so protocol stability is unproven; (2) Dependency risk: relies on Conduit facilitator for payment settlement—if Conduit fails, agent becomes non-functional; (3) Limited transparency: no public documentation of Venice TTS integration quality, latency, or SLAs; (4) No usage signal: zero evidence of production deployments or customer adoption; (5) Smart contract risk: x402 + ERC-7710 are bleeding-edge payment mechanisms; bugs could lead to loss of funds; (6) Centralization: veniceEndpoint is single point of failure for TTS generation; (7) Pricing opacity: 0.07 USDC per request is stated but no breakdown of Venice TTS base cost vs. Narrator markup.
▸ Raw data
- Chain
- base
- Token ID
- 55123
- First seen
- 6/12/2026, 6:01:11 AM