Recipes API
JSON and Markdown for scripts and AI agents.
Every recipe on this site is also available to scripts and AI agents — no key, the same data the pages render.
Any page, as Markdown or JSON
Take a recipe page URL, configured in the builder however you like, and add .md or .json. The query string carries the configuration, so the response is the command for exactly what the page shows:
https://vllm-recipes-hm812xejs-inferact-inc.vercel.app/deepseek-ai/DeepSeek-R1?hardware=b200&strategy=single_node_dep ← the page
https://vllm-recipes-hm812xejs-inferact-inc.vercel.app/deepseek-ai/DeepSeek-R1.md?hardware=b200&strategy=single_node_dep ← that configuration as Markdown
https://vllm-recipes-hm812xejs-inferact-inc.vercel.app/deepseek-ai/DeepSeek-R1.json?hardware=b200&strategy=single_node_dep ← that configuration as JSON
Adding the extension to the end of the whole URL (…&strategy=single_node_dep.md) works too. The Copy page menu on every recipe page links both forms for the current selection. An assistant fetching a recipe page URL for its user (ChatGPT-User, Claude-User, Perplexity-User, MistralAI-User), or any request sending Accept: text/markdown, gets the Markdown form for that URL's query directly.
- Markdown leads with the rendered command (marked authoritative), then the notes and known issues that apply to this configuration, the tuned preset in effect, and the guide as background — the form to hand to an AI assistant.
- JSON has the same shape as the static per-hardware renderings below, plus
selection(what was rendered),page_urlandmarkdown_url.
# The serve command for DeepSeek-R1 on 8× B200, data + expert parallel
curl -s "https://vllm-recipes-hm812xejs-inferact-inc.vercel.app/deepseek-ai/DeepSeek-R1.json?hardware=b200&strategy=single_node_dep" | jq -r .command
# Multi-node: one command per node — never replay one on every node
curl -s "https://vllm-recipes-hm812xejs-inferact-inc.vercel.app/deepseek-ai/DeepSeek-R1.json?hardware=h100&strategy=multi_node_tp&nodes=2" | jq -r '.head_command, .worker_commands[]'
Query parameters
The same ones the page URL uses. Values the recipe can't run fall back to its defaults, and selection.adjusted (JSON) or a note under the Configuration line (Markdown) says what changed and why.
| Parameter | Value |
|---|---|
hardware | A hardware profile id, e.g. h200, b200, gb300, mi355x (taxonomy) |
variant | A variant key of the recipe (default, nvfp4, …) |
strategy | A serving strategy id (strategies); multi-node ones also need nodes |
nodes | Node count for a multi-node strategy (nodes per instance under Mooncake) |
features | Comma-separated feature keys to turn on (tool_calling,reasoning, …). Use features=none to turn them all off. Omit it to use the recipe defaults. |
preset, point | A tuned preset and its operating point; preset=baseline drops a default preset |
kv_offload | A KV offload option (simple, lmcache, … — kv_offload in the taxonomy) or a Mooncake topology (kv_store_distributed_mooncake, kv_store_centralized_mooncake) |
prefill_nodes, decode_nodes, prefill_mode, decode_mode, pd_router, pd_connector | Prefill/decode disaggregation (strategy=pd_cluster) |
prefill_rank, decode_rank | Zero-based node index within the corresponding PD pool; selects the singular role command |
Each recipe's Markdown lists the values it accepts under Other configurations.
Select the PD router and KV connector independently, subject to catalog compatibility.
For Ascend, pd_router=ascend selects Ascend Router; pd_connector=mooncake_ascend
selects Mooncake (Ascend). Each choice requires Ascend hardware, PD disaggregation
and an active model preset that explicitly declares it in select.
The catalog defaults to MooncakeConnectorV2 with pool-size placeholders.
Recipes can override the implementation and settings through existing named preset
json_args edits, including when KV offload is composed; there is no name allowlist.
PD renderings include prefill.node_commands[] and decode.node_commands[], with every node's
node_rank, command, argv, env, and Docker equivalents. Run each on its named node;
the singular role command remains the node selected by prefill_rank / decode_rank.
Static files
Built with the site; cheap to fetch in bulk.
| Path | Contents |
|---|---|
/models.json | Every recipe: id, title, provider, page and JSON links |
/<hf_id>.json | One recipe: metadata, variants, features, guide, and recommended_command with a by_hardware index |
/<hf_id>/hw/<hardware>.json | The recommended rendering on one hardware profile, with alternatives per strategy |
/<hf_id>/hw/<hardware>/strategies/<strategy>.json | One hardware × strategy rendering |
/<hf_id>/presets/<preset>.json | A tuned preset, rendered at each of its points |
/strategies.json, /taxonomy.json | Serving strategies; hardware profiles and the rest of the vocabulary |
/recipe.schema.json | JSON Schema of a recipe YAML |
For AI assistants
/llms.txt— an index of every recipe, linking its Markdown form./llms-full.txt— the full text of every recipe in one file.