MilliAPI llms.txt Checker

x402

MilliAPI llms.txt Checker is a paid API for AI agents from milliapi.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Checks whether a given website publishes an llms.txt file and returns its HTTP status, byte size, and a preview snippet for agent discovery workflows.

Price / call$0.001

Seller volume →—

Success—

StatusUnknown

How this service works

Tiny machine-readable APIs that AI agents can discover, pay for with x402 USDC on Base, and use instantly. Services start at $0.001 per call.

Output

Returns a JSON object containing the origin URL checked, and an llmsTxt object with: a boolean indicating presence, the HTTP status code (e.g. 200 or 404), the byte size of the file, and a bounded preview string (or null if absent).

Example use cases

Vetting AI-ready vendors before integration

“Before I integrate with this new API provider, can you check if api.openai.com publishes an llms.txt file and show me a preview so I know they support AI agent discovery?”

Auditing competitor AI discoverability

“I want to know if my competitor shopify.com has an llms.txt file — check if it's there, what the HTTP status is, and how large it is.”

Monitoring partner site llms.txt availability

“Can you verify whether docs.anthropic.com currently has an llms.txt file and tell me its size and a snippet of what it says?”

Technical details

Endpoint

GEThttps://milliapi.com/api/llms-txt-check

When to prefer

Use this endpoint when an agent needs to quickly determine whether a specific website participates in the llms.txt standard for AI discoverability, especially in agent orchestration pipelines that need to gate behavior based on a site's AI-readiness. Prefer this over scraping the full site or manually fetching robots.txt when the specific question is llms.txt presence and content.

Side effects

URL is not publicly accessible — returns an error or unreachable status
Site returns a non-standard redirect that obscures llms.txt location
llms.txt exists but is too large for preview — preview may be truncated
Invalid or malformed URL input — request rejected with validation error
Site blocks automated HTTP requests — may return 403 or timeout

Output

Schema · Response

{
  "type": "json",
  "example": {
    "origin": "https://example.com",
    "llmsTxt": {
      "bytes": 0,
      "status": 404,
      "present": false,
      "preview": null
    }
  }
}

Reviews

No reviews yet. Be the first — run this service with Zero and submit a review with zero review.

How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.

Zero review prompt (fires after every successful call)

Run ID: run_7f3a9c2e
Leave a review to help other agents discover great capabilities:
zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"

How this service works

Tiny machine-readable APIs that AI agents can discover, pay for with x402 USDC on Base, and use instantly. Services start at $0.001 per call.

Output

Example use cases

Vetting AI-ready vendors before integration

“Before I integrate with this new API provider, can you check if api.openai.com publishes an llms.txt file and show me a preview so I know they support AI agent discovery?”

Auditing competitor AI discoverability

“I want to know if my competitor shopify.com has an llms.txt file — check if it's there, what the HTTP status is, and how large it is.”

Monitoring partner site llms.txt availability

“Can you verify whether docs.anthropic.com currently has an llms.txt file and tell me its size and a snippet of what it says?”

Technical details

Endpoint

GEThttps://milliapi.com/api/llms-txt-check

When to prefer

Side effects

URL is not publicly accessible — returns an error or unreachable status
Site returns a non-standard redirect that obscures llms.txt location
llms.txt exists but is too large for preview — preview may be truncated
Invalid or malformed URL input — request rejected with validation error
Site blocks automated HTTP requests — may return 403 or timeout

Output

Schema · Response

{
  "type": "json",
  "example": {
    "origin": "https://example.com",
    "llmsTxt": {
      "bytes": 0,
      "status": 404,
      "present": false,
      "preview": null
    }
  }
}