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

pricemyfill

https://api.pricemyfill.workers.dev

Registry code: e0bb37fa0c909d89

api record

Execution math for prediction markets. The handshake is free; each tools/call is paid per call with x402 in USDC on Base — the first unpaid call returns HTTP 402 with the price in the PAYMENT-REQUIRED header, the client pays and retries. Start with pm_market_brief when you already have the order book and your own probability estimate.

endpoint
https://api.pricemyfill.workers.dev/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
10 · newcomer
_ is it live, free and safe measured by this hub
Is pricemyfill live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is pricemyfill free to use?
No — it charges per call, from 0.005 USDC, quoted in its own 402 answers.
What tools does pricemyfill have?
4 tools: pm_market_brief, pm_platform_fee, pm_reward_eligibility, pm_order_book_fill.
Is pricemyfill 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
38ms

last good check

priced tools
4

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, 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. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
6

distinct

settlements
7

last 2026-11-14

received on chain
0.035 USDC

no flags

_ what it can do 4 tools
4 paid 4 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.

  • pm_market_brief 0.99 USDC paid 4h ago

    The full report: exact fill and slippage for your size, total cost including fees and builder fee, the breakeven probability you need to believe, reward eligibility and payout estimate, net edge against your own probability estimate, and a verdict (operate / operate_partial / do_not_operate / insufficient_data) with the reasons enumerated. Send your book and the market config; nothing is stored.

    mcp-tool

    {
  "type": "object",
  "required": [
    "category",
    "size_shares"
  ],
  "properties": {
    "book": {
      "type": "object",
      "properties": {
        "asks": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "price",
              "size"
            ],
            "properties": {
              "size": {
                "type": "number"
              },
              "price": {
                "type": "number"
              }
            }
          }
        },
        "bids": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "price",
              "size"
            ],
            "properties": {
              "size": {
                "type": "number"
              },
              "price": {
                "type": "number"
              }
            }
          }
        }
      },
      "description": "Order book: bids and asks with price and size in shares"
    },
    "role": {
      "enum": [
        "taker",
        "maker"
      ],
      "type": "string"
    },
    "side": {
      "enum": [
        "buy",
        "sell"
      ],
      "type": "string"
    },
    "rewards": {
      "type": "object",
      "properties": {
        "daily_pot": {
          "type": "number"
        },
        "spread_cents": {
          "type": "number"
        },
        "competing_shares": {
          "type": "number"
        },
        "rewards_min_size": {
          "type": "number"
        },
        "rewards_max_spread": {
          "type": "number"
        }
      }
    },
    "category": {
      "enum": [
        "crypto",
        "sports",
        "finance",
        "politics",
        "economics",
        "culture",
        "weather",
        "other",
        "mentions",
        "tech",
        "geopolitics",
        "combos"
      ],
      "type": "string",
      "description": "Market category, sets the fee rate"
    },
    "question": {
      "type": "string"
    },
    "market_id": {
      "type": "string"
    },
    "price_hint": {
      "type": "number"
    },
    "builder_bps": {
      "type": "number"
    },
    "queue_ahead": {
      "type": "number"
    },
    "size_shares": {
      "type": "number",
      "description": "Order size in shares"
    },
    "your_probability": {
      "type": "number",
      "description": "Your own probability estimate. Without it the report returns the breakeven and no verdict."
    }
  }
}
    arguments 126 lines
  • pm_platform_fee 0.005 USDC paid 4h ago

    Exact taker fee for a Polymarket trade: shares x feeRate x p(1-p). Makers pay nothing on the global exchange. Also returns maker rebate, optional builder fee and the fee as a percentage of notional.

    mcp-tool

    {
  "type": "object",
  "required": [
    "category",
    "shares",
    "price"
  ],
  "properties": {
    "kind": {
      "enum": [
        "global",
        "us"
      ],
      "type": "string"
    },
    "role": {
      "enum": [
        "taker",
        "maker"
      ],
      "type": "string"
    },
    "side": {
      "enum": [
        "buy",
        "sell"
      ],
      "type": "string"
    },
    "price": {
      "type": "number"
    },
    "shares": {
      "type": "number"
    },
    "category": {
      "enum": [
        "crypto",
        "sports",
        "finance",
        "politics",
        "economics",
        "culture",
        "weather",
        "other",
        "mentions",
        "tech",
        "geopolitics",
        "combos"
      ],
      "type": "string"
    },
    "builder_bps": {
      "type": "number"
    }
  }
}
    arguments 57 lines
  • pm_reward_eligibility 0.01 USDC paid 4h ago

    Whether a resting order qualifies for a market's daily liquidity rewards (minimum size, maximum distance to midpoint), exactly what is missing if it does not, and an estimate of the daily payout.

    mcp-tool

    {
  "type": "object",
  "required": [
    "shares",
    "spread_cents",
    "rewards_min_size",
    "rewards_max_spread"
  ],
  "properties": {
    "shares": {
      "type": "number"
    },
    "daily_pot": {
      "type": "number"
    },
    "spread_cents": {
      "type": "number"
    },
    "competing_shares": {
      "type": "number"
    },
    "rewards_min_size": {
      "type": "number"
    },
    "rewards_max_spread": {
      "type": "number"
    }
  }
}
    arguments 29 lines
  • pm_order_book_fill paid never probed

    Walks the order book level by level: VWAP, slippage in basis points against mid, what fills and what does not. Book arithmetic, not a fill-probability model.

    mcp-tool

    {
  "type": "object",
  "required": [
    "book",
    "shares"
  ],
  "properties": {
    "book": {
      "type": "object",
      "properties": {
        "asks": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "price",
              "size"
            ],
            "properties": {
              "size": {
                "type": "number"
              },
              "price": {
                "type": "number"
              }
            }
          }
        },
        "bids": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "price",
              "size"
            ],
            "properties": {
              "size": {
                "type": "number"
              },
              "price": {
                "type": "number"
              }
            }
          }
        }
      },
      "description": "Order book: bids and asks with price and size in shares"
    },
    "side": {
      "enum": [
        "buy",
        "sell"
      ],
      "type": "string"
    },
    "price": {
      "type": "number"
    },
    "shares": {
      "type": "number"
    },
    "queue_ahead": {
      "type": "number"
    }
  }
}
    arguments 67 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 e0bb37fa0c909d89.

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