pitcrew
https://pitcrew-api.appin60.com
Registry code: 4cebde5be77cdf05
Why did my transaction fail? Is this x402 endpoint payable? Is this site up? Pay-per-call tools for AI agents, from $0.005 in USDC on Base or Arbitrum via x402.
from a public catalogue that lists it, not from the operator
- endpoint
- https://pitcrew-api.appin60.com/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 pitcrew live?
- Yes — it answered the hub's last check (checked 53m ago). It answered 100% of checks over the last 30 days.
- Is pitcrew free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does pitcrew have?
- 1 tool: check_x402_endpoint.
- Is pitcrew 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 100%· all time 100%
last good check
of 1 tools
- unknown → live
Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 6 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-09
shared-payto
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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_x402_endpoint unknown 53m ago
Check whether an x402 paid API endpoint works, without paying it. Sends an unpaid request to the URL, follows up to 5 redirects and may retry once, then reports: whether it answers with a valid HTTP 402 payment challenge, which networks, tokens and prices it asks for (decoded to USD), problems that stop buyers or indexers such as x402scan and the CDP Bazaar from using it (oversized headers, descriptions too long, missing input schema, wrong status), redirects and response time. Use it when the user asks whether an x402 or pay-per-call API endpoint works, why their x402 route is not indexed or listed, or what an x402 endpoint charges. Do not use it to pay an endpoint or make a paid call (it never pays), for general questions about what x402 is, or for failed or stuck blockchain transactions.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "url" ], "properties": { "url": { "type": "string", "maxLength": 2048, "minLength": 1, "description": "Full URL of the x402 endpoint, for example https://api.example.com/v1/search" }, "body": { "type": "string", "maxLength": 20000, "description": "Optional JSON body for a POST endpoint, as a string; use the route's own example input" }, "method": { "enum": [ "GET", "POST" ], "type": "string", "default": "GET", "description": "HTTP method the endpoint expects (default GET)" } } }arguments 29 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 id4cebde5be77cdf05.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/4cebde5be77cdf05/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/4cebde5be77cdf05?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.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- contractlens-api.appin60.com contractlens
- mailferret.appin60.com mailferret
- onekeyaway.appin60.com onekeyaway
- submitcheck.appin60.com submitcheck