How many AI models does Recursive serve?
1 tracked model as of 26 October 2026: 1 language model (1 with a public ModelCap Index position), across 1 live endpoint observed through OpenRouter.
Inference provider
Every tracked model Recursive serves through OpenRouter, with Recursive's own input and output price per 1M tokens, the context window it serves, disclosed quantization and measured endpoint uptime. Rows link to the model page, where every provider's deployment is listed side by side.
Snapshot as of 26 October 2026
Recursive serves 1 tracked model through 1 endpoint as of 26 October 2026; the highest-ranked is Flint (ModelCap Index #71); mean measured uptime is 100.0%.
Ranked models first, in ModelCap Index order. Prices are the lowest Recursive lists for the model; the endpoint count shows how many deployments carry it.
1 tracked model as of 26 October 2026: 1 language model (1 with a public ModelCap Index position), across 1 live endpoint observed through OpenRouter.
Flint from Recursive is the highest-ranked language model Recursive serves, at ModelCap Index position #71 and Free per 1M output tokens on Recursive. The table lists every model in Index order.
Recursive lists no positive language-token price in the current snapshot.
Flint, served with a 262K-token context window on Recursive. Providers sometimes serve less than the model's published maximum, so the figure here is the provider's own.
Mean measured uptime across Recursive endpoints is 100.0% over the last 30 minutes, as reported by OpenRouter at the time of the snapshot. Per-model uptime is in the table; it is a live operational signal, not a service-level guarantee.
From the OpenRouter catalogue entry for each Recursive endpoint, in USD per 1M tokens, re-observed on every ModelCap refresh. Where Recursive exposes several deployments of one model at different prices, the table shows the lowest and notes the count; the model page lists each deployment.
This page uses the published ModelCap snapshot dated 26 October 2026. Publication and page updates happen separately. Offers retained from a failed refresh are marked stale in the data and are not counted here.