Scenario
Scenario is a Paris- and San Francisco-headquartered AI platform for game asset generation founded in 2021 by Emmanuel de Maistre and Hervé Nivon. The Scenario REST API lets game studios and creative teams generate consistent, on-brand images, video, audio, and 3D assets, train custom LoRA models on their own reference art, automate batch asset pipelines, and integrate AI-generated visuals into production tools like Unity. Scenario aggregates 500+ AI models from 50+ providers behind a single workspace and API, with full commercial licensing for generated assets and enterprise SSO, SOC 2 Type II, and governance controls.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Scenario the way a machine reads it — 23 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Scenario scores 23.1/100 (emerging), with a separate agent-readiness read of 16/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Scenario
Each block below is one kind of artifact we hold for Scenario. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Scenario Models API
List, inspect, and manage custom and base AI models available to a Scenario account. Returns training status, training progress, model type (image, video, audio, 3D), and metada...
Scenario Generation API
Generate game-ready images, video, audio, and 3D assets from text prompts, reference images, or ControlNet guides. Supports text-to-image, image-to-image, ControlNet (txt2img an...
Scenario Jobs API
Inspect the status, progress, metadata, and output assets of an asynchronous generation or training job. Generation and training requests return a jobId immediately; clients pol...
Scenario Assets API
List, retrieve, upload, and manage the images, video, audio, and 3D assets stored in a team's Scenario workspace. Includes endpoints for project-private assets, public asset ret...
Scenario Usage API
Retrieve unified compute-unit consumption for an account, filtered by date range, project, or model. Compute units match the metering used by the Scenario web application and ar...
Features 16
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 16 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Scenario — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 6
Reference material describing how the API behaves
Build 9
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 9 ·
Access & Security 3
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/scenario-gg · machine-readable index on apis.io