Where can I find o10’s text reference?
Start with /llms.txt for a content index. Selected pages also offer a Text version link; model records are available at /api/models.json.
o10 publishes plain-text versions of selected guides and a JSON model catalog. These formats make it easier to bring the relevant information into a research tool, application, or AI-assisted workflow.
Start with the core questions, then examine the examples and tradeoffs below.
Start with /llms.txt for a content index. Selected pages also offer a Text version link; model records are available at /api/models.json.
A text version is convenient for copying a focused explanation into another tool. Follow its source link to check the full context, including any limitations.
No. Check each record’s date and the current endpoint’s terms before using a price in a forecast or purchase decision.
Use the formatted page for reading, plain text for copying, and JSON for processing catalog records.
The llms.txt proposal describes a Markdown overview that points to relevant information. It is a guide to content, not a transcript of a model’s reasoning.
On o10, keep the source URL with any excerpt you reuse. A copied paragraph can lose qualifications elsewhere on the source page.
Sources: The llms.txt proposal
A convenient export does not establish that every fact is current or that an example applies to your workload.
Check model identifiers, dates, supported features, and the meaning of each price field. Calculate total task cost rather than multiplying one rate by an incomplete token count.
Google states that no special files or markup are required for its AI search features. Publishing a text index does not guarantee indexing, ranking, or citation.
Check source dates and endpoint terms before relying on a catalog price.
Paste a week of traffic. Get the number that books the audit.
See what you're overpaying →