Which AI clients can connect?

Any client that supports remote MCP servers — Claude, Claude Code, ChatGPT, Cursor, Codex, VS Code, Antigravity and others. The server speaks Streamable HTTP at https://app.epox.ai/api/mcp.

Programmatic access is this one endpoint. Call it from any language as JSON-RPC 2.0 over HTTPS with a workspace API key — the same tools an agent uses, with the same scopes.

Should I use OAuth or an API key?

OAuth for any client that can open a browser sign-in — there is no key to store. Use a workspace API key for scripts, CI and clients without OAuth support; it is read-only unless an owner checks Allow generation when creating it.

Can an agent publish to my store?

No. An agent can read whether a store is connected, but the connection cannot publish to your store, delete anything, change settings or buy credits.

Does an agent spend credits?

Only with the generate scope, and only when it starts generation or an edit — the same charge as doing it in the app. The image, video, background-removal and upscale tools take a dry run that returns a credit estimate first.

tools/call · epox_start_video

{
  "name": "epox_start_video",
  "arguments": {
    "prompt": "The sneaker's shadow lengthens up the terracotta wall",
    "sourceImageId": "asset_…",
    "aspectRatio": "9:16",
    "duration": "8s"
  }
}

Rendered through the Epox MCP server

API & MCP

Put Epox in your agent, your scripts and your pipeline.

One endpoint for Claude, ChatGPT, Cursor and your own code. Read the catalog, create products, generate images and video — read-only until a workspace owner allows generation.

Open a free account →

600 credits / day · no credit card

Everything you do in Epox, one tool call away.

Claude Code

claude mcp add --transport http epox https://app.epox.ai/api/mcp

Cursor · mcp.json

{"mcpServers":{"epox":{"url":"https://app.epox.ai/api/mcp"}}}

Codex

codex mcp add epox --url https://app.epox.ai/api/mcp
codex mcp login epox

Connect

Add the server. Approve in the browser.

Claude, ChatGPT, Cursor, Codex, VS Code — any client that speaks remote MCP. Add the server and a workspace owner approves the connection; with OAuth there is no key to create or store.

Streamable HTTP · OAuth or a workspace API key.

Read the setup guide →

Read

Your whole workspace, readable.

Products and collections, generated assets, template packs, generation flows and jobs, automations and try-on analytics — plus the credit balance and this month's usage. Every connection can read.

Each credential is tied to one workspace, so no tool takes a workspace ID.

tools/call · epox_generate_images

{
  "name": "epox_generate_images",
  "arguments": {
    "dryRun": true,
    "items": [
      { "prompt": "Sneaker on a concrete plinth, terracotta wall", "aspectRatio": "1:1" },
      { "prompt": "Same sneaker, story crop, open sky above", "aspectRatio": "9:16" }
    ]
  }
}

Generate

Images and video, priced before they start.

Put a product into looks you describe or a saved pack, make images from prompts — up to 12 in one call — and render clips from a still, with start and end frames or several shots.

Every generating tool takes dryRun: the price and whether the plan allows it, nothing started.

Plan and check

Plan the shoot. Check the result.

Epoxy turns an idea into a storyboard your agent can render shot by shot, and a quality judge reviews what comes back — before anything reaches a listing.

Planning and checking spend no credits.

JSON-RPC 2.0 over HTTPS

curl https://app.epox.ai/api/mcp \
  -H "Authorization: Bearer epox_wsk_live_…" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"epox_workspace_summary","arguments":{}}}'

API keys

An API for your scripts and CI.

Call the same endpoint from your own code: JSON-RPC 2.0 over HTTPS, authorized with a workspace API key. An owner creates the key in Settings → API Keys; it is shown once.

A key is read-only unless Allow generation is checked when it is created.

Read the developer guide →

Scopes & safety

Read-only until an owner says otherwise.

Generating — adding photos, starting queued work, spending credits — needs the separate generate scope, which only a workspace owner can grant. A generation an agent starts passes the same plan check, credit charge and queue as one started in Epox.

Every credential

Two scopesmcp:read always · mcp:generate only if granted

Owners approveEvery owner is emailed; any owner can revoke

What it can never doPublish to your store, delete, change settings, buy credits

Bounded by defaultOAuth lasts up to 90 days · stored only as hashes

One workspace per credentialNo tool can reach another account

The app’s own rulesSame plan check, credits and queue as in Epox