QR code API pricing
QR Code Crafter currently focuses on free static QR code generation. The public API can generate SVG, PNG, JPG, WebP, PDF, and EPS files without an account or required redirect provider.
The API is rate limited by estimated rendering cost rather than by a paid seat plan. SVG requests are cheaper to serve than raster, PDF, large-size, or logo jobs, so integrations should honor Retry-After and rate-limit headers.
Use this page to decide whether the free static API fits your workflow, when to request an issued API key for higher-volume jobs, and when a paid dynamic QR platform is more appropriate.
Key decisions
Free static QR generation
Generate static QR files through the public endpoint without buying a subscription, creating an account, or routing scans through QR Code Crafter.
Cost-weighted rate limits
Requests consume more budget when they require heavier rendering, larger output, PDF generation, or logo processing.
Optional issued API keys
Integrations can send X-Agent-Api-Key when a credential is issued. Public access still works unless key enforcement is enabled for a deployment.
No surprise scan pricing
Static QR codes do not meter scans. Your encoded destination, analytics platform, or redirect service controls any downstream reporting cost.
Free static API vs paid dynamic QR platforms
| Need | QR Code Crafter API | Paid dynamic platform |
|---|---|---|
| Static file generation | Free public API for SVG, PNG, JPG, WebP, PDF, and EPS output. | Often included, sometimes gated behind account or plan limits. |
| Editable destinations after print | Not included. Use a redirect URL you control before generating the code. | Usually included through hosted dynamic redirects. |
| Scan analytics | Use UTM links and first-party analytics after the landing page loads. | Often includes scan counts, location, device, and campaign dashboards. |
| High-volume generation | Use agent recipes, backoff, optional keys, and batch pacing. | May include contracted quotas, SLAs, dashboards, and user management. |
| Privacy and lock-in | The QR file contains the payload directly and keeps working after download. | Dynamic codes usually depend on the provider redirect staying active. |
How API usage is limited today
The current public API is designed for useful automation without pretending to be an enterprise metered billing platform.
Rendering cost matters
SVG is the lightest path. PNG, JPG, WebP, PDF, EPS, very large sizes, and embedded logos consume more rate-limit budget.
Backoff is part of the contract
Agents and integrations should honor HTTP 429 or 503 responses, read Retry-After, and watch X-RateLimit-Limit and X-RateLimit-Remaining headers.
API keys are optional, not a paywall
If a key is issued for an integration, send it through X-Agent-Api-Key. Design clients to keep working gracefully when public access is available or when a key is required.
No scan-based charge
QR Code Crafter does not meter static QR scans. A printed static file keeps working as long as the encoded destination remains valid.
When a paid dynamic QR provider is the better fit
Static QR files are not the right answer for every commercial workflow.
You need editable destinations
Choose a dynamic QR provider or your own redirect infrastructure when printed codes must be edited after distribution.
You need scan analytics before page load
Static QR codes can carry UTM links, but they do not count scans before the destination page opens.
You need account governance
Teams that need user roles, approvals, folders, scan dashboards, or SLAs may need a paid QR platform.
You need contracted volume guarantees
For guaranteed throughput, run your own QR generation service or use a vendor with a commercial API contract.
API pricing decision checklist
- Use QR Code Crafter when you need static QR files, not hosted dynamic redirects.
- Use SVG for high-volume jobs where a vector file is acceptable.
- Pace PNG, JPG, WebP, PDF, EPS, large-size, and logo jobs because they cost more to render.
- Set a clear User-Agent and honor Retry-After on 429 or 503 responses.
- Use UTM-tagged destination URLs when you need campaign reporting in first-party analytics.
- Use a paid dynamic provider when you need editable destinations, scan analytics, team governance, or an SLA.
Estimate whether the free API fits
- 1
Classify the QR workflow
Confirm whether the job needs static files, dynamic redirects, analytics, bulk generation, or account governance.
- 2
Choose efficient formats
Prefer SVG for lightweight generation and reserve PDF, EPS, raster, and logo jobs for workflows that need those assets.
- 3
Design for rate limits
Retry with backoff, read rate-limit headers, and use optional issued keys only when they are provided for your integration.
Frequently asked questions
Is the QR Code Crafter API free?
The current public API generates static QR assets without a paid subscription. It is still rate limited, so automated clients must honor Retry-After and rate-limit headers.
Do I need an API key?
Not for normal public access. If a credential is issued for your integration, include X-Agent-Api-Key and keep clients ready for deployments where key enforcement is enabled.
Can I generate QR codes in bulk through the API?
Yes, but pace requests and prefer efficient formats. For human spreadsheet workflows, use the bulk QR generator. For guaranteed throughput, use your own service or a contracted vendor.
Does free API usage include scan analytics?
No. The API creates static QR files. Use UTM links and your analytics platform for landing-page reporting, or choose a dynamic QR platform when you need scan analytics.
When should I pay for a dynamic QR provider?
Use a paid dynamic platform when you need editable destinations after print, provider-hosted scan analytics, team governance, folders, approval workflows, or contracted support.