llms.txt Intelligence API
Check caller-supplied llms.txt text for structure, link wording, size, page coverage, navigation, contradictions, instruction-override phrases, and version mismatches. All checks run locally on the request.
Check caller-supplied llms.txt text or structured JSON for one H1, a summary blockquote, H2 sections, and well-formed list links. URLs are not fetched.
Review link titles and descriptions in caller-supplied llms.txt content for generic labels and missing descriptions. Links are not opened.
Measure caller-supplied llms.txt size, repeated lines, and repeated link paths. The token figure is characters divided by four, not a model tokenizer.
Compare llms.txt link paths with a caller-supplied page list and report pages that have no matching link. Pages are not fetched, and an unmatched link is not treated as a missing site page.
Find repeated link titles that point at different paths and generic section names in caller-supplied llms.txt content. No page is fetched.
Compare caller-supplied llms.txt text with caller-supplied documents for conflicting account, API key, price, and HTTP method statements. This is a phrase match, not a reading of intent.
Look in caller-supplied llms.txt text for a fixed set of instruction-override phrases, script tags, hidden characters, and javascript links. Ordinary how-to steps are not flagged, and nothing is executed.
Compare caller-supplied llms.txt versions for /api/vN/ majors, summary semantic versions, updated dates, and link titles whose paths differ. Neither version is fetched.