Install Jentic One Beta

Connect the Pictory API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pictory API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpictory.ai%2Fpictory" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpictory.ai%2Fpictory" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Pictory API.

Preview a storyboard with its scene breakdown and visual selections before committing to a full render

Render a finished video directly from scenes built from a story, blogUrl, or pptUrl

Add AI voiceOver, backgroundMusic, subtitles, and an aspectRatio such as 9:16 for vertical video

Render an existing Pictory project by its project id

Poll a render job for progress and the output video, audio, thumbnail, and subtitle URLs

GET STARTED

Start building with Pictory API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Pictory API for, with concrete tasks.

★ Content-repurposing agent through Jentic

An AI agent publishing a weekly article can also produce a matching social video. Through Jentic the agent searches for 'create a video from a blog post', loads the Pictory storyboard render operation with its input schema, and submits a videoName with one scene whose blogUrl points at the article, an aspectRatio of 9:16, and voiceOver enabled. It then polls the job until the video URL is ready, with the Pictory key injected at call time by your own Jentic One instance.

Call POST /pictoryapis/v2/video/storyboard/render with videoName 'Weekly recap', aspectRatio '9:16', and a scene whose blogUrl is the article URL, then poll GET /pictoryapis/v1/jobs/{jobid} until the output URLs are returned

Preview before you pay for a render

The spec positions the preview as the way to validate content before incurring full rendering cost. The storyboard preview operation accepts the same body as a render and returns a jobId for reviewing scene breakdown and visual selections. Setting saveProject to true keeps the result as a Pictory project that can be rendered later by its project id.

Call POST /pictoryapis/v2/video/storyboard with videoName, saveProject true, and scenes from a script, review the preview, then call POST /pictoryapis/v2/projects/{projectid}/render for the saved project

On-brand training and explainer videos

Teams producing many explainer videos want consistent branding. The video brands operation lists each brand's UUID id and name, and a storyboard can apply a brandId or brandName along with a subtitle style, a logo, and background music. Scenes can be built from a slide deck through pptUrl, using speaker notes for narration.

Call GET /pictoryapis/v1/brands/video, then POST /pictoryapis/v2/video/storyboard/render with the chosen brandId, videoName 'Onboarding module 1', and a scene with pptUrl and useSpeakerNotes true

Key Endpoints

5 endpoints — the pictory api turns text, blog posts, slide decks, and existing audio or video into ai-generated videos.

METHOD

PATH

DESCRIPTION

POST

/pictoryapis/v2/video/storyboard

Create a storyboard preview

POST

/pictoryapis/v2/video/storyboard/render

Render a video from a storyboard

POST

/pictoryapis/v2/projects/{projectid}/render

Render a saved project

GET

/pictoryapis/v1/jobs/{jobid}

Get a render job's status and outputs

GET

/pictoryapis/v1/brands/video

List video brands

POST

/pictoryapis/v2/video/storyboard

Create a storyboard preview

POST

/pictoryapis/v2/video/storyboard/render

Render a video from a storyboard

POST

/pictoryapis/v2/projects/{projectid}/render

Render a saved project

GET

/pictoryapis/v1/jobs/{jobid}

Get a render job's status and outputs

GET

/pictoryapis/v1/brands/video

List video brands

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Pictory by hand means getting a pictai_ key, sending it as the raw Authorization header without a Bearer prefix, building its scene-based storyboard body, and polling render jobs until they finish. Through Jentic you install once, import Pictory from the API Directory, store the key once, and your agent calls it.

Permission scoping

Pictory puts the project id and job id in the URL path (/pictoryapis/v2/projects/{projectid}/render), so a rule can pin your agent to one saved project. You choose the operations it may call, so cost-incurring renders are not included unless you add them.

Credential isolation

Your Pictory API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a video from a blog post' or 'check a render job', and Jentic returns the matching Pictory operation with its input schema, including the scene fields, so the agent builds a valid storyboard without browsing the reference docs.

FAQs

Specific to using Pictory API through Jentic.

What authentication does the Pictory API use?

The Pictory API authenticates with an API key (ApiKeyAuth) per its OpenAPI spec, passed as the raw value of the Authorization header with no Bearer prefix. Keys start with pictai_ and are issued from the API access page in the Pictory app. Through Jentic the key is stored by your own instance and attached at call time.

Can I preview a Pictory video before rendering it?

Yes. POST /pictoryapis/v2/video/storyboard creates a storyboard preview so you can review scene breakdown and visual selections before committing to the full render. It accepts the same body as the direct render and returns a jobId to poll.

What are the rate limits for the Pictory API?

The OpenAPI spec does not specify rate limits. It recommends polling a render job every 10-30 seconds, or setting the webhook field on the render request to receive a push when the job finishes. Check https://docs.pictory.ai for current account limits.

Is there a Pictory MCP server?

You don't need an MCP server to give your agent Pictory. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the storyboard, render, and job operations on demand without loading another server's tool definitions into its context.

How do I render a video through Jentic?

Search Jentic for 'create a video from text', load the POST /pictoryapis/v2/video/storyboard/render operation, and execute it with a videoName and scenes, each with a story or blogUrl. Poll GET /pictoryapis/v1/jobs/{jobid} with the returned jobId for the video URL. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Pictory API?

Yes. Write a rule that allows only the storyboard preview and job status operations, and the agent can draft and check previews while the full render and project render operations stay with you. Every call it makes is logged for review.

Pictory API

AI ReadinessAI-Aware (B+)69/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaVideo ProcessingapiKey5 EndpointsREST

For Agents

Generate AI videos with Pictory from text, a blog URL, or slides: preview a storyboard, render the video, render a saved project, poll the job for output URLs, and apply a video brand.

Use for: Turn this blog post into a short vertical video, Create a video from a script with an AI voice-over, Preview the storyboard before rendering the final video, Check whether my render job has finished

Not supported: Does not host or stream finished videos to viewers, edit timelines frame by frame, or publish to social networks. Use for generating and rendering AI videos from text, links, and slides only.

The Pictory API turns text, blog posts, slide decks, and existing audio or video into AI-generated videos. A storyboard request takes a videoName and an array of scenes, each built from a story, a blogUrl, a pptUrl, or media with a transcript, plus optional voiceOver, backgroundMusic, subtitles, a brand, and an aspect ratio of 1:1, 16:9, 9:16, or 4:5. You can preview the storyboard before paying for a full render, render it directly, or render a saved Pictory project, then poll the render job for the video, audio, thumbnail, and subtitle file URLs.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

48%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

95%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Pictory API to your agent

Capabilities

Start building with Pictory API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Pictory API

Jentic AI Readiness Score

Pictory API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness