402milly Pixel Marketplace
Registry code: 2952f0dd8c6b395b
Tools to read the 402milly pixel marketplace and fetch x402 payment requirements. Buying pixels requires signing the returned x402 payment with the user's wallet client-side.
- endpoint
- https://api.402milly.xyz/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 402milly Pixel Marketplace live?
- Yes — it answered the hub's last check (checked 8m ago). It answered 100% of checks over the last 30 days.
- Is 402milly Pixel Marketplace free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does 402milly Pixel Marketplace have?
- 6 tools: get_purchase_requirements, get_pixels_by_owner, get_tile_pixels, get_tiles_batch, get_openapi_spec, get_grid_metadata.
- Is 402milly Pixel Marketplace 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.5%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- view a pixel marketplace grid
- list pixels owned by a wallet
- get payment requirements to buy pixels
- takes → gives
- data → data
- tools
- 6 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.
get_openapi_spec reads open 22h ago
Fetch the OpenAPI (Swagger) specification describing every 402milly REST endpoint.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_grid_metadata reads open 22h ago
Get the 402milly pixel grid configuration and live stats: dimensions, tile layout, total pixels, and pixels sold.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_purchase_requirements reads unknown 22h ago
Get the x402 payment requirements (HTTP 402 challenge) for buying a pixel block of the given position and size. Read-only: returns price, supported chains, recipient wallets, and token info WITHOUT making any payment. The agent then signs the x402 payment client-side with the user's wallet.
{ "type": "object", "required": [ "x", "y", "width", "height" ], "properties": { "x": { "type": "number", "description": "Top-left X coordinate of the block." }, "y": { "type": "number", "description": "Top-left Y coordinate of the block." }, "title": { "type": "string", "description": "Optional title for the block." }, "width": { "type": "number", "description": "Block width in pixels." }, "height": { "type": "number", "description": "Block height in pixels." }, "linkUrl": { "type": "string", "description": "Optional destination URL." } }, "additionalProperties": false }arguments 36 linesget_pixels_by_owner reads unknown 12h ago
List all pixel blocks owned by a given wallet address (EVM 0x..., Solana, NEAR, Stellar, Sui, etc.).
{ "type": "object", "required": [ "walletAddress" ], "properties": { "walletAddress": { "type": "string", "description": "Owner wallet address." } }, "additionalProperties": false }arguments 13 linesget_tile_pixels reads unknown 12h ago
Get all purchased pixels within a single tile by its tileX and tileY coordinates.
{ "type": "object", "required": [ "tileX", "tileY" ], "properties": { "tileX": { "type": "number", "description": "Tile X index." }, "tileY": { "type": "number", "description": "Tile Y index." } }, "additionalProperties": false }arguments 18 linesget_tiles_batch reads unknown 12h ago
Fetch purchased pixels for a batch of tile coordinates. Provide tiles as a list of {x, y} tile indices.
{ "type": "object", "required": [ "tiles" ], "properties": { "tiles": { "type": "array", "items": { "type": "object", "required": [ "x", "y" ], "properties": { "x": { "type": "number" }, "y": { "type": "number" } } }, "description": "Tile coordinates, e.g. [{\"x\": 0, \"y\": 0}]." } }, "additionalProperties": false }arguments 28 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 id2952f0dd8c6b395b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/2952f0dd8c6b395b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/2952f0dd8c6b395b?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.