> ## 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.

# Workflow Automation

> Use Phaseo from Zapier, n8n, Pipedream, and other automation platforms.

Phaseo works today in automation products that can send authenticated HTTP requests. Native marketplace apps can provide a more guided experience later.

## Shared request

Use these settings in an HTTP, webhook, or code action:

| Setting | Value |
| - | - |
| Method | `POST` |
| URL | `https://api.phaseo.app/v1/responses` |
| Header | `Authorization: Bearer <PHASEO_API_KEY>` |
| Header | `Content-Type: application/json` |

```json theme={null}
{
  "model": "openai/gpt-5-nano",
  "input": "Summarise the supplied workflow data in one paragraph."
}
```

Store the Phaseo API key in the platform's credential or secret store. Do not place it directly in a shared workflow definition.

## Zapier

Use **Webhooks by Zapier → Custom Request**:

1. Select `POST`.
2. Enter `https://api.phaseo.app/v1/responses`.
3. Add the bearer and content-type headers.
4. Map fields from earlier Zap steps into `input`.
5. Test the Zap with non-sensitive data.

A native Phaseo Zapier app would add model selection, structured-output actions, and Phaseo-specific authentication, but it requires publication through Zapier's developer platform.

## n8n

Use the **HTTP Request** node with bearer authentication and a JSON body. For structured workflow data, map the upstream item into the `input` field with an n8n expression.

A first-party n8n community node can later expose operations such as Generate Response, List Models, Get Model Pricing, and Create Embedding without manual HTTP setup.

## Pipedream

Use an HTTP request step or a Node.js code step. Store `PHASEO_API_KEY` as a Pipedream secret and read it from the step environment.

## Production guidance

* Set a spending limit on the Gateway API key used by each automation.
* Give each automation its own key so usage and revocation remain isolated.
* Use structured outputs when downstream steps expect machine-readable fields.
* Add retry handling for `429` and recoverable `5xx` responses.
* Avoid retrying non-idempotent external actions merely because a model step was retried.

## Related

* [Responses](https://phaseo.app/docs/v1/api-reference/endpoint/responses.md)
* [Structured Outputs](https://phaseo.app/docs/v1/guides/structured-outputs.md)
* [Error Handling](https://phaseo.app/docs/v1/api-reference/errors.md)


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