SLXD AI API Pricing

app.slxd/aiapipricing · v1.0.0 · search-and-web

SLXD AI API Pricing is healthy: it completed an MCP handshake in 1367 ms and exposes 10 tools.

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

Endpoint: https://aiapipricing.slxd.app/mcp/aiapipricing (streamable-http)

No repository listed · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count10
Latency1367 ms
Last checked (UTC)2026-10-18T21:40:33.207Z

Health history

Checked (UTC)StatusLatencyError
2026-10-18T21:40:33.207ZHealthy1367

Tools (10)

search_modelsSearches the catalogue of AI models and returns their current prices, with a confidence level and the sources backing each price.
get_model_priceReturns 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_modelsReturns 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_historyReturns 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_changesLists recent price increases, decreases, additions and removals across the catalogue, newest first.
list_providersLists 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_sourcesExplains 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_toolsSearches 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_schemaReturns the full input schema of a single tool, including which arguments are required. Call it after find_tools and before run_tool.
run_toolExecutes 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.