Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Create Prints 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%2Fcreateprints.ai%2Fcreateprints" | shStep 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%2Fcreateprints.ai%2Fcreateprints" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Create Prints API.
Queue an artwork generation job and poll it to completion
Import a standalone artwork file for printing
Search the public print catalogue and list available print sizes and frame colours
Create a human-completed checkout link for selected print products
Track checkout, fulfilment, and shipment status for an order
GET STARTED
List an account's artwork and orders
Patterns agents use Create Prints API for, with concrete tasks.
★ Chat Image to Wall Print
An assistant turns an image a user generated in chat into a physical wall print. It imports the artwork, searches the catalogue for compatible products and prices, lists the print sizes and frame colours, and creates a checkout link the user completes to place the order.
Call POST /api/image-generations/import to add the artwork, GET /api/prints to find products, then POST /api/checkout to create a checkout link
Order Tracking Through Delivery
After a checkout completes, an agent follows the order from production to the doorstep. It reads checkout, fulfilment, and shipment status for the order and lists the account's recent orders, surfacing shipment updates to the customer without manual lookups.
Call GET /api/checkout-status for the order, then GET /api/orders/list to confirm it against the account's recent orders
Artwork Generation and Printing
A creative tool queues artwork generation, polls the job until the image is ready, and prepares it for print. The agent then lists the unframed print sizes and frame options so the finished piece can be ordered in the right format.
Call POST /api/image-generations to queue the job, then GET /api/image-generations to poll it until the artwork is ready
AI Agent Integration via Jentic
An AI agent reaches the Create Prints API through Jentic without wiring its mix of apiKey, bearer, and OAuth2 credentials itself. It searches by intent, receives the matching operation and its input schema, and executes the call with the credential injected at run time, chaining artwork, catalogue, checkout, and order tracking in one flow.
Search Jentic for 'create a print checkout', load the operation schema, and execute it with Jentic-managed credentials
14 endpoints — the create prints api turns images and generated artwork into physical wall prints, posters, and framed artwork.
METHOD
PATH
DESCRIPTION
/api/image-generations
Queue an artwork generation
/api/image-generations
Get an artwork job
/api/prints
Search the public print catalogue
/api/agent-print-options
List purchasable physical print variants
/api/checkout
Create a human-completed checkout
/api/checkout-status
Get checkout, fulfilment, and shipment status
/api/orders/list
List account orders
/api/image-generations
Queue an artwork generation
/api/image-generations
Get an artwork job
/api/prints
Search the public print catalogue
/api/agent-print-options
List purchasable physical print variants
/api/checkout
Create a human-completed checkout
/api/checkout-status
Get checkout, fulfilment, and shipment status
/api/orders/list
List account orders
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Create Prints by hand means choosing among an apiKey, bearer, or OAuth2 credential per operation, polling artwork jobs, and threading checkout into order tracking yourself. Through Jentic you install once, import Create Prints from the API Directory, store the credential once, and your agent calls it.
Permission scoping
A rule can confine your agent to the operations it needs, such as browsing the catalogue and creating a checkout, because catalogue reads are public and the account actions are separate operations you choose to include. Order history and fulfilment retries stay out of reach unless you grant them.
Credential isolation
Your Create Prints credential 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 'turn an image into a print' or 'track a print order', and Jentic returns the matching Create Prints operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Create Prints API through Jentic.
What authentication does the Create Prints API use?
The Create Prints API accepts several credentials per its OpenAPI spec: an apiKey sent in the X-API-Key header, a bearer token, and an OAuth2 authorization-code flow for user sessions. Catalogue reads such as searching prints and listing print sizes are public. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at execution time.
Can I create a checkout for a print with the Create Prints API?
Yes. The checkout endpoint creates a human-completed checkout link for the selected print products, and the checkout-status endpoint reports fulfilment and shipment progress afterwards. Checkout returns structured JSON an agent can present to the buyer directly.
Can I generate artwork before printing with the Create Prints API?
Yes. Queue a generation job with the image-generations endpoint and poll the same resource until the artwork is ready, or import an existing file instead. Once an image is prepared, the catalogue, print-size, and frame endpoints show what it can be printed on.
How do I create a print checkout through Jentic with the Create Prints API?
Search Jentic for 'create a print checkout', and it returns the Create Prints checkout operation with its input schema. Load the schema and execute POST /api/checkout with the credential injected at run time. 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 Create Prints API?
Yes. Write a rule that allows only the operations the agent needs, for example browsing the catalogue and creating a checkout, while leaving out order history or retrying fulfilment unless you add them. Each call runs through your own instance and is logged for review.
For Agents
Generate or import artwork, browse print products and frames, create a checkout link, and track orders through fulfilment and delivery. Public catalogue reads need no credential; account actions use an apiKey, bearer token, or OAuth2 session.
Use for: Queue an artwork generation from a prompt, Import an existing image as artwork for printing, Search for compatible print products and prices, List the frame colours available for a print
Not supported: Does not handle apparel printing, warehousing, or payment capture beyond the hosted checkout link. Use for turning artwork into wall prints and tracking those orders only.
The Create Prints API turns images and generated artwork into physical wall prints, posters, and framed artwork. It queues artwork generation, imports standalone artwork files, searches the public print catalogue, and lists the print sizes and frame colours available for a piece. It then creates a human-completed checkout, reports fulfilment and shipment status, and lists an account's orders through to delivery.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>