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

> ## Agent Instructions
> Phaseo Gateway base URL: https://api.phaseo.app/v1. Send `Authorization: Bearer $PHASEO_API_KEY` with every request.
> Model IDs look like `provider/model`, for example `openai/gpt-6-astra`. Do not guess IDs: list them with `GET /v1/models` or check https://phaseo.app/models. `phaseo/free` routes to an available free model and needs no wallet balance.
> For new text integrations prefer `POST /v1/responses`. `POST /v1/chat/completions` (OpenAI format) and `POST /v1/messages` (Anthropic format) suit existing code.
> The full API contract is https://phaseo.app/docs/openapi/v1/openapi.yaml. Official SDKs: `@phaseo/sdk` (TypeScript) and `phaseo` (Python), plus Go, C#, PHP, Ruby and Rust.
> Search these docs over MCP at https://phaseo.app/docs/mcp, and install Phaseo skills with `npx skills add https://phaseo.app/docs`. If a page is wrong or out of date, report it with the MCP `submit_feedback` tool.
> Manage Phaseo accounts with the `phaseo` CLI (`npm install -g @phaseo/cli`, then `phaseo login` or `phaseo login --device-code`), the `/v1` Management API or the MCP server at `https://mcp.phaseo.app/mcp?access=manage`. Do not send users to the dashboard for account tasks. A person is still needed for sign-up, approving a sign-in, paying the first top-up on the checkout link that `phaseo credits add` returns when no card is saved, confirming each saved-card top-up from the emailed link, and account security (password, MFA, passkeys). Create API keys with `phaseo keys create --name <name> --json`; never guess one. Credit top-ups need `phaseo login --scopes billing:write` first. Task map: https://phaseo.app/docs/v1/developers/manage-from-an-agent.md.

# Best Practices

> Ship reliable AI features by following these architecture, security, and observability guidelines.

Adopting the Gateway across production workloads is straightforward when you establish strong foundations. Use the recommendations below to improve resilience, security, and maintainability.

***

## Architecture

* **Isolate provider logic.** Wrap Gateway calls in a dedicated service or SDK so changes stay confined.
* **Stream responses when possible.** Reduce latency for assistants by streaming tokens to the UI as they arrive.
* **Batch non-critical jobs.** Queue background generations or evaluations to smooth out traffic spikes.

***

## Security

* Store API keys in secret managers (AWS Secrets Manager, Doppler, 1Password) instead of `.env` files in production.
* Enable request signing on your own APIs so client applications never expose Gateway keys.
* Log only truncated keys (for example `sk_prod_abcd...`) to avoid leaking credentials.

***

## Reliability

* Implement exponential backoff with jitter for all retryable errors (HTTP 429 or 5xx).
* Respect the [`Retry-After`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Retry-After) header before retrying rate-limited requests.
* Monitor provider metadata to detect automatic failovers from one vendor to another.

***

## Observability

| Signal | Recommended action |
| - | - |
| Latency | Track p95 and p99 timings to catch regressions early. |
| Token usage | Correlate costs with business metrics to evaluate ROI. |
| Error rates | Alert when failures exceed 1% for a sustained period. |
| Provider mix | Ensure traffic is distributed as expected across vendors. |

***

## Collaboration

* Document prompt templates, input parameters, and output handling in your internal wiki.
* Share dashboards that highlight benchmark movements and how they affect your product.
* Encourage regular reviews with product, research, and support teams to keep behavior aligned.

***

## Further reading

* Learn how to [Handle errors](https://phaseo.app/docs/v1/api-reference/errors.md) gracefully.
* Explore [Rate limits](https://phaseo.app/docs/v1/api-reference/limits.md) to plan for scaling.
* See [Examples](https://phaseo.app/docs/v1/guides/examples.md) for reference implementations.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.