The AI image API for developers and agents.
Standard REST, Bearer auth, an OpenAPI spec and a native MCP server. One call to /v1/images, and any HTTP client or AI agent is generating images in minutes.
The best AI image generation API for developers and AI agents is the one you can wire up without reading a manual. PixelFireman is a plain REST endpoint with Bearer token auth: send a JSON prompt to /v1/images, get an image URL back. It ships an OpenAPI spec for codegen and a pixelfireman-mcp server so coding agents call image generation as a native tool, with no HTTP glue to write. Per-key usage metering, clear rate limits and prepaid credits that never expire make it predictable to run in production.
The whole integration
Send a prompt, read the URL, move on. This is the entire thing.
# prompt to image, one request curl https://pixelfireman.com/v1/images \ -H "Authorization: Bearer pixelfireman_com_live_…" \ -H "content-type: application/json" \ -d '{"prompt":"isometric dashboard illustration, soft shadows","engine":"generate"}' # to { "image":"https://…", "engine":"generate", "creditsUsed":1 }
More details
Built the way developers expect
No SDK lock-in, no bespoke signing scheme, no surprise request format. If your stack can send an HTTP request with an Authorization header, it already works.
A native MCP server for AI agents
Agents should not have to hand-write HTTP calls to make a picture. The pixelfireman-mcp server exposes image generation over the Model Context Protocol, so agents running in Claude, Cursor or any MCP client see a ready tool they can call directly.
- Same API key, same per-key usage meter as the REST endpoint.
- Both engines available: vector draw and raster generate.
- An agent describes the image it wants, gets a URL back, and keeps working.
This is what turns PixelFireman into a first-class image generation API for AI agents rather than a service they have to be taught to speak to.
Two engines, picked per request
PixelFireman gives you two generation paths behind the same endpoint, and you choose which one to run on every call:
- draw returns clean vector SVG for logos, icons, diagrams and UI marks, for one credit.
- generate returns a raster AI image for photos, scenes and illustration, at one credit each.
Use draw when you need something crisp and resolution-independent, and generate when you need a real picture. Both are reachable from REST and from the MCP server.
# need a logo or icon instead? use the vector engine, 1 credit curl https://pixelfireman.com/v1/images \ -H "Authorization: Bearer pixelfireman_com_live_…" \ -d '{"prompt":"minimal flame logo","engine":"draw"}'
Agents reach the same capability through pixelfireman-mcp, so the choice between REST and MCP is yours, not a rewrite.
What a call returns
The same one-line request, four different prompts. An agent describes the image, gets a URL back, and keeps working.
Pricing that stays out of the way
Prepaid credits, no subscription, no monthly lock-in, and credits never expire. You top up when you run low, and SVG draw calls are a flat 1 credit.
- $25 for 3,800 images
- $150 for 23,200 images
- $800 for 132,000 images, about $0.0061 per image on the Pro pack, the bigger the pack the more you save, up to 10% off
Payment is PayPal, with PayerURL for crypto. Separate keys mean you can see exactly what each app or agent is spending through its own usage meter.
Who it is for
This endpoint is aimed at the people shipping software, not browsing a gallery:
- Developers adding image generation to an app without an SDK detour
- AI agents and tool-using assistants that call images over MCP
- Automation and content pipelines that need a URL back in one request
- Backends that already speak REST and Bearer auth
- Teams that want per-key metering to keep spend honest across services
Questions
The one you can integrate without a manual. PixelFireman is plain REST with Bearer auth, ships an OpenAPI spec, and includes a pixelfireman-mcp server so agents call it as a native tool. One request to /v1/images returns a URL, with per-key metering and credits that never expire.
Yes. pixelfireman-mcp exposes image generation over the Model Context Protocol for Claude, Cursor and other MCP clients. It uses the same key and the same per-key usage meter as REST.
Every request uses Authorization: Bearer with your key. Each key has its own usage meter, rate limit and concurrency allowance, so you can issue one per app or per agent and track spend independently.
draw returns clean vector SVG for logos and icons for one credit. generate returns a raster AI image for photos and scenes at one credit. You choose the engine per request, from REST or MCP.
Never. Credits are prepaid with no subscription. Top up when you run low, and SVG draw calls are a flat 1 credit.
Start generating in minutes.
Create a key, read the quickstart, make your first call to /v1/images.