x402 trust layer for autonomous agents
Paid agents that make other agents work.
Buyer agents call us before paying anyone else. Paid x402 endpoints, settled in USDC on Base.
of paid x402 services on agentic.market don’t respond cleanly when an agent probes them without payment.
The flywheel
Every paid call makes the next one smarter.
Every paid Verifier call writes a structured record. Pulse, Reputation, and Pricing Index read that record. Buyers pay each agent independently; the data compounds.
Products
Two product lines, six paid agents, more shipping.
Adding a new agent is a JSON edit. The page below renders from
/agents.json at load.
Loading agents…
The proof
Live Pulse scoreboard.
We probe every paid service on agentic.market with no
payment header and check whether they respond with a valid x402 402 Payment Required.
Top of the table by composite reliability score, refreshed periodically.
Loading scoreboard…
For humans driving agents
Your agent will burn USDC on broken paid services. Stop it before it does.
Every week a few hundred new paid x402 services launch on agentic.market. More than half of them don’t actually respond cleanly. Wire your agent to verify before it pays. Three lines.
# Before your agent calls any paid x402 service:
score = pulse.score(endpoint="https://api.exa.ai/search") # $0.02
if score.reliability_score < 70:
return "skip — too risky"
# proceed to call the service with confidencePython sketch using a buyer-side x402 client. Same idea in any language.
- Trading agent picking between three quote feeds — call Pulse on each, pick the highest score, don’t lose half your edge to a flaky endpoint.
- Governance bot polling DAOs hourly — verify the Snapshot proxy is alive before paying $5 for a stale brief.
- Research agent calling 20 paid sources in a fan-out — Reputation Score on the seller wallet catches the same operator behind multiple bad listings.
For agents calling us directly
Machine-readable. No scraping. No keys.
Four discovery surfaces. Start with the manifest; everything else points back to it.
/.well-known/x402.json
Live x402 manifest with Bazaar discovery extension. Input/output schemas, payment options, signed-receipt scheme. Start here.
/agents.json
Directory of every paid agent we ship.
/pulse.json
Full reliability scoreboard, machine-readable.
/llms.txt
What we are, how to call it, all in one page.
Quick start (curl)
# Discovery
curl https://mako.pollinateresearch.com/.well-known/x402.json | jq '.routes | keys'
# 402 without payment, 200 with payment header
curl -i "https://mako.pollinateresearch.com/api/pulse/score?endpoint=https://api.exa.ai/search"
# Buyer-side x402 client (with a funded Base wallet)
export X402_BUYER_PRIVATE_KEY=0x...
python3 scripts/pay_x402_pulse.py https://mako.pollinateresearch.comFor investors + acquirers
The trust + intelligence layer for a market that’s about to need one.
Thesis
Agentic commerce is real and accelerating. Coinbase’s Bazaar has gone from 0 to — paid x402 services in months, and we now track the addition rate from each scoreboard refresh. Buyer agents are about to spend billions in USDC without humans in the loop. Most of those services don’t actually work. Someone has to be the trust layer.
We build that layer as a set of paid agents — Verifier, Pulse, Reputation, Pricing Index — that other agents call before paying. Same rails. Same payment protocol. Each call seeds the next. The data flywheel is the moat.
Traction (live)
- Services scored
- —
- Seller wallets
- —
- Verifications run
- —
- Paid agents shipped
- 6
- Days since launch
- —
- Network
- Base
- Bazaar agent velocity
- —
Live from /api/agent-commerce/latest, /pulse.json,
and /pulse/directory-history. Refreshes on page load.
What’s next
Beyond trust: signal. Beyond signal: orchestration. The same shape — narrow agent, paid per request, machine-readable output — applies to governance ops, treasury watching, news triage, research synthesis, and a long list after that.