Check llms.txt version consistency API
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.
The Check llms.txt version consistency operation is part of the llms.txt Intelligence API on BRAINIAC.software. 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. It is exposed as POST /api/v1/llms-txt/version-consistency and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied llms.txt text, structured documents, and optional documentation pages processed locally Limitations: No URL is fetched, so a link is not treated as working or as proof a page exists. Scores subtract documented weights from 100. They are not a model grade. Contradiction and instruction checks match listed phrases only. Ordinary how-to text is not treated as an attack. Structured JSON is rendered to llms.txt lines before the same checks run. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Validate llms.txt structure, Check llms.txt link quality, Analyze llms.txt context budget, Analyze llms.txt page coverage. Open the group documentation for the full request schema, field notes, and response examples before integrating.
/api/v1/llms-txt/version-consistencyExample request
curl -i -X POST "https://www.brainiac.software/api/v1/llms-txt/version-consistency" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"versions": [
{
"id": "march",
"text": "# Agent docs\n\n> API 1.2.0. Updated: 2026-03-01\n\n## Calls\n- [Create](https://example.com/api/v1/widgets): Create a widget.\n"
},
{
"id": "april",
"text": "# Agent docs\n\n> API 1.3.0. Updated: 2026-04-01\n\n## Calls\n- [Create](https://example.com/api/v2/widgets): Create a widget.\n"
}
]
}
JSONAn unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.
FAQ
- Do I need an API key? No. Pay the listed USDC amount with x402.
- What network? Base (eip155:8453), USDC.
- Is this an official determination? No. Results are for human review against the cited sources.
Related operations
- Validate llms.txt structure — $0.03 USDC
- Check llms.txt link quality — $0.03 USDC
- Analyze llms.txt context budget — $0.03 USDC
- Analyze llms.txt page coverage — $0.04 USDC