For sellers

Star maps,
made to order.

The Starmap API for print-on-demand and dropshipping shops: generate a personalized star map per order, at the moment it’s placed. No inventory to hold, no fulfillment stock to forecast, no renderer to build — just an API call that returns a print-ready file.

Why sellers use it instead of pre-printing stock

A star map only means something once it has a real place, date, and time behind it — which means it can’t be pre-rendered into inventory the way a generic poster can. Rendering on demand, per order, is the only version of this product that actually works for a print-on-demand or dropshipping catalog:

How it fits an on-demand order flow

  1. Your storefront collects the place, date, and time from the buyer — the customization is the product.
  2. At checkout (or fulfillment time), your system calls GET /api/starmap.svg with those values and your API key.
  3. The response is a print-ready file — hand it to your print-on-demand or dropshipping partner for that one order.
  4. Nothing is generated, stored, or paid for until the order that needs it actually exists.

The full request/response shape — parameters, formats, quota headers — is documented in the API guide and the interactive API reference.

Plans

Every Studio plan includes API access — plans differ only in the monthly render quota.

Studio — Basic$39/moper month

Enough for a shop just getting its star map line off the ground.

  • Renders100/mo
  • API accessIncluded
Open Studio

Questions sellers ask

Do I need to hold any inventory?

No. Every map is rendered on demand from the API when an order comes in — there’s nothing to pre-print or warehouse. This is what makes it a fit for print-on-demand and dropshipping: your catalog is a template, not a stock of finished posters.

Can I resell the maps I generate?

Yes — any Studio plan lets you generate and sell finished maps to your own customers. There’s no per-resale fee beyond your monthly render quota.

What format do I get back, and is it print-ready?

SVG (best for handing to a print partner or further editing) or PNG, at whatever width you request. Both come back from a single request, ready to send straight into a fulfillment pipeline.

How does it fit into an on-demand fulfillment flow?

Call the API at order time — after checkout, not before — with the buyer’s chosen place, date, and time. You get back a file to hand to your print-on-demand or dropshipping partner for that specific order, with nothing rendered until it’s actually sold.

Is there a way to test it before committing?

Studio accounts are free to create, and the visual creator gives you a live, unwatermarked-preview of exactly what the API produces before you write any integration code.