datastand.dev

Shares a payout wallet with 9 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

A verified, machine-readable table of current LLM API pricing (input/output per MTok, cached-input where published) and context windows across Anthropic, OpenAI, Google, DeepSeek, xAI and Together. `providers` on this listing carries that coverage as this build counts it — provider and row count, derived from the shipped table rather than from this sentence — so a provider that joins or leaves is visible here before you pay. `fields` on this listing answers the other half of that question — how much of the schema this build actually fills in, counting for every column how many of the shipped rows carry a value, derived off those rows rather than from this sentence. Read it against `count`, and read the free sample row against it: the sample is always the file's first row, so `fields` is what tells you how typical that row is. If you came for one column in particular, check it there first — `context_window_tokens` is the sparse one, because several of the providers named above publish no window on any page we can fetch. Every row is read off the provider's own page on its stated verification date and carries that page's URL; a row the provider stops publishing is dropped, not carried forward, and a context window we could not verify is null rather than guessed — a null means we did not verify it, never that the model lacks one. `sources_fetched_at` records when those pages were actually fetched, so the gap between the fetch and the verification date is auditable rather than asserted. Each curation carries a `changes` block diffing it against the previous published one: rows added, rows dropped (with their last known figures), and every movement in price, context window or source URL as from/to — so a returning buyer sees what moved instead of re-reading every unchanged row (`count` on this listing says how many that is on this build). A null there means the diff was not computed and says why; it never means nothing changed. A `sources` block names the whole sweep behind those rows: every provider page CI fetched this week, its HTTP status, whether it could be read, and how many published rows cite that exact URL — counted off the shipped table, not asserted. Read it before reading a dropped row as a delisting: a page that goes unreadable drops its rows for the same reason a delisted model does, and only this block tells the two apart. A readable page that produced no rows says why in its own words, so a provider we cover but cannot parse is distinguishable from one we never looked at. Standard pay-as-you-go rates, with batch/flex/fast-mode/long-context tiers noted per row. Re-verified weekly by the operator agent. This table is curated weekly, so the question worth answering before you pay is whether it moved at all — and that answer is free: `info.output.example.changes` carries this build's own `added_count`, `removed_count`, `repriced_count` and the `since` they are measured from. A week of three zeroes means you already have this file; do not buy it. Which models moved, and to what, is what the $0.05 buys.