> ## 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 --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. # Mini App Starter Prompts > Copyable prompts for coding agents to build small Phaseo apps with raw HTTP, SDKs, or agent runtimes. Use this page when you want to hand a coding agent one concrete prompt that produces a small, working app shape instead of a vague integration plan. > [!TIP] > > These prompts are written to be outcome-focused and implementation-specific so they work better in Cursor, Claude Code, Codex, and similar tools. ## How to use these prompts **1. Pick the integration surface** Choose the prompt that matches how you want the app to call Phaseo: * raw HTTP * one official SDK * Vercel AI SDK * Agent SDK **2. Replace the bracketed variables** Fill in values like `[APP IDEA]`, `[FRAMEWORK]`, `[MODEL]`, and `[LANGUAGE]` before you paste the prompt into your coding agent. **3. Ask for verification, not just code** Keep the verification lines in the prompt. They force the agent to report what it actually ran, what it assumed, and what still needs manual setup. ## Prompt packs > [accordion] Raw HTTP mini app > > Build a small app that uses **raw HTTP** against Phaseo instead of an SDK. > > You are implementing a small production-style demo app with Phaseo Gateway. > > Build a \[FRAMEWORK] mini app for \[APP IDEA]. > > Requirements: > \- Use raw HTTP requests, not A Phaseo SDK. > \- Use the Phaseo endpoint \[ENDPOINT]. > \- Use model \[MODEL]. > \- Read the API key from an environment variable named PHASEO\_API\_KEY. > \- Keep the app intentionally small: one main page, one server route or handler, and minimal styling. > \- Show the user input, the request submission state, the model output, and any gateway error state. > \- Add one example request payload in comments or docs so the integration is easy to audit later. > > Implementation details: > \- Use fetch. > \- Keep the request body explicit instead of hiding fields behind abstractions. > \- Add basic validation for empty input before making the API request. > \- Handle non-200 responses cleanly and surface the response body when useful. > \- Keep secrets server-side only. > > Deliverables: > \- The app code. > \- A short README section explaining how to run it. > \- A .env.example entry for PHASEO\_API\_KEY. > > Verification: > \- Run the local app if possible. > \- Verify one successful request path. > \- Report exactly what you verified, what you could not verify, and any remaining assumptions. > [accordion] TypeScript SDK mini app > > Build a mini app on the **TypeScript SDK** with a small, inspectable integration. > > You are building a small app on top of the Phaseo TypeScript SDK. > > Create a \[FRAMEWORK] mini app for \[APP IDEA]. > > Requirements: > \- Use @phaseo/sdk. > \- Use model \[MODEL]. > \- Prefer the responses API unless there is a strong reason to use another endpoint. > \- Read the API key from PHASEO\_API\_KEY. > \- Keep the code compact and understandable for a first integration. > \- Show loading, success, and failure states in the UI. > > Implementation details: > \- Use one server-side integration boundary instead of scattering SDK calls across many files. > \- Keep the request shape explicit, including model, input, and any important options. > \- Include one example of response parsing that extracts the final assistant text safely. > \- Add minimal comments only where the SDK response shape would otherwise be unclear. > > Deliverables: > \- Working app code. > \- Short setup instructions. > \- One short explanation of why the TypeScript SDK path is better than raw HTTP for this mini app. > > Verification: > \- Run the app if possible. > \- Exercise one end-to-end request. > \- Report the exact files changed and any remaining setup the user must do. > [accordion] Python SDK mini app > > Build a small Python app or service using the **official Python SDK**. > > You are implementing a small AI-powered Python app with Phaseo Gateway. > > Build a \[PYTHON FRAMEWORK OR APP TYPE] app for \[APP IDEA]. > > Requirements: > \- Use the official Python SDK phaseo. > \- Use model \[MODEL]. > \- Read credentials from PHASEO\_API\_KEY. > \- Keep the code small enough for a new team member to understand quickly. > \- Include one user input path and one model output path. > \- Include clean error handling for invalid input and upstream gateway failures. > > Implementation details: > \- Prefer one integration module that owns the Phaseo client creation. > \- Use the SDK response shape directly rather than wrapping it in unnecessary abstractions. > \- If structured output is useful for the app, use it and validate the returned shape. > \- Add a short README section with install and run steps. > > Deliverables: > \- App code. > \- Any dependency updates. > \- Short usage instructions. > > Verification: > \- Run the relevant command if possible. > \- Verify one successful request path or explain why you could not. > \- Call out any environment variables or local services the user still needs. > [accordion] Vercel AI SDK mini app > > Build a small app using **Phaseo through the Vercel AI SDK**. > > You are building a mini app that uses Phaseo through the Vercel AI SDK provider. > > Create a \[FRAMEWORK] app for \[APP IDEA]. > > Requirements: > \- Use the Phaseo Vercel AI SDK provider. > \- Use model \[MODEL]. > \- Read the Phaseo API key from PHASEO\_API\_KEY. > \- Keep the UX lightweight and oriented around one clear user task. > \- Support streamed output if the app is chat-like; otherwise explain why non-streaming is simpler here. > > Implementation details: > \- Keep the provider wiring explicit. > \- Use the AI SDK primitives in a standard, framework-appropriate way. > \- Avoid unnecessary extra state management for the first version. > \- Add one short explanation of how the provider model id is chosen. > > Deliverables: > \- App code. > \- Setup steps. > \- A brief note on how to switch to a different model later. > > Verification: > \- Run the app if possible. > \- Verify the main user flow. > \- Report any unverified parts separately. > [accordion] Agent SDK mini app > > Build a small app with the **Phaseo Agent SDK** and one bounded tool loop. > > You are building a small agentic app on top of Phaseo Gateway. > > Create a \[LANGUAGE] mini app for \[APP IDEA] using the Phaseo Agent SDK. > > Requirements: > \- Use the Phaseo Agent SDK for \[LANGUAGE]. > \- Use model \[MODEL]. > \- Include one or two deterministic local tools only. > \- Keep the tool loop bounded and easy to debug. > \- Read the API key from PHASEO\_API\_KEY. > \- Show the final output and, where appropriate, the tool activity or intermediate reasoning state. > > Implementation details: > \- Keep the agent definition in one place. > \- Keep tool definitions small and deterministic. > \- Avoid a giant general-purpose agent framework for the first version. > \- Add a note about where run state would be persisted if the app later becomes resumable. > > Deliverables: > \- App code. > \- Setup instructions. > \- A short explanation of why the Agent SDK is better than a one-shot completion for this workflow. > > Verification: > \- Run the main path if possible. > \- Verify one end-to-end agent run. > \- Report any remaining assumptions, especially around environment setup or local tool dependencies. ## How to make the prompts work better * Replace `[APP IDEA]` with one narrow user job, not a broad product pitch. * Replace `[MODEL]` with the exact model id you want the agent to use. * Say whether the output should be free text, strict JSON, chat, or one generated asset. * Mention the UI framework and deployment target when you know them. * Add one or two constraints that matter, such as `EU-only providers`, `use streaming`, or `keep all secrets server-side`. ## Related guides * [Quickstart](https://phaseo.app/docs/v1/quickstart.md) * [Examples](https://phaseo.app/docs/v1/guides/examples.md) * [TypeScript SDK overview](https://phaseo.app/docs/v1/sdk-reference/typescript/overview.md) * [Python SDK overview](https://phaseo.app/docs/v1/sdk-reference/python/overview.md) * [Agent SDK overview](https://phaseo.app/docs/v1/sdk-reference/agent-sdk/overview.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.