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

# Integrations

> Connect Pixio to the tools you already work in

Everything you can do in the Pixio app, you can do from somewhere else — your own code, an AI assistant, or an automation. One integration key unlocks all of it.

<CardGroup cols={2}>
  <Card title="API keys" icon="key" href="/integrations/api-keys">
    Create a key, choose what it can reach, and disable it when you're done.
  </Card>

  <Card title="Claude skill" icon="robot" href="/integrations/claude-skill">
    Generate images, video, and audio directly from a conversation with Claude.
  </Card>

  <Card title="Agents & plugins" icon="puzzle-piece" href="/integrations/agents-and-plugins">
    Let an external app request access to your Pixio account, and revoke it later.
  </Card>

  <Card title="What you can automate" icon="list-check" href="/integrations/what-you-can-automate">
    The honest list — what's supported, and what isn't.
  </Card>
</CardGroup>

## Which one do I want?

| If you want to…                            | Use                                                                                 |
| ------------------------------------------ | ----------------------------------------------------------------------------------- |
| Generate from your own script or backend   | An **API key** plus the [live API reference](https://beta.pixio.myapps.ai/api-docs) |
| Create from a chat with Claude             | The **[Pixio skill](/integrations/claude-skill)**                                   |
| Let a third-party tool act on your account | **[Plugin authorization](/integrations/agents-and-plugins)**                        |
| Run a chain you've already built in Pixio  | An API key — saved **workflows** are callable                                       |
| Build ComfyUI graphs and call them         | **[Pixio ComfyUI](/comfyui/overview)**, a separate product with its own API         |

## How it works

<Steps>
  <Step title="Create a key">
    In the app, open **Integrations** and create an integration key. Name it after where it'll be used.
  </Step>

  <Step title="Choose its reach">
    Keys are scoped. Grant only the areas the integration actually needs.
  </Step>

  <Step title="Authenticate">
    Send the key as a Bearer token. Every request is billed to the same credit balance as the app.
  </Step>

  <Step title="Generate and poll">
    Start a generation, then poll it until it finishes. Results land in your assets exactly as if you'd made them in the app.
  </Step>
</Steps>

## Same account, same credits

An integration isn't a separate world. Anything created through a key:

* **Costs the same credits** as it would in the app
* **Respects your plan** — a model your plan can't run through the UI can't run through a key either
* **Appears in your assets** and generation history
* **Counts toward the same limits**

<Info>
  Failed generations aren't charged, through the API just as in the app.
</Info>

## Reference

The complete endpoint reference — every model, operation, and parameter, with copyable request examples — lives in the app at **[/api-docs](https://beta.pixio.myapps.ai/api-docs)**. It's generated from the catalog and the API's own specification, so it can't drift from the real behavior.

<Warning>
  Treat an integration key like a password. It can spend your credits. Never commit one to a repository or ship it in client-side code — keep it server-side, in an environment variable.
</Warning>