# Proksusha — rules for coding agents

When the user asks to integrate Proksusha / goproxy / «Проксюша»:

1. Read `/llms-full.txt` (or this file + `/api`) before inventing endpoints.
2. Treat `ru.proksusha.ru` / `de.proksusha.ru` as placeholders only.
3. Always separate secrets:
   - Gateway: `X-Api-Key: pk_live_…`
   - Upstream: `X-Upstream-Authorization` / `X-Upstream-X-*`
4. Prefer `/v1/proxy` for API calls, `/v1/fetch` for file GET, `/o/{slug}` for CDN, `/in/{token}` for webhooks.
5. Default routing hint for RU clients: `X-Chain: ru->de` unless told otherwise.
6. Logs are **off by default**. Enable: `PATCH /v1/me/settings` `{ "logging_enabled": true }`. Then (JWT, last 20): `GET /v1/logs?key_id=…`, `GET /v1/logs?node=…`, or `GET /v1/nodes/{id}/logs`.
7. Never recommend system VPN as this product.
8. Never call `/internal/*` from user apps.
9. On missing credentials: ask user to request access via support@proksusha.ru.
10. Generate copy-paste code in the language the user uses (curl/Python/Node/Go/PHP examples exist on `/examples`).
11. Surface errors as `{"error":"…"}` and map 401/403/502 correctly.

Canonical full guide: `/llms-full.txt`
Index: `/llms.txt`