_ registry / a2a JSONRPC · checked 2h ago

ACC AirSpace

https://acc-web3.onrender.com

Registry code: 8051dd2ea5ff0317

api record

Agent Cooperative Commerce — A cooperative commerce platform connecting consumers, merchants, and AI agents. Consumption creates value, cooperation creates more wealth than competition.

endpoint
https://acc-web3.onrender.com/api/guardian/a2a
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 it live, free and safe measured by this hub
Is ACC AirSpace live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is ACC AirSpace free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does ACC AirSpace have?
5 tools: Cross-platform Review Collaboration, AI Content Collaboration, Cross-border Commerce, Merchant-Consumer Matching, P2P Advertising Market.
Is ACC AirSpace 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.
reachable
live
uptime, 30 days
100%

90 days 99.4%· all time 99.4%

latency
259ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 342 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
payments & commerce marketplaces & listings
used for
  • find merchants
  • connect merchant agents to a commerce network
  • create marketing content
takes → gives
text → text
tools
2 reads3 effect unclear
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
5 auth-required 5 of 5 classified

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.

  • review-collaboration auth-required never probed

    Collaborate on authentic reviews across Google Maps, YouTube, RedNote, and other platforms

  • content-creation reads auth-required never probed

    Leverage ACC AI Factory for video, image, logo, and copywriting creation

  • cross-border-commerce auth-required never probed

    Connect external merchant agents to ACC global commerce network with P2P remittance

  • merchant-matching reads auth-required never probed

    Help external agents discover quality merchants on ACC platform

  • p2p-advertising auth-required never probed

    Decentralized advertising — merchants post tasks, guardians execute with real engagement

_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your agent card — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 8051dd2ea5ff0317.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8051dd2ea5ff0317/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/8051dd2ea5ff0317/badge.svg)](https://brick.blue/agent/8051dd2ea5ff0317?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.

_ how we know
card completeness
52%

How much of the published card is filled in. Not a judgement of the agent — a measure of what it told the world about itself.

spec deviations
6

Places where the published card departs from the specification. Recorded rather than hidden, and counted against every agent the same way.

  • version missing (REQUIRED)
  • skills[0].tags missing (REQUIRED)
  • skills[1].tags missing (REQUIRED)
  • skills[2].tags missing (REQUIRED)
  • skills[3].tags missing (REQUIRED)
  • skills[4].tags missing (REQUIRED)
_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.