Install Jentic One Beta

Connect the PostNitro Embed API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PostNitro Embed 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%2Fpostnitro.ai%2Fpostnitro" | 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%2Fpostnitro.ai%2Fpostnitro" | 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 PostNitro Embed API.

Generate a carousel, image, or video post with AI from a text topic, an article URL, or an X post URL

Import your own slide content into a PostNitro template as a starting_slide, body slides, and an ending_slide

Render output as PNG slides, a single PDF, an MP4 video, or a saved DESIGN via responseType

Poll a post's status by embedPostId and read its processing logs when a step fails

GET STARTED

Start building with PostNitro Embed API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use PostNitro Embed API for, with concrete tasks.

★ Agent-made carousels through Jentic

A developer asks their agent to turn each new blog post into a branded carousel. Through Jentic the agent finds the PostNitro generate operation by intent, sends the article URL with the templateId, brandId, and presetId from the dashboard, polls status until COMPLETED, and returns the PDF link. The embed-api-key header is attached by your own instance, so the agent never sees the key.

Call POST /post/initiate/generate with postType CAROUSEL, responseType PDF, aiGeneration type article and context set to the article URL, then poll GET /post/status/{embedPostId} until COMPLETED and fetch GET /post/output/{embedPostId}

Rendering your own copy into a template

When the words are already written, the import operation places them into a design without AI rewriting. CAROUSEL and VIDEO posts take an ordered slides array with exactly one starting_slide, one or more body_slide entries, and exactly one ending_slide, while IMAGE takes a single slide object. PNG output returns one image URL per slide.

Call POST /post/initiate/import with postType CAROUSEL, responseType PNG, a templateId and brandId, and a slides array of a starting_slide, three body_slide entries, and an ending_slide

Short video posts with a soundtrack

For reels-style content, postType VIDEO turns each slide into a scene and renders an MP4. GET /audio lists the workspace's audio files newest first, and an entry's id goes into videoSettings.audioId to set the soundtrack. Audio is uploaded in the PostNitro app; the API only lists and deletes it.

Call GET /audio to pick an audio id, then POST /post/initiate/generate with postType VIDEO, responseType MP4, and videoSettings.audioId set to that id

Debugging failed renders

Asynchronous generation can fail at a specific step, such as AI image generation hitting a plan quota. The status operation returns PENDING, COMPLETED, or FAILED along with a logs array, so a pipeline can report the failing step instead of retrying blindly.

Poll GET /post/status/{embedPostId} and, if status is FAILED, return the step names from the logs array

Key Endpoints

6 endpoints — the postnitro embed api generates social media carousels, single image posts, and short videos from a postnitro design template, brand configuration, and ai preset.

METHOD

PATH

DESCRIPTION

POST

/post/initiate/generate

Initiate AI carousel generation

POST

/post/initiate/import

Create a post from your own slides

GET

/post/status/{embedPostId}

Check generation status

GET

/post/output/{embedPostId}

Retrieve generated files

GET

/audio

List workspace audio files

DELETE

/audio/{id}

Delete an audio file

POST

/post/initiate/generate

Initiate AI carousel generation

POST

/post/initiate/import

Create a post from your own slides

GET

/post/status/{embedPostId}

Check generation status

GET

/post/output/{embedPostId}

Retrieve generated files

GET

/audio

List workspace audio files

DELETE

/audio/{id}

Delete an audio file

Why Jentic?

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

Setup

Wiring PostNitro by hand means sending the embed-api-key header, looking up templateId, brandId, and presetId values, matching the slides shape to each postType, and writing the initiate, poll, and fetch loop. Through Jentic you install once, import PostNitro from the API Directory, store the key once, and your agent calls it.

Permission scoping

PostNitro carries the template, brand, and content in the request body, so rules bound which operations your agent may call rather than which template. You choose the operations it may call, so the permanent audio deletion at DELETE /audio/{id} is not included unless you add it.

Credential isolation

Your PostNitro 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 'generate a carousel' or 'check carousel render status', and Jentic returns the matching PostNitro operation with its input schema, including the postType and responseType enums, so the agent sends a valid request.

FAQs

Specific to using PostNitro Embed API through Jentic.

What authentication does the PostNitro Embed API use?

The PostNitro Embed API authenticates with an API key sent in the embed-api-key request header, per its OpenAPI spec. You generate the key from your PostNitro dashboard. Through Jentic the key is stored by your own instance and attached at call time, so the agent never handles it.

Is there a PostNitro MCP server?

Yes. PostNitro documents an MCP server at https://mcp.postnitro.ai/mcp. You can also connect the PostNitro Embed API directly through Jentic: your agent gets the full 6-endpoint surface from the spec without loading another server's tool definitions into its context, your key is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.

How does PostNitro generation work?

Generation is asynchronous. POST /post/initiate/generate or POST /post/initiate/import returns an embedPostId; poll GET /post/status/{embedPostId} until status is COMPLETED, then call GET /post/output/{embedPostId}. For PNG the result is one image URL per slide, for PDF a single document URL, and for MP4 a single video URL.

What are the rate limits for the PostNitro Embed API?

The OpenAPI spec does not specify rate limits. Usage is metered in post credits, with AI images billed against a separate quota; check https://postnitro.ai/docs/embed/api for current plan limits.

Can I limit what my agent is allowed to do with PostNitro?

Yes. For example, allow only POST /post/initiate/generate, GET /post/status/{embedPostId}, and GET /post/output/{embedPostId}, and the agent can create posts and collect their files but cannot delete audio from your workspace. Every call it makes is logged, so you can see how many posts a task spent.

How do I generate a carousel from an article through Jentic?

Search Jentic for 'generate a carousel from an article', load POST /post/initiate/generate, and send postType CAROUSEL, your templateId, brandId, and presetId, and aiGeneration with type article and the URL as context. To run it on your own infrastructure, install Jentic One from its GitHub repo.

PostNitro Embed API

AI ReadinessAI-Aware (B)63/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaImage ProcessingapiKey6 EndpointsREST

For Agents

Generate AI or imported social media carousels, image posts, and videos from PostNitro templates, poll until rendering completes, and fetch the PNG, PDF, or MP4 output URLs.

Use for: Generate a LinkedIn carousel from this blog article URL, I need to turn a topic prompt into a PDF carousel, Create a carousel from my own slide text using my brand template, Check whether my carousel has finished rendering

Not supported: Does not publish or schedule posts to social networks, host media, or edit uploaded audio. Use for generating and rendering carousel, image, and video post files only.

The PostNitro Embed API generates social media carousels, single image posts, and short videos from a PostNitro design template, brand configuration, and AI preset. A post can be written by AI from a text prompt, an article URL, or an X post URL, or imported from your own slide content, and rendered as PNG slides, a PDF document, an MP4 video, or a saved design. Generation is asynchronous: an initiate call returns an embedPostId, the status operation reports PENDING, COMPLETED, or FAILED with processing logs, and the output operation returns the file URLs. Workspace audio files used as video soundtracks can be listed and deleted.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

94%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

60%

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: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

29%

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

59%

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.

46%

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).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PostNitro Embed API to your agent

Capabilities

Start building with PostNitro Embed API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

PostNitro Embed API

Jentic AI Readiness Score

PostNitro Embed 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