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

AI API Pricing

https://aiapipricing.slxd.app

Registry code: 8ae773ac1909d997

api record

Look up, compare and track AI model API prices from an AI assistant. No sign-in needed.

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

endpoint
https://aiapipricing.slxd.app/mcp/aiapipricing
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 AI API Pricing live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is AI API Pricing free to use?
Yes — the hub reached it with no key and no payment.
What tools does AI API Pricing have?
10 tools: tool_schema, search_models, get_model_price, compare_models, price_history, find_tools, run_tool, recent_changes, ….
Is AI API Pricing 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
127ms

last good check

priced tools
0

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

  • recent_changes open 1h ago

    Lists recent price increases, decreases, additions and removals across the catalogue, newest first.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "days": {
          "type": "integer",
          "default": 30,
          "maximum": 365,
          "minimum": 1
        },
        "limit": {
          "type": "integer",
          "default": 50,
          "maximum": 200,
          "minimum": 1
        }
      }
    }
    arguments 17 lines
  • data_sources open 1h ago

    Explains where the prices come from: which sources are consulted, their weight and licence, when each last succeeded, and whether any is currently failing. Use this to judge how much to trust a price.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • list_providers open 1h ago

    Lists every provider in the catalogue and how many models each has. These are the houses that MAKE the models: a reseller (Vertex, Bedrock, Azure, OpenRouter, a subscription plan) is a sales channel, not a provider — ask `get_model_price` with a `channel` for what one of those charges.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • tool_schema unknown never probed

    Returns the full input schema of a single tool, including which arguments are required. Call it after find_tools and before run_tool.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "minLength": 1,
          "description": "Exact tool name, as returned by find_tools."
        }
      }
    }
    arguments 13 lines
  • search_models unknown never probed

    Searches the catalogue of AI models and returns their current prices, with a confidence level and the sources backing each price.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 100,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Free text matched against name and id."
        },
        "provider": {
          "type": "string",
          "description": "Restrict to one provider slug, e.g. `openai`."
        }
      }
    }
    arguments 19 lines
  • get_model_price unknown never probed

    Returns every current price for one model — input, output, cached reads, batch and priority tiers, context brackets — with the confidence level and which sources agree. By default these are the maker's own prices; pass `channel` to get what a reseller charges for the same model instead. Two dimensions can share a label, so the ones that would collide carry their qualifiers, e.g. 'Web search (context size: high)'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "model"
      ],
      "properties": {
        "model": {
          "type": "string",
          "description": "Model id as `provider/slug`, e.g. `anthropic/claude-sonnet-4-5`."
        },
        "channel": {
          "enum": [
            "direct",
            "vertex",
            "bedrock",
            "azure",
            "sagemaker",
            "databricks",
            "snowflake",
            "watsonx",
            "cloudflare",
            "fireworks",
            "alibaba",
            "openrouter",
            "github_copilot",
            "coding_plan",
            "token_plan",
            "other"
          ],
          "type": "string",
          "description": "Sales channel to price. Omit for the maker's own price. `direct` is the maker, the rest resell the same model at their own rate; a channel that does not sell this model returns the model with no prices."
        }
      }
    }
    arguments 34 lines
  • compare_models unknown never probed

    Returns the current prices of several models side by side. Amounts in credits are never converted to money, so a credit-billed model is not comparable to a token-billed one. Two dimensions can share a label, so the ones that would collide carry their qualifiers, e.g. 'Web search (context size: high)'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "models"
      ],
      "properties": {
        "models": {
          "type": "array",
          "items": {
            "type": "string",
            "description": "Model id as `provider/slug`, e.g. `anthropic/claude-sonnet-4-5`."
          },
          "maxItems": 8,
          "minItems": 2
        }
      }
    }
    arguments 17 lines
  • price_history unknown never probed

    Returns a model's price over time. Each point is [date, amount] with the date as YYYY-MM-DD. The series holds only the points where the price CHANGED — prices are step functions, so a stable model is one point, not one per day; when a price changed twice on one day, both points are returned with the same date, in order. One series per price dimension: two dimensions can share a label, so the ones that would collide carry their qualifiers, e.g. 'Web search (context size: high)'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "model"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "ISO date, inclusive."
        },
        "from": {
          "type": "string",
          "description": "ISO date, inclusive."
        },
        "model": {
          "type": "string",
          "description": "Model id as `provider/slug`, e.g. `anthropic/claude-sonnet-4-5`."
        }
      }
    }
    arguments 20 lines
  • find_tools unknown never probed

    Searches the full catalogue of available tools by keyword and returns the matching tool names with a short description. Use it when no directly-listed tool fits the task — many tools are available but not listed. Then call tool_schema for the one you picked, and run_tool to execute it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Space-separated keywords, e.g. 'invoice pdf export'. Matched against tool names and descriptions; any term may match."
        }
      }
    }
    arguments 13 lines
  • run_tool unknown never probed

    Executes a tool by name with the given arguments. Use it for tools that are not directly listed — look them up with find_tools and check their arguments with tool_schema first. Prefer a directly-listed tool whenever one fits. If the action is destructive, ask the user to confirm before calling it.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "minLength": 1,
          "description": "Exact tool name, as returned by find_tools."
        },
        "arguments": {
          "type": "object",
          "description": "Arguments object matching the tool's schema.",
          "propertyNames": {
            "type": "string"
          },
          "additionalProperties": {}
        }
      }
    }
    arguments 21 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 8ae773ac1909d997.

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

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.