Docs API reference
Markdown Get an API key

REST APIapi.sogni.ai

Your next idea
has an API.

Images, video, music, and agent workflows, in your stack and behind your interface. Make something we wouldn't have thought of.

Get an API keyRead the conventions

Sogni's pink sloth in glasses and a black work jacket, making things in a rain-lit studio with a synthesizer and GPU computer.
Independent minds. After hours. Artwork made with Sogni

Your first call One request. The model picks up Sogni's creative tools and returns an image URL.

curl https://api.sogni.ai/v1/chat/completions \
  -H "Authorization: Bearer $SOGNI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "messages": [
      { "role": "user", "content": "Generate a cinematic image of a neon alley in Tokyo during rain." }
    ]
  }'

The Supernet runs on GPU capacity contributed by independent operators, including people running hardware at home. People-powered compute, for people with their own ideas.

New here? Start with authentication and conventions. Already building? Pick your next move below. Every endpoint shows its full versioned path; you'll see /v1, /v2, and /v4 resources here.

Before you hit send. Public reads and account operations have different access rules. Check authentication before you call, keep API keys on your server, and give polling requests room to breathe.

Pick your next move

Make something. Check on it. See what's available. Every endpoint in the reference, grouped by what you're trying to do.

Getting started

Getting Started

Authentication, versioning, errors, rate limits, idempotency, and billing.

Generation

Chat and agents

Media and accounts

Network

Resources

Previously shared section links

Existing bookmarks still work. Each section now has a focused reference page.