_ registry / mcp streamable-http · checked 1h ago

x402aff-docs

https://www.x402aff.xyz

Registry code: 5fe30127a893878b

api record

Read-only answers about x402aff, the builder-code affiliation kit for x402 sellers on Base. Use get_install_instructions to integrate it, get_integration_docs for configuration and payouts, search_faq for common questions, and get_security_model for what protects a split. Nothing here moves funds or needs credentials.

endpoint
https://www.x402aff.xyz/api/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 it live, free and safe measured by this hub
Is x402aff-docs live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is x402aff-docs free to use?
Yes — the hub reached it with no key and no payment.
What tools does x402aff-docs have?
4 tools: get_integration_docs, get_install_instructions, get_security_model, search_faq.
Is x402aff-docs 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 100%· all time 100%

latency
262ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
3 open 1 never probed 3 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_install_instructions open 1h ago

    Get the install command, server wiring code, and buyer-side one-liner for adding x402aff builder-code affiliation to an x402 seller, in TypeScript or Python. Use this when a user wants to integrate x402aff.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "language": {
          "enum": [
            "typescript",
            "python"
          ],
          "type": "string",
          "description": "SDK language. Defaults to typescript."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_security_model open 1h ago

    Get what protects money sitting in an x402aff split: the attacks tested against live Base mainnet on a fork and their results, plus the two canonical contracts the kit reads.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "part": {
          "enum": [
            "all",
            "attacks",
            "contracts"
          ],
          "type": "string",
          "description": "Which part to return. Defaults to all."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • search_faq open 1h ago

    Search the x402aff FAQ (networks, private keys, unknown builder codes, gas, whether the s tag is proof, payout rounding, RPC choice). Returns the matching questions with answers; an empty query returns all of them.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "Words to match against questions and answers."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • get_integration_docs unknown never probed

    Read one section of the x402aff developer docs: quickstart, buyer, builder_code_check (X-Builder-Code-Status and on-chain self-checks), payment_flow, configuration (builder share bps, RPC, multiple recipients), payouts (release, pending, claims dashboard), discovery (SQL for every kit payment), other_languages (porting to Go or Rust), or good_to_know (caveats).

    mcp-tool

    {
      "type": "object",
      "required": [
        "topic"
      ],
      "properties": {
        "topic": {
          "enum": [
            "quickstart",
            "buyer",
            "builder_code_check",
            "payment_flow",
            "configuration",
            "payouts",
            "discovery",
            "other_languages",
            "good_to_know"
          ],
          "type": "string",
          "description": "Which section to read."
        }
      },
      "additionalProperties": false
    }
    arguments 24 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 5fe30127a893878b.

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