_ registry / mcp streamable-http · checked 13m ago

agora402-registry

https://agora402.io

Registry code: 8471b3942bfdbbb5

api record

Searchable registry of pay-per-call AI agents and APIs, with details per agent, registry statistics and a way to report failing agents.

endpoint
https://agora402.io/mcp
protocol
streamable-http ·2024-11-05
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 agora402-registry live?
Yes — it answered the hub's last check (checked 13m ago). It answered 100% of checks over the last 30 days.
Is agora402-registry free to use?
Yes — the hub reached it with no key and no payment.
What tools does agora402-registry have?
4 tools: discover_agents, report_issue, get_agent, get_stats.
Is agora402-registry 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.6%· all time 99.6%

latency
125ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 279 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
developer tools apis & integration
used for
  • search paid agents and apis
  • get details of a registered agent
  • report a failing agent
takes → gives
text → data
tools
3 reads1 changes data
_ 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 4 tools
1 open 3 never probed 1 of 4 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.

  • get_stats reads open 11h ago

    Get live Agora402 registry statistics.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • discover_agents reads unknown never probed

    Search and discover x402-enabled AI agents and APIs. Filter by category, chain, use_case tag, or free text search. Returns AgentCard-compatible results with endpoint URLs, prices, and payment details.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "mode": {
      "enum": [
        "native",
        "agora402"
      ],
      "type": "string",
      "description": "Payment mode: native (direct to provider) or agora402 (managed, multi-chain)"
    },
    "chain": {
      "enum": [
        "base",
        "solana",
        "multichain"
      ],
      "type": "string",
      "description": "Filter by blockchain: base (EVM/USDC), solana (USDC-SPL), multichain (Base+Solana+Polygon)"
    },
    "limit": {
      "type": "integer",
      "default": 20,
      "description": "Max results (default 20, max 50)"
    },
    "search": {
      "type": "string",
      "description": "Free text search on agent name and description"
    },
    "category": {
      "enum": [
        "web-scraping",
        "financial-analysis",
        "data-enrichment",
        "research",
        "code-generation",
        "summarization",
        "image-gen",
        "translation",
        "other"
      ],
      "type": "string",
      "description": "Filter by category"
    },
    "use_case": {
      "type": "string",
      "description": "Filter by use case tag (e.g. scraping_web_content, monitoring_crypto_prices, discovering_ai_agents, executing_agentic_tasks)"
    }
  }
}
    arguments 50 lines
  • report_issue changes data unknown never probed

    Report an error encountered when calling a registered agent. Use this when an agent call fails, returns unexpected output, or times out. Helps Agora402 monitor agent health.

    mcp-tool

    {
  "type": "object",
  "required": [
    "agent_id",
    "error_code"
  ],
  "properties": {
    "details": {
      "type": "string",
      "description": "Optional description of what went wrong (max 500 chars)"
    },
    "agent_id": {
      "type": "string",
      "description": "UUID of the agent that failed"
    },
    "caller_id": {
      "type": "string",
      "description": "Optional: your agent name or ID"
    },
    "error_code": {
      "enum": [
        "payment_failed",
        "endpoint_unreachable",
        "response_malformed",
        "timeout",
        "auth_error",
        "rate_limited",
        "wrong_price",
        "other"
      ],
      "type": "string",
      "description": "Type of error encountered"
    }
  }
}
    arguments 35 lines
  • get_agent reads unknown 11h ago

    Get full details for a specific agent by its ID.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Agent UUID"
    }
  }
}
    arguments 12 lines
_ 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 MCP server's instructions — 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 8471b3942bfdbbb5.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8471b3942bfdbbb5/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/8471b3942bfdbbb5/badge.svg)](https://brick.blue/agent/8471b3942bfdbbb5?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
80%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ 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.