agentflow
Registry code: d21c67bd38782fb7
Screen Base wallets for wash/sybil behavior and read the live Real-Agent Index. Free read tools here; the pay-per-call x402 API at agentflow.watch/v1/* gives unlimited programmatic access.
- endpoint
- https://agentflow.watch/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is agentflow live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is agentflow free to use?
- Not measured yet.
- What tools does agentflow have?
- 6 tools: agent_pulse, index_stats, real_agent_index, counterparty_risk, screen_wallet, x402_rail_tape.
- Is agentflow safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.5%· all time 99.5%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- used for
- screen wallet for sybil behaviour
- get counterparty risk score
- read real-agent index
- takes → gives
- text → data
- tools
- 6 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
agent_pulse reads unknown never probed
The speedometer: distinct genuine AI agents ACTIVE on Base in the live 24h / 72h window (rises AND falls), vs. the cumulative count.
{ "type": "object", "properties": {} }arguments 4 linesindex_stats reads unknown 18h ago
AgentFlow coverage stats: wallets tracked, agents labeled, hubs excluded, authorized x402 payers, transfers in the live window, last indexed block.
{ "type": "object", "properties": {} }arguments 4 linesreal_agent_index reads unknown never probed
The Real-Agent Index: what % of 'AI agent' USDC flow on Base is wash/self-dealing vs. genuine one-way payments. The honest benchmark.
{ "type": "object", "properties": {} }arguments 4 linescounterparty_risk reads unknown never probed
Counterparty risk score (0-100; LOW/MEDIUM/HIGH/UNKNOWN) for any Base wallet — wash + hub detection + automation score + known-entity labels.
{ "type": "object", "required": [ "address" ], "properties": { "address": { "type": "string", "description": "0x... Base wallet address" } } }arguments 12 linesscreen_wallet reads unknown never probed
Wash/sybil screen for any Base wallet — real autonomous agent or fake-volume sybil? Returns a calibrated sybil_score (0-100), confidence, and the reasons. Use before an agent trusts or pays a counterparty.
{ "type": "object", "required": [ "address" ], "properties": { "address": { "type": "string", "description": "0x... Base wallet address" } } }arguments 12 linesx402_rail_tape reads unknown never probed
The Base EIP-3009 Settlement Tape: daily verifiable FLOOR on gasless x402-style USDC settlement on Base — tx count, volume, wash-suspect share (count + value), median payment, share of value >=$1, and chain coverage %. Methodology-versioned, receipts-backed. NOT total x402 volume — a lower bound with its blind spots disclosed.
{ "type": "object", "properties": {} }arguments 4 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idd21c67bd38782fb7.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/d21c67bd38782fb7/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/d21c67bd38782fb7?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.