API

Background Generation API

Background Generation is a api from gamma that teams use to call background generation through one stable api surface through one SkillBoss endpoint.

It returns structured output from model gamma/background_generation, supports pay as you go billing, and gives agents a stable invocation contract instead of vague routing hints.

Call Background Generation through one stable API surface

Ship integrations faster without vendor account setup

Use the capability directly inside human and agent workflows

Direct Answer

What this API does

Background Generation is a api exposed through SkillBoss. Use it when you need to call background generation through one stable api surface, want one stable request surface, and need a model ID and billing path that both humans and agents can act on quickly.

Best Fit

You want Background Generation behind one stable SkillBoss endpoint instead of wiring up gamma directly.

You need a canonical page with copyable request shape, pricing context, and model ID for developer handoff or agent routing.

You are comfortable using the standard API key path for token-based or variable-cost execution.

Watchouts

This API is not a strong x402 or Payment Later fit today because the final cost is not deterministic before execution.

If you need a different capability category, use the catalog and vendor links below instead of forcing the wrong endpoint.

Capability Snapshot

Endpoint

POST /v1/run

Auth

Bearer API key

Model

gamma/background_generation

Payments

Standard API key

Canonical URL

https://www.skillboss.co/th/use/background-generation-api

How to invoke this API

Step 1

Send one POST request

Use https://api.skillboss.co/v1/run with a standard JSON body and your SkillBoss API key.

Step 2

Pin the exact model ID

Set "model": "gamma/background_generation" so your app or agent routes to the intended capability consistently.

Step 3

Choose the right billing path

This API should use the standard API key flow before machine payments. Keep the standard API key flow as the default unless your agent specifically benefits from machine-native payment rails.

Request Shape

Copyable JSON for agents and developers

Pay as you go
{
  "model": "gamma/background_generation",
  "inputs": {
        "prompt": "Run a sample request with Background Generation."
      }
}

Example Response

{
  "id": "run_123",
  "output": {
    "status": "completed"
  }
}

For Humans

Where teams use this API

Developers embedding Background Generation inside apps quickly

Operators running repeatable workflows from one API key

Teams standardizing on one billing and auth layer instead of many

For Agents

How this fits agent workflows

Background Generation inside agent loops that need a stable capability URL

Automations that benefit from one auth model across many APIs

Multi-step agents that need direct, copyable invocation patterns

Best Use Cases

Call Background Generation through one stable API surface

Ship integrations faster without vendor account setup

Use the capability directly inside human and agent workflows

Quick Start

cURL

curl -X POST https://api.skillboss.co/v1/run \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gamma/background_generation",
    "inputs": {
          "prompt": "Run a sample request with Background Generation."
        }
  }'

Python

import requests

response = requests.post(
    "https://api.skillboss.co/v1/run",
    headers={
        "Authorization": "Bearer YOUR_API_KEY",
        "Content-Type": "application/json"
    },
    json={
        "model": "gamma/background_generation",
        "inputs": {
              "prompt": "Run a sample request with Background Generation."
            }
    }
)

print(response.json())

Payment Options

x402 and Payment Later

This API should use the standard API key flow before machine payments. This endpoint is priced by tokens or variable execution cost, so the final price is not deterministic before the run completes. That makes x402 and Payment Later secondary options rather than the primary billing path.

x402

USDC on Base

Status: Not recommended. Use x402 when an agent can know the exact price before execution and pay onchain request by request.

Payment Later

Stripe-backed machine payments

Status: Not recommended. Use Payment Later when an agent should pay with card-backed machine payments instead of prefunded crypto.

x402 Code

# Background Generation uses variable or token-based pricing,
# so x402 is not the primary path for this model today.

import requests

response = requests.post(
    "https://api.skillboss.co/v1/run",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
    json={
        "model": "gamma/background_generation",
        "inputs": {
              "prompt": "Run a sample request with Background Generation."
            }
    }
)

print(response.json())

Payment Later Code

# Background Generation does not have deterministic pricing up front,
# so Payment Later is not the primary path for this model today.

import requests

response = requests.post(
    "https://api.skillboss.co/v1/run",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
    json={
        "model": "gamma/background_generation",
        "inputs": {
              "prompt": "Run a sample request with Background Generation."
            }
    }
)

print(response.json())

Why this page is easier to discover and route

Canonical

One stable cited URL

The canonical page, model ID, and request surface are visible above the fold, which reduces ambiguity for searchers and agents.

Extractable

Decision blocks before detail

Direct-answer, best-fit, watchout, and invocation sections expose the critical facts in short standalone passages.

Operational

Launch-ready payment guidance

Payment guidance is separated from quick start, so users can launch first and choose x402 or Payment Later only when it actually fits.

Frequently Asked Questions

What is the Background Generation API used for?

Background Generation is a api available through SkillBoss. Teams use it for call background generation through one stable api surface without managing separate vendor credentials.

What inputs does Background Generation require?

Send a POST request to https://api.skillboss.co/v1/run with "model": "gamma/background_generation" and an "inputs" object containing the capability-specific parameters shown in the request example on this page.

What does a successful response look like?

Successful responses return a run identifier plus a structured output payload. The exact shape varies by capability, and this page shows a representative example response block so developers and agents can plan parsing correctly.

Is pricing per request or per token?

Background Generation uses pay as you go pricing on SkillBoss. Check the pricing card and payment section on this page before wiring billing logic into your app or agent.

When should I use x402 or Payment Later instead of a standard API key?

This API should use the standard API key flow before machine payments. This endpoint is priced by tokens or variable execution cost, so the final price is not deterministic before the run completes. That makes x402 and Payment Later secondary options rather than the primary billing path.

What is the native vendor behind this API?

The underlying vendor for this endpoint is gamma. SkillBoss provides the unified API surface, billing layer, and canonical discovery page for Background Generation.

Ready to use Background Generation?

Get your API key, call gamma/background_generation, and use this capability in both product workflows and AI agents.