Skip to main content
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.

API keys

Create a key, choose what it can reach, and disable it when you’re done.

Claude skill

Generate images, video, and audio directly from a conversation with Claude.

Agents & plugins

Let an external app request access to your Pixio account, and revoke it later.

What you can automate

The honest list — what’s supported, and what isn’t.

​
Which one do I want?

​
How it works

1

Create a key

In the app, open Integrations and create an integration key. Name it after where it’ll be used.
2

Choose its reach

Keys are scoped. Grant only the areas the integration actually needs.
3

Authenticate

Send the key as a Bearer token. Every request is billed to the same credit balance as the app.
4

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.

​
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
Failed generations aren’t charged, through the API just as in the app.

​
Reference

The complete endpoint reference — every model, operation, and parameter, with copyable request examples — lives in the app at /api-docs. It’s generated from the catalog and the API’s own specification, so it can’t drift from the real behavior.
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.