canonical: https://jentic.com/apis/createprints.ai/createprints # Create Prints API 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. ## For AI 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. ## Scope 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. ## Capabilities - 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 - List an account's artwork and orders ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'create a print checkout', load the operation schema, and execute it with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/api/image-generations` | Queue an artwork generation | | GET | `/api/image-generations` | Get an artwork job | | GET | `/api/prints` | Search the public print catalogue | | GET | `/api/agent-print-options` | List purchasable physical print variants | | POST | `/api/checkout` | Create a human-completed checkout | | GET | `/api/checkout-status` | Get checkout, fulfilment, and shipment status | | GET | `/api/orders/list` | List account orders | ## Key resources - **Artwork** — Generate, import, retry, and list artwork under `/api/image-generations` - **Product discovery** — Search the catalogue and list print sizes and frame options - **Checkout** — Create a checkout and read checkout, fulfilment, and shipment status - **Orders** — List account orders under `/api/orders/list` ## AI readiness 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. - **Score:** 67 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 80 / 100 - Developer Experience & Jentic Compatibility: 67 / 100 - AI-Readiness & Agent Experience: 47 / 100 - Agent Usability: 94 / 100 - Security: 69 / 100 - AI Discoverability: 76 / 100 - **View full report:** https://jentic.com/apis/createprints.ai/createprints/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Printful** — Print-on-demand fulfilment for apparel, posters, and wall art - **Shutterstock** — Stock imagery to source artwork for printing - **Stability AI** — Image generation to create artwork for printing ## FAQ ### 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.