# SLXD AI API Pricing

- Registry name: `app.slxd/aiapipricing` · version 1.0.0
- Categories (automatic, keyword rules): Cloud & networking, Infrastructure & security
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=app.slxd%2Faiapipricing
- Server page: https://mcpstation.net/s/app.slxd--aiapipricing.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://aiapipricing.slxd.app/mcp/aiapipricing`

## Tools (as reported by the server, not verified)

- `search\_models`: Searches the catalogue of AI models and returns their current prices, with a confidence level and the sources backing each price.
- `get\_model\_price`: 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 dimensio
- `compare\_models`: 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\)
- `price\_history`: 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
- `recent\_changes`: Lists recent price increases, decreases, additions and removals across the catalogue, newest first.
- `list\_providers`: 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.
- `data\_sources`: 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.
- `find\_tools`: 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.
- `tool\_schema`: Returns the full input schema of a single tool, including which arguments are required. Call it after find\_tools and before run\_tool.
- `run\_tool`: 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.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html