Skip to main content
APOB exposes a remote Model Context Protocol (MCP) endpoint at /mcp using Streamable HTTP. A connected client can discover tools for generation, models, elements, media transfer, Live scenes, and billing. The server also provides a resource describing the required create_image prompt syntax.

​
Connect your client

1

Obtain the MCP resource URL

Use the URL supplied by your integration. The endpoint must be enabled in that environment. These examples use APOB_MCP_URL for the complete resource URL, including /mcp; they do not assume a production hostname.
2

Authorize the connection

Add the remote endpoint in an MCP client that supports Streamable HTTP and OAuth authorization code with PKCE. Sign in to APOB and review the account and client before approving mcp:access. See authentication.
3

Discover the current tools

Initialize the client, then request tools/list. Use the returned input schemas for your account. Some generation defaults change with the account’s free or paid status and selected quality.
4

Submit once and follow the receipt

Check inputs, credits, and billing settings before a write. Save returned identifiers and follow the existing task. Acceptance is separate from final media, payment, or entitlement fulfillment.
MCP uses an OAuth access token. GraphQL uses an APOB API key or Firebase ID token. An APOB API key, Firebase ID token, or browser session cookie does not replace the MCP bearer token.

​
Choose a reference

Authentication

Discover OAuth endpoints, authorize with PKCE, and manage connected apps.

HTTP and JSON-RPC

Initialize, discover capabilities, call tools, and interpret errors.

Tool catalog

Find all 34 tools and understand account-specific defaults.

Generation

Create, edit, clone, extend, and retrieve final media.

Library and elements

Discover assets, train models, and manage reusable references.

Uploads and Live

Transfer local files, import remote files, and create or vote on scenes.

Billing

Inspect offers and accounts, submit purchases, and follow Checkout status.

Connected apps API

Retrieve setup instructions, list connections, and revoke access through GraphQL.

​
Account and task boundaries

Tool identity comes from the verified connection. Each call rechecks the account; knowing another account’s identifier does not grant access to its private assets. Generation results are restricted to the owner of the root generation task. Creation and billing writes can spend credits or charge a saved payment method. Repeated writes can execute again. If a response is uncertain, reconcile the existing task, account history, or payment before considering another write. Read credits and billing before running paid work. The setup instructions returned by the GraphQL API describe client configuration. Successful use also depends on the enabled endpoint and the client’s transport and OAuth support.