Using Treezor documentation with AI assistants

Treezor supports the llms.txt proposal and publishes documentation in formats that AI assistants and development agents can retrieve directly.

Choose the right source

Need	Recommended source
Discover relevant documentation	/llms.txt
Read one topic	Per-page Markdown (use the Download as Markdown button)
Verify methods, parameters, enums, schemas	OpenAPI YAML files
Explore the API interactively	Scalar viewers in API References
Bulk import or offline indexing	/llms-full.txt

Documentation index

Start with /llms.txt to discover which pages are relevant to your task. Retrieve only what you need rather than loading the full documentation.

OpenAPI specifications

Use guides for workflows and business logic. Verify exact HTTP methods, paths, parameters, required fields, enums, and schemas against the OpenAPI contracts:

• Treezor API – Main API contract
• PCI DSS API – Card-sensitive endpoints
• Webhooks – Webhook payloads

The API References section provides interactive Scalar viewers for exploring endpoints — these are for human use, not agent ingestion.

Bulk documentation file

/llms-full.txt contains the complete documentation in a single file (~1.9 MB, ~48K lines). Use this for offline indexing or bulk import. For interactive work, prefer the index plus targeted retrieval.

Suggested agent instruction

Use /llms.txt as the documentation index.

Retrieve only the Markdown pages relevant to the task. Use Treezor guides 
for workflows and business behavior. Verify exact methods, paths, parameters, 
required fields, enums, and schemas against the OpenAPI specifications.

Do not invent undocumented fields or behavior. Report any conflict between 
a guide and an API contract.

Limitations

• The llms-full.txt file may contain VitePress formatting artifacts
• Some internal links in the Markdown output may not resolve when fetched directly
• OpenAPI files are renamed with date suffixes on deployment — the links above point to the source files