Install Jentic One Beta

Connect the Printify Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Printify Public 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%2Fprintify.com%2Fprintify" | 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%2Fprintify.com%2Fprintify" | 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 Printify Public API.

Browse Printify catalog blueprints, the print providers that fulfil them, and each provider's variants

Upload artwork to the Printify media library from a URL or base64 contents

Create a product from a blueprint_id, print_provider_id, variants, and print_areas, then publish it to the connected store

Calculate the shipping cost of an order from its line_items and address_to before submitting

GET STARTED

Start building with Printify Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Printify Public API for, with concrete tasks.

★ Agent-built print-on-demand products

An AI agent running a merch store can turn a design into a sellable product without a human clicking through the Printify dashboard. Through Jentic the agent searches for 'create a print-on-demand product', uploads the artwork with uploadAnImage, looks up a blueprint and print provider in the catalog, and calls createANewProduct with the variants and print_areas that place the image. It then publishes the product to the connected store.

POST /v1/uploads/images.json with file_name 'logo.png' and a url, then POST /v1/shops/{shop_id}/products.json with title, blueprint_id, print_provider_id, variants, and print_areas referencing the uploaded image id

Order routing from a custom storefront

A store built outside the native Printify integrations can still fulfil through Printify. The storefront calls calculateTheShippingCostOfAnOrder with the cart's line_items and address_to to show shipping at checkout, then submitAnOrder with the same fields and an external_id after payment. If the order is held for review, sendAnExistingOrderToProduction releases it, and getOrderDetailsById returns its current state.

POST /v1/shops/{shop_id}/orders/shipping.json with line_items and address_to, then POST /v1/shops/{shop_id}/orders.json with external_id 'web-1042', the same line_items, and address_to

Comparing print providers

Before choosing where a product is made, a merchant can compare providers for one blueprint. The catalog routes list every print provider that fulfils a blueprint, the variants each one offers, and shipping information including standard, priority, express, and economy methods, so the choice can weigh variant coverage and delivery options.

GET /v1/catalog/blueprints/{blueprint_id}/print_providers.json, then for each provider GET /v1/catalog/blueprints/{blueprint_id}/print_providers/{print_provider_id}/variants.json and summarise variant counts

Order event monitoring

Operations tooling can react to Printify order and product changes by registering a webhook per shop with a topic and url. simulateWebhook sends a test event so the receiver can be checked before live orders flow, and modifyAWebhook or deleteAWebhook adjust the subscription later.

POST /v1/shops/{shop_id}/webhooks.json with a topic and url 'https://example.com/printify', then POST /v1/shops/{shop_id}/webhooks/{webhook_id}/simulate

Key Endpoints

40 endpoints — the printify public api automates print-on-demand product and order creation for printify shops.

METHOD

PATH

DESCRIPTION

GET

/v1/catalog/blueprints.json

List catalog blueprints

GET

/v1/catalog/blueprints/{blueprint_id}/print_providers.json

List print providers for a blueprint

POST

/v1/uploads/images.json

Upload an image

POST

/v1/shops/{shop_id}/products.json

Create a new product

POST

/v1/shops/{shop_id}/products/{product_id}/publish.json

Publish a product

POST

/v1/shops/{shop_id}/orders/shipping.json

Calculate order shipping cost

POST

/v1/shops/{shop_id}/orders.json

Submit an order

GET

/v1/shops/{shop_id}/orders/{order_id}.json

Get order details

GET

/v1/catalog/blueprints.json

List catalog blueprints

GET

/v1/catalog/blueprints/{blueprint_id}/print_providers.json

List print providers for a blueprint

POST

/v1/uploads/images.json

Upload an image

POST

/v1/shops/{shop_id}/products.json

Create a new product

POST

/v1/shops/{shop_id}/products/{product_id}/publish.json

Publish a product

POST

/v1/shops/{shop_id}/orders/shipping.json

Calculate order shipping cost

POST

/v1/shops/{shop_id}/orders.json

Submit an order

GET

/v1/shops/{shop_id}/orders/{order_id}.json

Why Jentic?

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

Setup

Wiring Printify by hand means creating a personal access token, sending it as a bearer header, resolving blueprint, print provider, and variant ids before you can build a product, and handling page-based list limits that differ by resource. Through Jentic you install once, import Printify from the API Directory, store the token once, and your agent calls it.

Permission scoping

Printify puts the shop id in the URL path (/v1/shops/{shop_id}/...), so a rule can pin your agent to one shop's products, orders, and webhooks. You choose the operations it may call, so destructive or costly ones like deleteAProduct, cancelAnOrder, or disconnectAShop are not included unless you add them.

Credential isolation

Your Printify token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header 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 print-on-demand product' or 'calculate order shipping', and Jentic returns the matching Printify operation with its input schema, including required fields like blueprint_id and print_areas, so the agent calls the right endpoint directly.

FAQs

Specific to using Printify Public API through Jentic.

What authentication does the Printify Public API use?

Per its OpenAPI spec, the Printify Public API authenticates with a bearer token in the Authorization header, declared on its catalog, shop, product, order, upload, and webhook operations. You generate the personal access token in your Printify account. Through Jentic the token is held by your own instance and attached at call time.

Can I calculate shipping before submitting an order with the Printify Public API?

Yes. POST /v1/shops/{shop_id}/orders/shipping.json takes the same line_items and address_to you would submit and returns the shipping cost. The catalog also exposes per-blueprint shipping information, with separate routes for standard, priority, express, and economy methods.

What are the rate limits for the Printify Public API?

The OpenAPI spec does not specify rate limits. Check the Printify developer documentation at https://developers.printify.com for the current limits before running large catalog or product syncs.

Is there a Printify MCP server?

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

How do I submit an order through Jentic with the Printify Public API?

Search Jentic for 'submit a print-on-demand order', load the submitAnOrder operation, and execute it with the shop_id plus line_items and address_to, which the spec marks as required. Add an external_id so you can match it to your own system. 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 Printify Public API?

Yes. Write a rule that allows only the catalog reads and the products and orders reads under /v1/shops/12345/, so the agent can browse blueprints and report on that shop's orders but cannot submit, cancel, or delete anything. Every call it makes is logged for review.

Printify Public API

AI ReadinessFoundational (C)57/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceOrder Managementbearer40 EndpointsREST

For Agents

Create print-on-demand products from Printify catalog blueprints, upload artwork, and submit, price, and track orders for a Printify shop.

Use for: List all shops connected to my Printify account, Find all print providers that fulfil a specific t-shirt blueprint, I need to create a mug product with my uploaded design, Calculate shipping for an order to a UK address

Not supported: Does not take payments, host a storefront, or manage marketplace listings directly. Use for Printify print-on-demand products and order fulfilment only.

The Printify Public API automates print-on-demand product and order creation for Printify shops. It browses the catalog of blueprints, print providers, and variants, uploads artwork by URL or base64 contents, and creates products from a blueprint_id, print_provider_id, variants, and print_areas. Orders are submitted with line_items and an address_to, priced for shipping before submission, sent to production, or cancelled, and shop webhooks report order and product events. Shipping data covers standard, priority, express, and economy methods per blueprint.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C-Signals: 4

92%

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

17%

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

67%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

49%

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

19%

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.

34%

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

52%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Printify Public API to your agent

Capabilities

Start building with Printify Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Printify Public API

Jentic AI Readiness Score

Printify Public 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