Install Jentic One Beta

Connect the OfflineCreator Studio agent commerce to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OfflineCreator Studio agent commerce, 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%2Fofflinecreatorstudio.com%2Fofflinecreatorstudio" | 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%2Fofflinecreatorstudio.com%2Fofflinecreatorstudio" | 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 OfflineCreator Studio agent commerce API.

List every launch model with its base USD price, credit cost, supported aspect ratios, and payPerGeneration flag

Lock a generation quote for a modelId, aspectRatio, and options before committing credits

Start a generation with a quoteToken and a maxCredits ceiling so an over-budget quote is refused with MAX_CREDITS_EXCEEDED

Pay for a single generation over x402 by retrying with a PAYMENT-SIGNATURE header, with no account needed

GET STARTED

Start building with OfflineCreator Studio agent commerce API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use OfflineCreator Studio agent commerce API for, with concrete tasks.

★ Budget-capped generation from an AI agent

An agent producing assets for a project needs to generate without overspending. Through Jentic it searches for 'start a priced generation', loads the OfflineCreator Studio startGeneration operation, and first calls quoteGeneration to lock the price for a modelId and aspectRatio. It then starts the generation with the quoteToken and a maxCredits ceiling, so a quote above the ceiling is refused with MAX_CREDITS_EXCEEDED before any credits are reserved.

Call POST /api/v1/generations/quote with a modelId and aspectRatio '16:9', then POST /api/v1/generations with the same modelId, a prompt, the returned quoteToken, and maxCredits 20

Model and price discovery

Before generating, a tool needs to know which models exist and what each costs. GET /api/agent/models returns every launch model with its base price in USD, credit cost, supported aspect ratios, and whether it can be bought anonymously; models that need an uploaded input are marked payPerGeneration false. Because options can change the price, the runtime 402 challenge or a locked quote stays the authoritative amount.

Call GET /api/agent/models and return the three models with the lowest credit cost that support aspect ratio '1:1' and have payPerGeneration true

Account-free pay per generation over x402

A client with a USDC wallet can generate without signing up. The first POST /api/agent/generate call returns HTTP 402 with x402 payment requirements priced from the model list; retrying with a PAYMENT-SIGNATURE header settles the payment and starts the job. The response carries a claim token, which GET /api/agent/generate/{id} accepts as an Authorization Claim header or the claim query parameter to report status and, once done, a short-lived signed output URL.

POST /api/agent/generate with a modelId and prompt, settle the returned x402 challenge, then poll GET /api/agent/generate/{id} with the claim token until it returns the signed output URL

Key Endpoints

7 endpoints — the offlinecreator studio api runs priced generations against a list of launch models and lets software pay for them per call.

METHOD

PATH

DESCRIPTION

GET

/api/agent/models

List models with prices

POST

/api/v1/generations/quote

Lock a generation quote

POST

/api/v1/generations

Start a priced generation

POST

/api/agent/generate

Pay per generation over x402

GET

/api/agent/generate/{id}

Poll and download a prepaid generation

POST

/api/v1/checkout/x402

Buy a credit pack over x402

GET

/api/agent/models

List models with prices

POST

/api/v1/generations/quote

Lock a generation quote

POST

/api/v1/generations

Start a priced generation

POST

/api/agent/generate

Pay per generation over x402

GET

/api/agent/generate/{id}

Poll and download a prepaid generation

POST

/api/v1/checkout/x402

Buy a credit pack over x402

Why Jentic?

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

Setup

Wiring OfflineCreator Studio by hand means sending a Studio bearer key, handling 402 payment challenges, locking quotes before spending, and tracking claim tokens for prepaid jobs. Through Jentic you install once, import OfflineCreator Studio from the API Directory, store the key once, and your agent calls it.

Permission scoping

OfflineCreator Studio carries the model and prompt in the request body, so rules bound which operations your agent may call, not which model it uses. You choose the operations, so spending routes like the credit pack purchase and ACP checkout are not included unless you add them.

Credential isolation

Your Studio 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 'start a priced generation' or 'list generation models', and Jentic returns the matching OfflineCreator Studio operation with its input schema, including modelId, quoteToken, and maxCredits, so the agent calls it correctly.

FAQs

Specific to using OfflineCreator Studio agent commerce API through Jentic.

What authentication does the OfflineCreator Studio API use?

Its OpenAPI spec declares HTTP bearer authentication on every operation, carrying a Studio API key or an MCP OAuth access token. Operation descriptions add that the model list and pay-per-generation routes need no account, and that prepaid outputs are fetched with a claim token sent as an Authorization Claim header or the claim query parameter. Through Jentic the Studio key is stored by your own instance and attached at call time.

Can I cap how many credits a generation spends?

Yes. POST /api/v1/generations accepts maxCredits, a spend ceiling in credits. If the locked quote is above it, the call is refused with 409 MAX_CREDITS_EXCEEDED before anything is reserved or charged. Lock the price first with POST /api/v1/generations/quote and pass the returned quoteToken.

What are the rate limits for the OfflineCreator Studio API?

The OpenAPI spec does not specify rate limits. Check the OfflineCreator Studio documentation at https://offlinecreatorstudio.com/mcp-cli for current limits.

Is there an OfflineCreator Studio MCP server?

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

How do I start a generation through Jentic?

Search Jentic for 'start a priced generation', load quoteGeneration to lock a price for your modelId, then execute startGeneration with the prompt, quoteToken, and a maxCredits ceiling. Jentic injects your Studio key on each call. To run it on your own infrastructure, install Jentic One from its GitHub repo.

How does pay per generation over x402 work?

The first POST /api/agent/generate call returns HTTP 402 with x402 payment requirements priced from the model list. Retrying with a PAYMENT-SIGNATURE header settles the payment in USDC and starts the generation, with no credit balance or signup involved. The response includes a claim token you present to GET /api/agent/generate/{id} to poll status and download the output.

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

Yes. Write a rule that allows only GET /api/agent/models, POST /api/v1/generations/quote, and POST /api/v1/generations, and the agent can price and run generations against your credits but cannot buy credit packs or open checkout sessions, and every call it makes is logged.

OfflineCreator Studio agent commerce

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLMl Inferencebearer7 EndpointsREST

For Agents

List generation models with their prices, lock a quote, start a generation under a credit ceiling, and poll or download prepaid outputs with a claim token.

Use for: List the models OfflineCreator Studio can generate with and what each costs, Get a locked quote for a generation before spending credits, I want to start a generation but never spend more than 20 credits, Check whether my prepaid generation has finished

Not supported: Does not edit uploaded images, host a media library, or manage wallets and payouts. Use for pricing, paying for, and running model generations only.

The OfflineCreator Studio API runs priced generations against a list of launch models and lets software pay for them per call. A client can lock a quote for a model, aspect ratio, and options, then start the generation against that quote with a maxCredits spend ceiling that refuses an over-budget quote before anything is charged. Without an account, a pay-per-generation route answers with an x402 payment challenge priced from the model list, settles in USDC on retry, and returns a claim token used to poll status and download the output. Credit packs can be bought over x402, and ACP checkout sessions can be created for a generation.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

46%

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: DSignals: 4

40%

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.

47%

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: B-Signals: 1

60%

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: B-Signals: 1

61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the OfflineCreator Studio agent commerce to your agent

Capabilities

Start building with OfflineCreator Studio agent commerce API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

OfflineCreator Studio agent commerce

Jentic AI Readiness Score

OfflineCreator Studio agent commerce

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