Amazon Nimble Studio

Name: Amazon Nimble Studio API
Brand: Amazon Nimble Studio
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent Deliveryhmac49 EndpointsREST

For Agents

Provision and manage cloud-based virtual studios for VFX, animation, and game artists — create studios, launch profiles, streaming sessions, and shared studio components.

Quickstart

Get started with Amazon Nimble Studio in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"start a Nimble Studio streaming session"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Amazon Nimble Studio API.

Provision a virtual Nimble Studio in a region with KMS encryption and admin/user IAM roles

Define StudioComponents that wire studios to shared file systems, license servers, and render farms

Create LaunchProfiles that bundle compute, storage, and software for an artist persona

Manage versioned StreamingImages — base AMIs of artist workstations with pre-installed creative software

GET STARTED

Start building with Amazon Nimble Studio API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Amazon Nimble Studio, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Amazon Nimble Studio, keeping it validated and agent-ready. Nimble Studio is AWS's managed virtual production studio for visual effects, animation, and game-development teams — it provisions cloud-based artist workstations and rendering capacity. The 49 endpoints cover Studios, StudioComponents (shared file systems, license servers, render farms), LaunchProfiles, StreamingImages, StreamingSessions and the streams that artists connect to, plus EulaAcceptances and StudioMembers for access control.

Use Cases

Patterns agents use Amazon Nimble Studio API for, with concrete tasks.

★ Stand Up a Cloud-Based VFX Studio

VFX and animation studios need to provision artist workstations on demand without buying hardware. Nimble Studio lets an agent provision a Studio, register StudioComponents for shared file systems and license servers, then create LaunchProfiles per artist persona. Artists request a StreamingSession against a profile and connect via NICE DCV, with all rendering and storage staying in the AWS region.

Call CreateStudio with a studioName and admin/user role ARNs, then CreateLaunchProfile referencing the studio's StudioComponents and a StreamingImage id

Burst Render Capacity Through Studio Components

Render farms see spiky demand around shot delivery. Nimble Studio's StudioComponents abstract over render-management systems (Deadline, Tractor) so an agent can register a managed or customer-managed render farm component and reference it from launch profiles. Artists submitting render jobs through the workstation see the configured farm without each artist needing to set up their own connection.

Call CreateStudioComponent with Type=RENDER_FARM and a Configuration referencing the render manager's hostname, then list it in the LaunchProfile's StudioComponentIds

Manage Artist Sessions for Cost and Access

Studios pay for compute by the hour and need tight control over which artists are running which workstations. The StreamingSessions sub-API lets an agent start, stop, and terminate sessions, list currently active sessions, and check ownership against StudioMembers. Combined with EULAs and IAM roles, this provides a complete access surface for the production environment.

Call ListStreamingSessions, identify sessions with State=READY and idle for >2 hours, then call StopStreamingSession to suspend them

AI Agent Integration for Studio Operations

Through Jentic, a studio operations agent can drive Nimble Studio entirely from natural-language intents — create studios, register components, manage launch profiles, start and stop sessions. Jentic returns each operation's input schema and brokers AWS credentials, so production engineers can build studio automation as LLM tool calls instead of bespoke Lambda scripts.

Resolve the intent 'start a Nimble Studio session for an artist' via Jentic search, load CreateStreamingSession, and execute it with studioId, launchProfileId, ec2InstanceType and ownedBy

Key Endpoints

49 endpoints — jentic publishes the only available openapi specification for amazon nimble studio, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/2020-08-01/studios

Create a new Nimble Studio

POST

/2020-08-01/studios/{studioId}/launch-profiles

Create a launch profile in a studio

POST

/2020-08-01/studios/{studioId}/streaming-sessions

Start an artist streaming session

POST

/2020-08-01/studios/{studioId}/streaming-sessions/{sessionId}/streams

Issue a stream URL for a session

POST

/2020-08-01/studios/{studioId}/streaming-images

POST

/2020-08-01/studios/{studioId}/eula-acceptances

Accept the EULAs required by studio software

POST

/2020-08-01/studios

Create a new Nimble Studio

POST

/2020-08-01/studios/{studioId}/launch-profiles

Create a launch profile in a studio

POST

/2020-08-01/studios/{studioId}/streaming-sessions

Start an artist streaming session

POST

/2020-08-01/studios/{studioId}/streaming-sessions/{sessionId}/streams

Issue a stream URL for a session

POST

/2020-08-01/studios/{studioId}/streaming-images

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS access keys live in the Jentic MAXsystem vault. Jentic signs each Nimble Studio request with SigV4 on the agent's behalf, so studio-operations automation never touches raw IAM credentials.

Intent-based discovery

Agents search by intent (e.g., 'start a Nimble Studio session') and Jentic returns the matching Nimble Studio operation with its input schema, so the agent can call CreateStudio, CreateLaunchProfile or CreateStreamingSession without browsing the AWS docs.

Time to first call

Direct Nimble Studio integration: 2-3 days for IAM and EULA wiring, launch-profile composition and session lifecycle handling. Through Jentic: under a day — search, load schemas, chain operations.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Amazon AppStream 2.0

AppStream 2.0 streams general-purpose Windows applications over a managed NICE DCV pipeline

Choose AppStream when streaming general-purpose business apps to end users. Use Nimble Studio for content-creation pipelines that need shared file systems, render farms, and creative-software EULAs.

Complementary

Amazon EC2

EC2 underpins the streaming instances and render workers that Nimble Studio orchestrates

Use directly when an agent needs lower-level instance and AMI control than Nimble Studio's launch-profile abstraction.

Complementary

AWS Elemental MediaStore

MediaStore stores and serves the rendered media output by a Nimble Studio production

Use to hold the finished rendered frames or VOD assets produced by a Nimble Studio pipeline.

FAQs

Specific to using Amazon Nimble Studio API through Jentic.

Why is there no official OpenAPI spec for Amazon Nimble Studio?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Nimble Studio via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Amazon Nimble Studio API use?

Nimble Studio is signed with AWS Signature Version 4 using IAM access keys. Studios additionally have admin and user role ARNs that gate which members can manage versus consume studio resources. Through Jentic, AWS credentials live in the MAXsystem vault and are used to sign requests on the agent's behalf.

Can I run third-party creative software on a Nimble Studio workstation?

Yes. StreamingImages are AMIs that you build with the required creative software (Maya, Houdini, Nuke, etc.) and register against a studio. Each StreamingImage tracks owner, encryption configuration and software-specific EULAs that members must accept before starting a session.

What are the rate limits for the Nimble Studio API?

AWS applies per-account control-plane throttling to Nimble Studio. Session start operations are not instantaneous — DescribeStreamingSession returns a State of CREATE_IN_PROGRESS, READY, STOPPED, etc. and should be polled rather than retrying the create call.

How do I start an artist session through Jentic?

Use the Jentic search query 'start a Nimble Studio session', load CreateStreamingSession, and execute it with studioId, launchProfileId, ec2InstanceType, ownedBy and a streamingImageId. Jentic signs the call with SigV4 against your stored AWS credentials and returns the sessionId so the agent can then issue a stream URL.

Is Amazon Nimble Studio free?

There is no charge for the Nimble Studio control plane itself, but the underlying compute (EC2 streaming instances), storage and any third-party software licences are billed separately. Costs are heavily driven by streaming session run time, so an agent that stops idle sessions is one of the highest-leverage automations on this API.