[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Printful API and MCP server > Printful has a full REST API, documented at developers.printful.com, with private tokens for your own store and OAuth for public apps, but no official MCP server (checked 17 Oct 2026). The API docs never mention MCP. The API covers orders, shipping rates, files, mockups, sync products and webhooks, so the gap is a hosted, maintained MCP server with no token or OAuth app to run. Print-on-demand service: you upload a design, pick a product, and Printful prints and ships it to your customer. Orders arrive from a connected store or are created by hand in the dashboard. ## What is the Printful API? Cotlet's Printful API exposes 10 endpoints for your own Printful account: list orders, get order, list sync products, list product templates, get shipping rates, create draft order, upload design file, generate mockups, confirm order and cancel order. The list_orders endpoint returns orders of your store, newest first, filtered by status. Each endpoint takes simple JSON inputs like order_id, items or status and works both as an operation of the printful_read or printful_write MCP tool for agents and as a REST call for scripts. - **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities.md) - **Endpoints:** 10 (5 read, 5 write) - **Updated:** 2026-10-18 Printful has a full REST API, documented at developers.printful.com, with private tokens for your own store and OAuth for public apps, but no official MCP server (checked 17 Oct 2026). Cotlet is a hosted MCP server and REST API for Printful with 10 endpoints (5 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work. ## Does Printful have an official API? Printful has a full REST API, documented at developers.printful.com, with private tokens for your own store and OAuth for public apps, but no official MCP server (checked 17 Oct 2026). The API docs never mention MCP. The API covers orders, shipping rates, files, mockups, sync products and webhooks, so the gap is a hosted, maintained MCP server with no token or OAuth app to run. | Task | Printful official | Cotlet | |---|---|---| | List orders and read one with its shipments | Yes: API: GET /orders and GET /orders/{id}; the order object has tracking numbers | Yes | | Create a draft order | Yes: API: POST /orders; you are only charged for confirmed orders | Yes | | Confirm an order for fulfillment | Yes: API: POST /orders/{id}/confirm, which charges your card | Yes | | Cancel an order or delete a draft | Yes: API: DELETE /orders/{id} | Yes | | Check shipping rates | Yes: API: POST /shipping/rates, 120 calls per 60 seconds, 5 if the quantity is over 100 | Yes | | List sync products of a store | Yes: API: GET /store/products | Yes | | Upload a design file | Yes: API: POST /files from a URL, processed asynchronously | Yes | | Generate product mockups | Partly: API: Mockup Generator, 10 requests per 60 seconds for established stores and 2 for new ones | Yes | Sources: [Printful API documentation](https://developers.printful.com/docs/), [Printful Help: How can I check the status of an order?](https://help.printful.com/hc/en-us/articles/360014007400-How-can-I-check-the-status-of-an-order), [Printful Help: Can I change or cancel an order that is already submitted?](https://help.printful.com/hc/en-us/articles/360014007060-Can-I-change-or-cancel-an-order-that-is-already-submitted), [Printful Help: What are mockup images?](https://help.printful.com/hc/en-us/articles/360014066179-What-are-mockup-images) ## For AI agents ```text Printful has a full REST API, documented at developers.printful.com, with private tokens for your own store and OAuth for public apps, but no official MCP server (checked 17 Oct 2026). The API docs never mention MCP. The API covers orders, shipping rates, files, mockups, sync products and webhooks, so the gap is a hosted, maintained MCP server with no token or OAuth app to run. Cotlet provides a hosted MCP server and REST API for Printful: 10 tools (5 read, 5 write). Access Sign up at https://cotlet.dev/app/signup?app=printful, then request the app and create API keys in the Cotlet console. MCP server https://cotlet.dev/mcp/v1 MCP tools printful_read, printful_write, reads and writes apart; call one with {"operation": "", "arguments": {...}} REST base https://cotlet.dev/api/v1/printful, each operation at its own route, e.g. POST /api/v1/printful/draft-orders Auth Authorization: Bearer . Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in. Operations list_orders, get_order, list_sync_products, list_product_templates, get_shipping_rates, create_draft_order, upload_design_file, generate_mockups, confirm_order, cancel_order Confirm upload_design_file, confirm_order, cancel_order (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations) Markdown https://cotlet.dev/integrations/printful-api-mcp-server.md How access works: 1. The user signs up at https://cotlet.dev/app/signup?app=printful, requests Printful in the Cotlet console and creates an API key there. 2. The user signs in to Printful once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Printful for agents. An agent cannot do this step. 3. The API key goes into the MCP client or the REST call as a bearer token. Fits: people who want a hosted Printful server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Printful MCP server instead. Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA. Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev. Sign-in: the user signs in to Printful in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Printful only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273). API key: holds no Printful login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once. Terms: the user stays responsible for following Printful's terms; Cotlet is not affiliated with Printful. ``` ## What can an AI agent do in Printful? Cotlet is best for store owners and small print-on-demand teams who want an AI agent to check orders, shipping and mockups in Printful without running or fixing a server, or renewing API tokens. - **[Find failed and stuck orders](https://cotlet.dev/integrations/printful-api-mcp-server/find-failed-and-stuck-orders.md)** (runs: daily): "List my Printful orders that failed or are still drafts. For each, tell me why it did not go through and whether I can confirm it now. Do not confirm anything." → `list_orders`, `get_order` - **[Confirm draft orders after a shipping check](https://cotlet.dev/integrations/printful-api-mcp-server/confirm-draft-orders-after-shipping-check.md)** (runs: daily): "Look at my Printful draft orders. For each, check the shipping rate to the recipient and show me the cheapest option and the delivery window. Confirm only the ones I approve." → `list_orders`, `get_order`, `get_shipping_rates`, `confirm_order` - **[Generate mockups for new designs](https://cotlet.dev/integrations/printful-api-mcp-server/generate-mockups-for-new-designs.md)**: "Take my product template "Autumn tote" and generate mockups in all available styles. Give me the download links." → `list_product_templates`, `generate_mockups` - **Create orders from a list**: "Here are 12 recipients and the sync product each one bought. Create a draft order for each, check shipping, and show me the total before anything is confirmed." → `list_sync_products`, `create_draft_order`, `get_shipping_rates` - **Cancel orders before fulfillment**: "Cancel Printful order 31840 and tell me where the refund goes. If it is already being fulfilled, tell me and do nothing." → `get_order`, `cancel_order` - **Check tracking for shipped orders** (runs: weekly): "List my Printful orders from the last 14 days that are fulfilled and give me the carrier and tracking number for each, so I can answer customer emails." → `list_orders`, `get_order` ## Can Printful automations run on a schedule in n8n, Make or Zapier? Yes. Cotlet does not replace your automation platform: it gives it a Printful connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to find failed and stuck orders, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off. | Where | How to connect | How to schedule | |---|---|---| | Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. | | n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/printful/orders. | Schedule Trigger node. | | Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. | | Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. | | Your own script | GET https://cotlet.dev/api/v1/printful/orders with your API key. | cron or GitHub Actions. | ## Tools **For AI agents:** Every endpoint and its schema is public. The 10 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Printful. ### list_orders Orders of your store, newest first, filtered by status. Access: read. REST: `GET /api/v1/printful/orders`. MCP: `printful_read → list_orders`. | Parameter | Type | Required | Description | |---|---|---|---| | `status` | enum | no | draft, failed, waiting_for_fulfillment, being_fulfilled, partially_fulfilled, fulfilled or canceled. Default: all. | | `limit` | integer | no | Orders per page. Default 20. | | `cursor` | string | no | Next page cursor from the previous call. | Returns one page of orders with ID, status, recipient name, item count and creation date. Without a status it returns every order. Use cursor to read on. The status follows the dashboard labels, for example Draft, Failed or Fulfilled. Example response: ```json { "orders": [ { "order_id": 31911, "status": "draft", "recipient": "Anna Berg", "items": 2, "created_at": "2026-10-17T07:12:00Z" }, { "order_id": 31877, "status": "failed", "recipient": "Mia Alvarez", "items": 2, "created_at": "2026-10-16T22:40:00Z" } ], "next_cursor": null } ``` ### get_order One order with recipient, items, costs and shipments. Access: read. REST: `GET /api/v1/printful/orders/{order_id}`. MCP: `printful_read → get_order`. | Parameter | Type | Required | Description | |---|---|---|---| | `order_id` | integer | yes | Order ID from list_orders. | Returns the status, the recipient address, each item with its quantity, the costs Printful shows, and the shipments with carrier and tracking number once the order has shipped. A draft has no shipments yet. Example response: ```json { "order_id": 31840, "status": "fulfilled", "recipient": { "name": "Tom Reed", "country": "US", "state": "OR" }, "items": [ { "name": "Autumn tote", "quantity": 1 } ], "costs": { "currency": "USD", "total": "18.40" }, "shipments": [ { "carrier": "USPS", "tracking_number": "9400111899223344556677", "shipped_at": "2026-10-12" } ] } ``` ### list_sync_products Products synced to your store, with their variants. Access: read. REST: `GET /api/v1/printful/sync-products`. MCP: `printful_read → list_sync_products`. | Parameter | Type | Required | Description | |---|---|---|---| | `query` | string | no | Only products whose name contains this text. | Returns the products in your store with ID, name and variant count. Use the variant ID with create_draft_order. Products that are not synced to a store do not appear. Example response: ```json { "products": [ { "product_id": 410220, "name": "Autumn tote", "variants": [ { "variant_id": 5120881, "name": "Autumn tote, natural" } ] } ] } ``` ### list_product_templates Your saved product templates. Access: read. REST: `GET /api/v1/printful/product-templates`. MCP: `printful_read → list_product_templates`. No parameters. Returns the templates from Product templates with ID and name. Use template_id with generate_mockups. Example response: ```json { "templates": [ { "template_id": 7723, "name": "Autumn tote" }, { "template_id": 7701, "name": "Pine mug" } ] } ``` ### get_shipping_rates Shipping options and delivery windows for a recipient and items. Access: read. REST: `GET /api/v1/printful/countries/{country_code}/shipping-rates`. MCP: `printful_read → get_shipping_rates`. | Parameter | Type | Required | Description | |---|---|---|---| | `country_code` | string | yes | Two-letter country code, for example DE. | | `state_code` | string | no | Required for US, AU and CA. | | `items` | object[] | yes | Items as variant_id and quantity. | Returns every rate with name, price, currency and the delivery window in days. Country is always required, and state is required for US, Australia and Canada. Call it right before placing an order. The rates can differ from the cost estimate unless shipping settings are enabled for the store. Example response: ```json { "rates": [ { "name": "Standard", "rate": "5.95", "currency": "EUR", "min_delivery_days": 3, "max_delivery_days": 6 }, { "name": "Express", "rate": "14.50", "currency": "EUR", "min_delivery_days": 1, "max_delivery_days": 3 } ] } ``` ### create_draft_order Create an order as a draft. Nothing is charged or sent to print. Access: write. REST: `POST /api/v1/printful/draft-orders`. MCP: `printful_write → create_draft_order`. | Parameter | Type | Required | Description | |---|---|---|---| | `recipient` | object | yes | name, address1, city, country_code, zip, and state_code where required. | | `items` | object[] | yes | Items as sync variant_id and quantity. | | `shipping` | string | no | Shipping option name from get_shipping_rates. Default: Standard. | Creates the order with the recipient and items and leaves it as a draft. Printful charges only confirmed orders, and you can edit or delete a draft in the Dashboard, or with cancel_order. It reaches no one and costs nothing, so it does not ask for confirmation. Example response: ```json { "order_id": 31920, "status": "draft", "recipient": "Anna Berg", "items": 1, "created_at": "2026-10-17T09:20:00Z" } ``` ### upload_design_file Add a design file to your file library from a URL. Access: write, asks the user first. REST: `POST /api/v1/printful/design-files`. MCP: `printful_write → upload_design_file`. | Parameter | Type | Required | Description | |---|---|---|---| | `url` | string | yes | Public URL of the design file, PNG or JPEG. | | `filename` | string | no | Name to show in the library. | Adds the file to your Printful file library, which Printful then processes. The URL must be public. Use the file ID in a product or order. The file stays in the library until you remove it there. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "file_id": 88120344, "filename": "autumn-tote.png", "status": "waiting" } ``` ### generate_mockups Generate product mockups for a template and return download links. Access: write. REST: `POST /api/v1/printful/templates/{template_id}/mockups/generate`. MCP: `printful_write → generate_mockups`. | Parameter | Type | Required | Description | |---|---|---|---| | `template_id` | integer | yes | Template ID from list_product_templates. | | `styles` | string[] | no | Mockup styles to generate. Default: every style Printful offers for the product. | Generates the mockups for one template in the styles you ask for, waits until they are ready, and returns one link per image. Printful limits how often mockups can be generated, so a long list of templates runs one at a time. It writes only to the mockup page, reaches no one and changes no order, so it does not ask for confirmation. Example response: ```json { "template_id": 7723, "mockups": [ { "style": "front_flat", "url": "https://files.example.com/mockups/7723-front-flat.png" }, { "style": "lifestyle", "url": "https://files.example.com/mockups/7723-lifestyle.png" } ] } ``` ### confirm_order Submit a draft order for fulfillment. Access: write, asks the user first. REST: `POST /api/v1/printful/orders/{order_id}/confirm`. MCP: `printful_write → confirm_order`. | Parameter | Type | Required | Description | |---|---|---|---| | `order_id` | integer | yes | Order ID from list_orders. | Submits the draft for fulfillment and charges your card, which makes it real money and a real shipment. Printful starts work on it, and once it is Being Fulfilled it cannot be edited or canceled in the Dashboard. A payment that fails leaves the order as Failed. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "order_id": 31911, "status": "waiting_for_fulfillment", "total": "27.45", "currency": "EUR" } ``` ### cancel_order Cancel a submitted order or delete a draft. Access: write, asks the user first. REST: `POST /api/v1/printful/orders/{order_id}/cancel`. MCP: `printful_write → cancel_order`. | Parameter | Type | Required | Description | |---|---|---|---| | `order_id` | integer | yes | Order ID from list_orders. | Deletes a draft, or cancels an order that is Waiting for Fulfillment, with a full refund. Once the order is Being Fulfilled, Printful does not allow cancelling it and the call returns that status without changing anything. Cancelling in Printful does not cancel the order in your sales channel. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "order_id": 31840, "status": "canceled" } ``` ## How do I connect Printful to Claude Code, Codex or Cursor? Connecting Printful takes three steps: sign up, sign in to Printful once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key. ### Connect Printful to your agent. 1. **Create an account** Sign up and add Printful in the console. Your API key is there too. 2. **Sign in to Printful in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Printful there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off. 3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once. Claude Code: ``` claude mcp add --transport http cotlet \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` Cursor: ``` { "mcpServers": { "cotlet": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` 4. **Ask your agent** Ask in plain words. Your agent finds the Printful tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool. ``` List my Printful orders that failed or are still drafts. For each, tell me why it did not go through and whether I can confirm it now. Do not confirm anything. ``` ### Call Printful from your scripts. 1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code. ``` export COTLET_API_KEY="cotlet_..." ``` 2. **Call a tool** Every tool is an endpoint under /api/v1/printful with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise. ``` curl -X POST https://cotlet.dev/api/v1/printful/draft-orders \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"recipient":{"name":"Anna Berg","address1":"Lindenallee 4","city":"Hamburg","country_code":"DE","zip":"20095"},"items":[{"variant_id":5120881,"quantity":1}],"shipping":"Standard"}' ``` 3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing. ``` { "order_id": 31920, "status": "draft", "recipient": "Anna Berg", "items": 1, "created_at": "2026-10-17T09:20:00Z" } ``` ## Why use Cotlet for Printful? **Built for agents** - One MCP server for every app you connect. - The same tools as a REST API for scripts and cron jobs. - Works with Claude Code, Codex and Cursor. **Your login stays yours** - You sign in to Printful yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses. - A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory. - The model never sees a login. - No stored passwords, no CAPTCHA solving, no MFA bypass. **You stay in control** - Scope each API key: its apps, its tools, read only or read and write. - Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you. - Every background request listed in your Background activity. Disable for agents in one click. **Kept working for you** - We test every integration every 6 hours. - When Printful changes, the tool pauses until we fix it. - Failed calls cost nothing. ## Is it safe to connect Printful to Cotlet? Yes. You sign in to Printful yourself, in your own Cloud Browser, and we never save your password. Your agents only get Printful once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself. - **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev) - **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on) - **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev) - **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev) [How Cotlet protects your access](https://cotlet.dev/security.md) ### Common concerns **Who runs Cotlet?** Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet. **Is this an official Printful integration?** No, Cotlet is independent of Printful. Printful's own API is too limited for this work. Cotlet works through your own Printful account, the way you use Printful in the browser, so you need no partner approval and no developer setup. **What about client data and GDPR?** Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it. **Can I start with read only?** Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool. **Is it reliable?** Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev. **How do I stop?** Press Disable for agents next to Printful in your console: your agents lose access at once and you stay signed in. Signing out of Printful in the browser works too, and Reset browser deletes the whole profile. ## Is there a Printful MCP server on GitHub? Yes. Community Printful MCP servers exist on GitHub, usually maintained by one person. You install one yourself, give it a Printful API token, and fix it when Printful changes. Cotlet hosts the same kind of server for you, signs in as you, and our team keeps it working. | | GitHub MCP server | Cotlet | |---|---|---| | Setup | Clone the repo, create a private token in Printful, store it, add the server to each MCP client | Sign up, sign in to Printful once, add one MCP server or API key | | When Printful changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free | | Your Printful access | A token in a file on your computer, readable by any program you run | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click | | When access expires | Tools fail until you replace the token by hand, Printful does not refresh private tokens | Your Cloud Browser keeps you signed in; if Printful logs you out, your agent gets a link to sign in again | | Upkeep | You update, monitor and debug it yourself | Nothing to host or update | | Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule | | Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription | ### Which one fits you **Pick Cotlet if** - you are not a developer, or you do not want to maintain a server - you need it to keep working when Printful changes, without checking it yourself - your agent or a script should run it on a schedule, also while your computer is off **Pick an open-source server if** - you are comfortable installing, updating and fixing it yourself - you want your sign-in to stay on your own computer - you only need it now and then, from one MCP client ## How much does the Printful API cost? Free 7-day trial with 2,000 credits, no card needed. After that, the Printful API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over. | Credits | Price, one time | Calls at 25 credits | Per 1,000 credits | |---|---|---|---| | 5,000 | $29 | 200 | $5.80 | | 15,000 | $79 | 600 | $5.27 | | 32,000 | $149 | 1,280 | $4.66 | | 60,000 | $249 | 2,400 | $4.15 | Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md) ## How Cotlet holds your access Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Printful account. - **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms) - **Your sign-in:** You sign in to Printful yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Printful only after you enable it. When Printful signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md) - **Revoking access:** Press Disable for agents next to Printful, sign out of Printful in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool. - **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA. - **Printful's terms:** You use your own Printful account and stay responsible for following Printful's terms. Cotlet is independent and not affiliated with Printful. [Terms](https://cotlet.dev/terms) - **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev) ## Frequently asked questions **How do I get access?** Sign up free, open Printful in the console and press Request access. Then you create your API key and connect Printful there. **Do I need to be technical?** No. You sign in to Printful once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix. **Is it safe to connect Printful to Cotlet?** Yes. You sign in to Printful yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Printful once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security. **Is a hosted server safer than a local one? My Printful sign-in would leave my computer.** On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Printful cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off. **Why does Cotlet send requests instead of clicking in my browser?** To be fast, Cotlet doesn't click through Printful's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Printful sees the same browser and IP you signed in with, and every request is listed in your Background activity. **What if someone gets my Cotlet API key?** The key holds no Printful login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once. **Why a signed-in browser and not OAuth, like other integration platforms?** Printful offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273). **Do I need an API token for Cotlet?** No. Cotlet works through your own Printful login, so you create no private token and no OAuth app. Printful private tokens expire and cannot be refreshed, they must be replaced manually (Printful API documentation, checked 17 Oct 2026). **Can my agent spend money without asking?** Only if you switch confirmation off. By default confirm_order and cancel_order wait for your OK. Printful charges your card when an order is submitted for fulfillment, and an order that is Being Fulfilled can no longer be canceled (Printful Help: Can I change or cancel an order that is already submitted). **Can my agent post or send messages in Printful without asking me?** No. Every call to upload_design_file, confirm_order or cancel_order waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_draft_order, generate_mockups runs without asking, because it sends nothing to anyone and one call undoes it. **Can I use the Printful API in n8n?** Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/printful from the HTTP Request node. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners. ## For AI agents: sign your user up Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed. 1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests 2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them. 3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests. One call creates the account and sends the access request; we email the user when access is granted.