Providers

Bring your own media stack.

Route agents through OpenAI, FAL, Google, and custom provider adapters without rewriting the workflow.

agents
01Claude Code
02Codex
03Hermes
04Custom agents
pixa gatewayOne contract. Any provider.

Agents stay in control while Pixa handles adapter routing, cache state, and workflow outputs.

adapter graphprovider matched by capability
Provider adapters

Swap models without changing agent behavior.

Pixa adapters normalize provider-specific inputs, outputs, and errors into workflow primitives that agents can inspect and reuse.

01

Provider Neutral Calls

Agents call one workflow contract while Pixa selects the model, adapter, cache path, and output shape.

02

Adapter-Level Memory

Prompts, inputs, provider responses, masks, and generated assets stay attached to the workflow run.

03

Production Routing

Pin a provider, fail over by capability, or expose provider choice as a workflow input.

Bring your own provider

Run open workflows against the stack you already trust.

Use the built-in adapters, fork them, or add your own provider layer while keeping PixaScript workflows portable.

Read provider docs