Skip to main content
llms.txt ready

Documentation for AI agents

Piano Analytics developers documentation are exported in formats designed for large language models, following the llmstxt.org standard. Use these files to ground coding agents, chatbots, and RAG pipelines on accurate, up-to-date reference material.

Which file should I use?

Pick the lightest file that gives your agent enough context. Indexes are cheap; full content is powerful but heavy.

Explore & route

Let your agent scan the index and fetch only the pages it needs.

llms.txt

Ingest everything

Load the full corpus in one request when context window allows.

llms-full.txt

Focus on one area

Use a section index to keep the context lean and relevant.

  • Collect datallms-data-collection.txt
  • Extract datallms-data-api.txt
  • Access managementllms-configuration.txt

Deep-dive one topic

Fetch a single page markdown URL from any index entry.

*.md

Available files

llms.txt

Master index of the entire documentation. Each entry links to a machine-readable .md page with a one-line summary.

Best for: Starting point for any AI agent — discover topics and route to the right pages.

https://developers.piano.io/analytics/llms.txt

llms-full.txt

Complete documentation content in a single file, following the llmstxt.org standard.

Best for: One-shot ingestion when you need everything. Large file (~13k+ lines).

https://developers.piano.io/analytics/llms-full.txt

llms-data-collection.txt

Index scoped to Collect data — SDKs, events, consent, collection API, and more.

Best for: Implementing tracking, SDK integration, or event collection.

https://developers.piano.io/analytics/llms-data-collection.txt

llms-data-api.txt

Index scoped to Extract data — Reporting API v3 parameters, methods, and errors.

Best for: Building data extraction pipelines or API integrations.

https://developers.piano.io/analytics/llms-data-api.txt

llms-configuration.txt

Index scoped to Access management — users, teams, and API routes.

Best for: Automating user and team provisioning via the Access Management API.

https://developers.piano.io/analytics/llms-configuration.txt

Per-page markdown files

Every documentation page also has a standalone .md export. Links in the index files point to these URLs — not to the human-readable HTML pages.

Pattern: https://developers.piano.io/analytics/<route>.md

Example: data-api/getting-started/authentication.md

https://developers.piano.io/analytics/data-api/getting-started/authentication.md

Quick start

Fetch an index or a single page from the command line:

curl -s https://developers.piano.io/analytics/llms.txt
curl -s https://developers.piano.io/analytics/llms-data-collection.txt
curl -s https://developers.piano.io/analytics/data-collection/sdks/javascript.md

Example prompts

Copy and adapt these instructions for your AI tool of choice:

Cursor / Windsurf rule

When answering questions about Piano Analytics developer documentation: 1. Fetch https://developers.piano.io/analytics/llms.txt first. 2. Identify relevant .md URLs from the index. 3. Fetch only those .md pages — do not guess API details. 4. Prefer llms-data-collection.txt for SDK/event questions and llms-data-api.txt for Reporting API questions.

ChatGPT / Claude project instruction

You have access to Piano Analytics developers documentation via llms.txt exports. Start with the section index that matches the user's question: - Data collection & SDKs → llms-data-collection.txt - Reporting API → llms-data-api.txt - Access management → llms-configuration.txt Follow links to individual .md pages for authoritative answers.

RAG / agent workflow

Index step: ingest llms.txt (or a section file) as your routing catalog. Retrieval step: fetch targeted .md URLs listed in the index — avoid llms-full.txt unless you need site-wide context. Summaries in the index come from each page's "description" frontmatter field.

This site follows the llmstxt.org convention.