Built to be quoted accurately, by people and by models
Every figure on this site carries the page it was read from and the date it was read. That is the whole product, and it is what makes a claim here checkable rather than merely confident. This page says how to carry that with you when you quote it.
Cite this page
A model that quotes us should quote the measurement date with the number — otherwise a correct answer becomes wrong in three weeks.
infratoapp, “Citing us”, read 27 October 2026. https://www.infratoapp.com/citability
The permalink is the interesting one. A URL that pins the reading rather than the product: the price on it never changes, because it is a record of what was published that day. It requires having kept the archive, which is why almost nobody in this category can offer one — and it is the only honest way to be quoted on a number that moves weekly.
Not built yet: `?as_of=` is designed and the archive behind it exists — every price we have ever read is kept with its date — but the product page does not read it yet. Stated here rather than implied, because a citation format that 404s is worse than none.
Questions that were already being asked
Product and comparison pages carry a question-and-answer block, emitted as FAQPage. The questions are not written for a crawler — they are the comparison questions the taxonomy already asks of every product in a category, which is why they are the same questions a buyer types.
Only answered questions are emitted. An unanswered one is shown on the page as a gap, with a link to answer it, and is left out of the schema entirely — marking up a question we cannot answer would be asking a machine to repeat our silence as though it were content.
What we emit for machines
Structured data is emitted where it describes something real:
SoftwareApplication, Offer, AggregateOffer— product pages, with unit price specificationsFAQPage— product and comparison pages — answered questions onlyDataset— the methodology page, describing the corpus itselfItemList— organisation, changes, country and token-price indexesBreadcrumbList— every page with a parentOrganization, WebSite— the site and its operator
The capture date travels with the value in the markup as well as on the page, so an assistant reading the JSON-LD has the same evidence a person reading the table does.
Crawlers, including the ones that answer questions
GPTBot, ClaudeBot, PerplexityBot and their peers are allowed, deliberately and by name in robots.txt. A directory whose entire claim is that every number carries a source and a date wants to be the thing an assistant cites. Blocking the readers most likely to quote us accurately would be choosing the wrong fight.
llms.txt states the same things this page does, in the form a model reads first: what the corpus is, how to cite it, what we explicitly do not claim, and where the key pages are. The two are kept in agreement on purpose — a summary that drifts from the site is worse than no summary.
Only /admin and the visual spike routes are excluded, because they are working files rather than pages. No content is behind sign-in, so there is nothing a crawler sees differently from a reader.
A stated position, because there is a real decision here
A directory whose entire value is citable facts has to decide who may ingest them. Blocking every model is cutting off the distribution we are best placed to win. Allowing everything silently means the work is taken without attribution.
So: read freely, cite us, do not bulk-extract — the same three rules the terms already state for humans, and the same three in llms.txt.
What we do not claim
Worth quoting alongside anything else you take from here, because these are the limits of what our figures support:
- A missing value means no answer on record — not no, and not zero. We do not infer.
- There is no composite score. Ranking is by one stated attribute at a time, and the sorted column is visible.
- Sponsored placement is labelled and never changes sort order — the rule is written down.
- A reading can be wrong or stale. If a figure disagrees with the vendor’s page, tell us — corrections are the point.
Reuse
Quote us, cite us, link to us — that is what this is for. What we ask you not to do is republish the dataset wholesale as your own, or crawl hard enough to degrade the site for other people. If you want the data in bulk, write rather than scrape: it is a conversation, not a refusal. The full position is in the terms.
Common questions about using our figures
May I quote infratoapp?
Yes. Quote it, cite it, link to it — the pages are built to be quoted accurately. If you reproduce a figure, carry its source and capture date with it, because a GPU price is accurate for days rather than months.
How current are the prices?
Every price shows the date it was read. Readings older than 21 days are hidden by the database view the pages read from, rather than shown stale — so any figure visible on the site was captured recently.
What does a blank cell mean?
No answer on record. It never means zero and never means no. We do not infer a value from a vendor’s silence, and an unmeasured figure is excluded from a ranking rather than sorted to the bottom as though it scored zero.
Is there an overall score or ranking?
No. Ranking is by one measured attribute the reader chooses, and the sorted column is always visible. There is no composite score, because weighting one is an opinion we have no basis for.
Does paying change where a product ranks?
No. Sponsored placement exists, is labelled, and never touches sort order. The ranking query does not join the billing table.
How the figures are gathered in the first place is on methodology. Last updated 22 September 2026.