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

ai-pricing-hub

https://ai-pricing-hub-mcp.fly.dev

Registry code: 5c199f9c43dbb69d

api record

Compare LLM API and cloud compute pricing, estimate workload costs, pick a model within budget.

from a public catalogue that lists it, not from the operator

endpoint
https://ai-pricing-hub-mcp.fly.dev/mcp
protocol
http-sse ·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 ai-pricing-hub live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ai-pricing-hub free to use?
Yes — the hub reached it with no key and no payment.
What tools does ai-pricing-hub have?
5 tools: recommend-llm-model, compare-compute-pricing, compare-models-side-by-side, compare-llm-models, estimate-llm-cost.
Is ai-pricing-hub 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
135ms

last good check

priced tools
0

of 5 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 5 tools
2 open 3 never probed 2 of 5 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.

  • compare-llm-models open 1h ago

    Browse and filter the whole LLM catalogue and get back a ranked table: price, quality (ELO), efficiency and capabilities. Use this when the user wants to SEE THE FIELD — 'show me models under $1/1M', 'which providers have vision models', 'list open-weight models above ELO 1300'. For a single PICK under a budget use recommend-llm-model; to weigh 2-4 NAMED models against each other use compare-models-side-by-side. Prices come from optimtoken.optimnow.io where reachable; the response's `provenance` says which tier served them and whether they are vendor-verified. Filter by provider, price tier (category), openness, capability, price range, or minimum ELO score. Optionally enrich with business metrics for a use case. Price tier and openness are independent: a model can be Frontier-priced and open-weight at once. Reports both list-price cost and the optimized cost achievable with prompt caching and the batch API. IMPORTANT: Report all prices, costs, and scores EXACTLY as returned. Do NOT add commentary, opinions, or recommendations beyond what the data shows. Present the results as a table and let the user draw conclusions.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "number",
      "maximum": 50,
      "minimum": 1,
      "description": "Max models to return (default: 15)"
    },
    "minElo": {
      "type": "number",
      "description": "Minimum Chatbot Arena ELO score. Typical range 1000-1500; ~1400 is roughly frontier-class. Models with no ELO score never satisfy this.",
      "exclusiveMinimum": 0
    },
    "category": {
      "type": "string",
      "description": "Price tier, matched by exact equality (case-insensitive): Frontier, Mid-tier, Budget, Image. This is cost only — self-hostability is the separate `openness` axis."
    },
    "openness": {
      "enum": [
        "Open source",
        "Open weights",
        "Proprietary",
        "Unknown"
      ],
      "type": "string",
      "description": "Filter by self-hostability, derived from the licence: Open source, Open weights, Proprietary, Unknown"
    },
    "provider": {
      "type": "string",
      "description": "Filter by provider name (e.g. 'OpenAI', 'Anthropic', 'Google')"
    },
    "capability": {
      "type": "string",
      "description": "Capability, matched by exact equality (case-insensitive): Text, Vision, Reasoning, Agents, Image Gen, Audio. Any other string returns zero matches. There is no Code capability: for what coding costs, use useCasePreset codingTask."
    },
    "volumePreset": {
      "enum": [
        "10k",
        "100k",
        "1m"
      ],
      "type": "string",
      "description": "Monthly request volume: 10k, 100k, or 1m. Default: 100k"
    },
    "maxInputPrice": {
      "type": "number",
      "description": "Max input price per 1M tokens in USD"
    },
    "useCasePreset": {
      "enum": [
        "supportTicket",
        "knowledgeQA",
        "meetingSummary",
        "marketingContent",
        "codingTask",
        "invoiceProcessing",
        "callSummary",
        "agentWorkflow"
      ],
      "type": "string",
      "description": "Workload shape, which sets tokens per request: supportTicket (1.5k in / 500 out), knowledgeQA (2k / 800), meetingSummary (10k / 1.2k, batch-eligible), marketingContent (2.5k / 1.8k), codingTask (3k / 2k), invoiceProcessing (1.5k / 600, batch-eligible), callSummary (2k / 700, batch-eligible), agentWorkflow (6k / 3k). Default: supportTicket"
    },
    "maxOutputPrice": {
      "type": "number",
      "description": "Max output price per 1M tokens in USD"
    }
  }
}
    arguments 70 lines
  • estimate-llm-cost open 1h ago

    Cost a workload with EXACT numbers the caller supplies: arbitrary token counts per request and any monthly volume, not just the 10k/100k/1m presets the other cost tools use. Use this for 'about 800 in and 200 out, 4 million calls a month', or to price one named model across every use-case profile. To compare 2-4 named models like for like at a preset volume, use compare-models-side-by-side instead. Provide a model name to get detailed cost breakdowns, or compare costs across all use case presets. Each figure comes twice: list price, and the optimized price achievable with prompt caching and the batch API. IMPORTANT: Report all cost figures EXACTLY as returned. Do NOT add commentary or recommendations beyond the data.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "modelName": {
      "type": "string",
      "description": "Model name, e.g. 'GPT-4o'. A partial name matches up to 5 models and ALL of them are costed. If omitted, the first 8 catalogue entries are used — that is catalogue order, not a quality ranking."
    },
    "monthlyVolume": {
      "type": "integer",
      "maximum": 1000000000,
      "minimum": 1,
      "description": "Exact monthly request count, any integer (default 100,000). This tool does not take the 10k/100k/1m presets the other cost tools use."
    },
    "useCasePreset": {
      "enum": [
        "supportTicket",
        "knowledgeQA",
        "meetingSummary",
        "marketingContent",
        "codingTask",
        "invoiceProcessing",
        "callSummary",
        "agentWorkflow"
      ],
      "type": "string",
      "description": "Workload shape, which sets tokens per request: supportTicket (1.5k in / 500 out), knowledgeQA (2k / 800), meetingSummary (10k / 1.2k, batch-eligible), marketingContent (2.5k / 1.8k), codingTask (3k / 2k), invoiceProcessing (1.5k / 600, batch-eligible), callSummary (2k / 700, batch-eligible), agentWorkflow (6k / 3k). Default: every preset."
    },
    "customInputTokens": {
      "type": "integer",
      "maximum": 10000000,
      "minimum": 1,
      "description": "Custom input tokens per request. Must be supplied TOGETHER with customOutputTokens — either alone is ignored and the preset is used. A custom shape assumes no cacheable prefix and no batch eligibility, so its optimized cost equals its list cost."
    },
    "customOutputTokens": {
      "type": "integer",
      "maximum": 10000000,
      "minimum": 1,
      "description": "Custom output tokens per request. Must be supplied TOGETHER with customInputTokens — either alone is ignored and the preset is used."
    }
  }
}
    arguments 42 lines
  • recommend-llm-model unknown never probed

    Pick a model. Returns a ranked top 3 for one workload under optional constraints, each with a per-constraint satisfied/violated breakdown as the evidence. Use this when the user wants an ANSWER rather than a table — 'what should I use for support tickets under $500 a month'. To browse or filter the whole catalogue instead, use compare-llm-models. Constraints: (monthly budget, minimum ELO, required capability, self-hostability). Returns a top 3 as structured facts — efficiency rank, ELO, list and optimized cost, FinOps flag, volatility, and a per-constraint satisfied/violated breakdown. When nothing satisfies every constraint the query is reported as over-constrained and the nearest misses are returned instead, each carrying the constraint it failed. IMPORTANT: Report the returned facts EXACTLY. The ranking is already computed — do not re-rank, and do not present a near miss as if it satisfied the constraints.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "useCasePreset"
  ],
  "properties": {
    "minElo": {
      "type": "number",
      "description": "Minimum Chatbot Arena ELO score. Typical range 1000-1500; ~1400 is roughly frontier-class. Models with no ELO score never satisfy this.",
      "exclusiveMinimum": 0
    },
    "openness": {
      "enum": [
        "Open source",
        "Open weights",
        "Proprietary",
        "Unknown"
      ],
      "type": "string",
      "description": "Require a self-hostability bucket, derived from the licence: Open source, Open weights, Proprietary, Unknown"
    },
    "volumePreset": {
      "enum": [
        "10k",
        "100k",
        "1m"
      ],
      "type": "string",
      "description": "Monthly request volume: 10k, 100k, or 1m. Default: 100k"
    },
    "useCasePreset": {
      "enum": [
        "supportTicket",
        "knowledgeQA",
        "meetingSummary",
        "marketingContent",
        "codingTask",
        "invoiceProcessing",
        "callSummary",
        "agentWorkflow"
      ],
      "type": "string",
      "description": "Workload shape, which sets tokens per request: supportTicket (1.5k in / 500 out), knowledgeQA (2k / 800), meetingSummary (10k / 1.2k, batch-eligible), marketingContent (2.5k / 1.8k), codingTask (3k / 2k), invoiceProcessing (1.5k / 600, batch-eligible), callSummary (2k / 700, batch-eligible), agentWorkflow (6k / 3k)."
    },
    "maxMonthlyBudget": {
      "type": "number",
      "description": "Maximum monthly budget in USD at the given volume. Tested against the LIST-price monthly cost, not the caching/batch-optimized cost.",
      "exclusiveMinimum": 0
    },
    "requiredCapability": {
      "type": "string",
      "description": "Capability the model must have: Text, Vision, Reasoning, Agents, Image Gen, Audio. There is no Code capability: for coding, pass useCasePreset codingTask."
    }
  }
}
    arguments 56 lines
  • compare-compute-pricing unknown never probed

    Compare cloud compute instance pricing across AWS, Azure, GCP, DigitalOcean, OCI, OVH, and Alibaba. Filter by region, provider, vCPUs, memory, category, processor, or use case. All prices are Linux on-demand list prices in USD. Not every price column is live: `provenance.priceTypes` says which of each provider's price columns come from a live API, which are static constants, and which are unavailable, and `provenance.staticPriceColumns` lists the non-live ones outright. When you report a savings plan or reserved rate that appears there, say that it is a static estimate. IMPORTANT: Report all prices EXACTLY as returned. Do NOT add commentary or recommendations beyond the data.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "number",
      "maximum": 50,
      "minimum": 1,
      "description": "Max instances to return (default: 20)"
    },
    "region": {
      "enum": [
        "us-east",
        "us-west",
        "europe",
        "asia-pacific"
      ],
      "type": "string",
      "description": "Pricing region: us-east, us-west, europe, asia-pacific. Default: us-east"
    },
    "sortBy": {
      "enum": [
        "price",
        "vcpus",
        "memory",
        "pricePerVCPU"
      ],
      "type": "string",
      "description": "Sort by: price, vcpus, memory, pricePerVCPU. Default: price"
    },
    "useCase": {
      "type": "string",
      "description": "Use case. Must be one of these exactly (case-insensitive): Web App, Database, HPC, ML & AI, Dev/Test, Big Data. Any other string returns zero matches rather than an error."
    },
    "category": {
      "type": "string",
      "description": "Instance category. Must be one of these exactly (case-insensitive): General Purpose, Compute Optimized, Memory Optimized, Storage Optimized, GPU / Accelerated, Burstable. Any other string returns zero matches rather than an error."
    },
    "maxVCPUs": {
      "type": "number",
      "description": "Maximum number of vCPUs"
    },
    "minVCPUs": {
      "type": "number",
      "description": "Minimum number of vCPUs"
    },
    "provider": {
      "type": "string",
      "description": "Cloud provider. Must be one of these exactly (case-insensitive): AWS, Azure, GCP, DigitalOcean, OCI, OVH, Alibaba. Any other string returns zero matches rather than an error."
    },
    "maxMemory": {
      "type": "number",
      "description": "Maximum memory in GiB"
    },
    "minMemory": {
      "type": "number",
      "description": "Minimum memory in GiB"
    },
    "processor": {
      "type": "string",
      "description": "Processor. Matched by exact equality (case-insensitive), so a partial value like 'H100' returns nothing. Known values: Intel, AMD, Graviton, Ampere, NVIDIA A100, NVIDIA H100, NVIDIA L4, NVIDIA T4, NVIDIA V100, NVIDIA Other."
    }
  }
}
    arguments 64 lines
  • compare-models-side-by-side unknown 1h ago

    Compare 2-4 named LLM models against all 8 use-case profiles at a chosen monthly volume, showing list and optimized cost for each. Use when the user names specific models to weigh against each other, rather than filtering the whole catalogue. If they also supply their own token counts, or a volume outside 10k/100k/1m, use estimate-llm-cost instead. Every name is resolved against the catalogue and the result is reported: a name that matched nothing, matched several models, or duplicated an earlier pick is stated explicitly. IMPORTANT: Report all prices and costs EXACTLY as returned, and repeat any name-resolution warning to the user — a missing column is not the same as a model that costs nothing.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "models"
  ],
  "properties": {
    "models": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 4,
      "minItems": 2,
      "description": "2-4 model names to compare, e.g. ['GPT-4o', 'Claude Opus 5', 'Gemini 3.1 Pro']"
    },
    "volumePreset": {
      "enum": [
        "10k",
        "100k",
        "1m"
      ],
      "type": "string",
      "description": "Monthly request volume: 10k, 100k, or 1m. Default: 100k"
    }
  }
}
    arguments 27 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 5c199f9c43dbb69d.

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

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.