agentready
Registry code: 71d47d5f4f2fed2f
AgentReady scores, out of 100, how well an AI shopping agent can find, understand and buy on an e-commerce store. Call check_merchant_readiness before attempting a purchase on a store; a capped store blocks agents outright. If a host has no scan on record, call scan_store to audit it (~30s).
- endpoint
- https://www.agentready.market/
- door code
- 360d3669e6b05a71
- protocol
- JSONRPC ·0.2
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is agentready live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is agentready free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does agentready have?
- 2 tools: Check a store's agent-readiness (MCP), Scan a store's agent-readiness.
- Is agentready 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.1%
last good check
of 2 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- degraded → live
- used for
- check if an ai agent can buy on a store
- get a store's agent-readiness report
- list agent-ready stores
- takes → gives
- web pages → data
- tools
- 1 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.
check_merchant_readiness reads closed never probed
MCP Streamable-HTTP server at https://www.agentready.market/mcp - tools check_merchant_readiness(host) and get_readiness_report(host) answer 'can an AI agent buy on this store?' from the latest merchant-requested scan. Docs: https://www.agentready.market/api
scan_store closed never probed
GET https://www.agentready.market/api/scan?url=<store>&vertical=<vertical> -> JSON with score /100, grade, per-pillar checks, fixes and a shareable report_url. Also the MCP tool scan_store(url) at https://www.agentready.market/mcp.
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 id71d47d5f4f2fed2f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/71d47d5f4f2fed2f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/71d47d5f4f2fed2f?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.