OpenRouter Models Scraper — AI Pricing & Specs | from $1.50/1K

Scrape OpenRouter's full AI model catalog — 300+ models with pricing, context lengths, modalities, provider info, and optional per-endpoint breakdown.

What you get

Field	Example
model_id	openai/gpt-4o
name	OpenAI: GPT-4o
provider	openai
context_length	128000
pricing_prompt_usd_per_token	0.0000025
pricing_completion_usd_per_token	0.00001
pricing_image_usd_per_token	(when applicable)
pricing_audio_usd_per_token	(when applicable)
pricing_web_search_usd	(per search call)
pricing_input_cache_read_usd_per_token	(cache pricing)
pricing_internal_reasoning_usd_per_token	(reasoning models)
modality	text+image->text
input_modalities	["text","image","file"]
tokenizer	GPT
is_free	false
pricing_tier	paid / free / variable
is_moderated	true
supported_parameters	full list
endpoints	per-provider breakdown (optional)
url	browsable model page link
created_at	ISO datetime
+ 16 more fields	see dataset schema

39 fields per model, pay per result.

Use cases

• LLM cost comparison: compare prompt/completion pricing across 57+ providers at once
• Model discovery: filter by modality, provider, context length, free vs. paid
• Pricing monitoring: track price changes over time (schedule the actor)
• AI product research: find which providers support which features (caching, reasoning, vision)
• Competitive intelligence: audit the LLM market automatically

Input

Parameter	Type	Description
filterText	string	Case-insensitive substring filter on model id/name/description
includeEndpoints	boolean	Fetch per-provider endpoint breakdown (one extra API call/model)
maxItems	integer	Max models to return; 0 = all (~300+)
proxyConfiguration	proxy	Optional Apify Residential proxy (not required for standard use)

Access method

Rung-1 (official public JSON API) — GET https://openrouter.ai/api/v1/models. No authentication, no access friction, no proxy required. Extremely reliable.

Pricing

Pay-per-result (PPE). Charged per model record pushed to the dataset.

Catalog size	Cost at $1.50/1K
Full catalog (~344 models)	~$0.52
Top 50 models	~$0.08
Single provider filter	pennies

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.