1 · Discover
Find exact offerings
search_components({
entity: "offering",
family: "model",
query: "MiniMax M3"
})Returns Ollama and OpenRouter as separate choices. Use next_offset when total_count exceeds the current page.
For agents
AIStackPicker exposes the same exact parts and offers as the human Catalog through read-only MCP and REST surfaces. Agents can distinguish a model from the provider route or artifact that supplies it, then carry that exact identity into estimates and compatibility checks. Every response carries clean citation links and dates, and never includes affiliate URLs.
Endpoint
POST /api/mcp
Streamable HTTP transport. Read-only in v1. A plain-text summary for crawlers and agents lives at /llms.txt.
Exact part workflow
Use a component when the general part is enough. Use an exact Offering when provider, artifact, plan, billing path, price, or availability matters. These three calls preserve that boundary end to end.
1 · Discover
search_components({
entity: "offering",
family: "model",
query: "MiniMax M3"
})Returns Ollama and OpenRouter as separate choices. Use next_offset when total_count exceeds the current page.
2 · Inspect
get_component({
entity: "offering",
slug: "openrouter-minimax-m3"
})Returns the exact provider route, Variant specifications, price observations, latest availability, sources, dates, and clean citation URL.
3 · Use
estimate_build({ config: {
variant: "cloud-llm-api",
path: "api",
model: "model_minimax_m3",
model_offering:
"offering_openrouter_minimax_m3",
usage: "prof_moderate"
} })The component identifies the model; the Offering identifies the provider route. The estimator never borrows another route's price or availability.
REST equivalents
The same Core payload backs REST and MCP. Responses are capped at 20 rows and return a stateless next offset.
Tools
search_components
Search legacy component families or exact Catalog offerings. Exact results keep provider, product, variant, delivery, billing, price, availability, and citation identity separate.
get_component
Retrieve one component or exact offering. Offering records include full specifications, per-field sources, and exact price and availability observations.
estimate_build
Price a complete or partial stack using selected component and exact offering IDs. Returns line items, monthly and one-time totals, price completeness, and warnings.
check_compatibility
Check the same configuration against reviewed compatibility rules. Completeness, compatibility, and unknown fit remain separate results.
get_build
Retrieve a saved build by its share id, including its frozen per-part estimate snapshot, current estimate, per-Offering identity/price/availability/specification receipts, and the reason each field was chosen.
The same data humans see
The tools read the exact records behind the human Catalog and Builder, so an agent's estimate matches the one on the site: same prices, same compatibility rules, same verification dates. Missing price or availability stays unknown. Historical legacy_only Offerings can be retrieved for old saves but never appear as new choices.