Support
Help when you need it.
Most answers are in the docs and below. When you need a person, contact us or email hello@pixeldrive.pro — we reply within a business day.
Getting started
Design a template, mark variables, render via the API.
Read the docs →API reference
Endpoints, auth, bulk render, MCP, signed URLs, errors.
API docs →Billing & credits
Plans, usage, cache-free hits, rollover, invoices.
Manage billing →API tokens
Create, name and revoke the tokens your code uses.
Manage tokens →Common questions
How do credits work?
One credit per non-cached render. Identical template + payload returns from cache for free, previews are free, and unused credits roll over.
Is this AI image generation?
No — and that is the point. PixelDrive renders your exact design deterministically. Same input, same pixels, every time. No prompts, no surprises.
Can AI agents use it?
Yes. The hosted MCP server lets Claude, Cursor and other MCP-aware clients generate on-brand images directly. See the docs for the connection config.
A render failed or looks wrong — what do I do?
Check that your payload keys match the template’s data-field ids and that image URLs are reachable. If it still fails, send us the template id and payload and we’ll dig in.
How fast is it?
Sub-second p50 on a render fleet built for volume. Cache hits return instantly.
Still stuck? We’re happy to help.
Contact us