> ## Documentation Index
> Fetch the complete documentation index at: https://yn-c9bb3266.mintlify.app/llms.txt
> Use this file to discover all available pages before exploring further.

# AGENTS

# Yuno docs — agent instructions

Yuno's payment API docs, built on [Mintlify](https://mintlify.com). Pages are MDX with YAML frontmatter; config in `docs.json`; API reference generated from `api-reference/openapi.json`.

## Commands

* `mint dev` — local preview
* `mint broken-links` — check internal links
* `python3 scripts/openapi_paths_parity.py` — CI-enforced: local `paths` must match [production openapi.json](https://docs.y.uno/api-reference/openapi.json)
* `python3 scripts/sync_openapi_from_official.py` — refresh API `info` (description, contact, license) from `~/yuno-docs-official/openapi.yaml` without changing `paths`
* `python3 scripts/generate_llms_txt.py` — regenerate `llms.txt` after any `docs.json` navigation change
* `python3 scripts/generate_missing_diagrams.py` — regenerate HTML diagrams under `diagrams/` (data in `all_diagrams()`)

## Authoritative sources

* API contract: `api-reference/openapi.json`. Do not invent paths, fields, enums, or status codes. If MDX disagrees with OpenAPI, trust OpenAPI and flag the doc.
* Agent first-reads: `llms.txt`, this file, `api-reference/openapi.json`.

## Terminology

* **checkout session** (not "session"), **payment method** (not "payment type"), **provider** (not "gateway" / "acquirer"), **Dashboard** (capitalized), **sandbox** (lowercase), **merchant**.
* REST headers in examples: `public-api-key`, `private-secret-key`. The merchant account identifier is `account_id` (a body field). **Never** use `account_code` or `account-code` in prose, headers, or code samples; it's an internal name.

## Style

* Second person, active voice, sentence case headings.
* Bold for UI (**Settings**), code formatting for files/commands/fields.
* Use `<Steps>` for procedures and `<CodeGroup>` for cURL / Node.js / Python samples.
* Obvious placeholders: `YOUR_PUBLIC_API_KEY`, `CUSTOMER_ID`.

## Boundaries

* Document only Yuno features. No competitor references, no internal tooling.
* Placeholder values only for keys / IDs in examples.
* MCP is sandbox/dev only — do not steer merchants to MCP for live payments.

## Diagrams

* Embed via `/diagrams/...` (same-origin iframes). Don't link external diagram hosts.