# AIScan LLMs.txt Checker

> AIScan LLMs.txt Checker is a paid API for AI agents from api.getaiscan.app, paid per call via x402, $0.07/call, status unknown (last checked 2026-09-14).

Checks whether a website has a valid llms.txt file and evaluates its AI-readiness configuration

## Facts

- Endpoint: POST https://api.getaiscan.app/api/agent/check_llms_txt
- Price: $0.07/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aiscan-llms-txt-checker-0ed10b09
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wQopjSK8suTSbMo1nS6QR

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability aiscan-llms-txt-checker-0ed10b09 -d '<json body>'
```

Example prompt: Can you check if openai.com has an llms.txt file set up and whether it's properly configured for AI agent discoverability?

## When to prefer this

Use this endpoint specifically when you need to determine whether a website has an llms.txt file in place — a key signal of MCP and AI agent readiness. Choose this over a general AI visibility audit when you only need the llms.txt check specifically, not a full 4-score AEO/GEO/Agent/MCP audit.

## Known failure modes

- Invalid or malformed URL returns an error
- Site is unreachable or times out during the check
- Payment of $0.07 USDC not settled, resulting in 402 response
- URL missing scheme (e.g. missing https://) causes rejection
- Rate limiting or server errors on the target domain prevent analysis

## How this service works

AIScan audits any website for AI visibility in 60 seconds. 4 scores: AEO, GEO, Agent Readiness, MCP Readiness. Plus Brand Visibility: how often AI actually names your brand. The only scanner with MCP Readiness.

## Output

Returns a capability string confirming the check was executed, plus the analyzed site URL and payment settlement info. The core result indicates whether the llms.txt check was performed — the capability field describes what was run.

## Example request

```json
{
 "url": "https://example.com"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url"
 ],
 "properties": {
  "url": {
   "type": "string",
   "description": "Full URL of the website to analyze, e.g. https://example.com"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "capability"
 ],
 "properties": {
  "url": {
   "type": "string",
   "description": "Analyzed site URL"
  },
  "payment": {
   "type": "object",
   "description": "Payment settlement info"
  },
  "capability": {
   "type": "string",
   "description": "Capability that was executed"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aiscan-llms-txt-checker-0ed10b09/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.getaiscan.app](https://www.zero.xyz/host/api.getaiscan.app/llms.txt)