# LLM Usage Policy

This project allows controlled AI usage of its public API and documentation.

## Allowed for AI / LLM

- API documentation: https://validatethis.org/developers
- Full capability discovery: GET https://validatethis.org/api/v1/status (returns all 33 tools, endpoints, pricing, limits)
- Validation examples and tool descriptions on each tool page and /tools
- Tool sections: /tools (trust & scam checks), /validators (data & format validators), /seo (technical SEO tools), /security (security & developer tools), /ai (AI visibility / AEO tools), /api (API & webhook tools)
- SEO and how-to pages: /guides/, /json-error/, /html-error/, /csv-error/, /xml-error/, /yaml-error/, /xsd-error/, /api-response-error/, /soap-response-error/, /ci-config-error/, /regex-error/, /match-debugger-error/, /env-file-error/, /log-file-error/, /error-pattern-error/, /base64-error/, /log-format-error/, /secrets-error/, /hash-error/, /datetime-error/, /robots-error/, /sitemap-error/, /schema-org-error/, /uuid-error/, /webhook-payload-error/

## API (machine-readable)

- GET https://validatethis.org/api/v1/status — discover all tools and endpoints (json, html, csv, xml, yaml, xsd, config-structure, ci-config, api-response, soap-response, robots, regex, pattern, env-file, env-syntax, secrets, log-file, error-pattern, log-format, base64, checksum, hash, datetime, iso-compliance, timestamp, uuid, id-collision, format, webhook-payload, signature, replay, schema)
- POST /api/v1/validate/<tool> and POST /api/v1/check/*, POST /api/v1/test/* — one endpoint per tool
- GET https://validatethis.org/api/v1/example?tool=<tool>&slug=<slug> — prefill example from error guides

Deterministic output. No side effects. Explicit error codes and line/column when applicable.
Ideal as external verification layer for AI workflows. All 33 tools are API-accessible.

Rate: without an API key, 500 successful v1 calls per public IP per calendar day (all tools combined). With a key: monthly quota per key (see /api/v1/status). At most 3 API keys (vt_*) per account; create via POST /api/keys when authenticated, delete with DELETE /api/keys/{id}.