Brand files for AI agents
The same Production Pack, machine-callable: a structured brief, three directions, a true-vector pack, a JSON manifest and a spec the agent can re-render. Pay per pack in USDC on Base with x402.
Agent API (2026-11-09): the contract, the free endpoints and the paid checkout are live. A preview is $1 and a Production Pack $19 in USDC on Base, paid per request with x402, with no account, API key or card. A request that arrives without payment returns 402 with the exact amount, asset, network and address.
The contract
The API returns a manifest, not a paragraph: signed URLs, a SHA-256 for every file, the palette, the font licence, the QA gate results and the parametric spec. The agent can hand the zip to its user and the manifest to its own code.
POST https://dosiefoxie.com/api/v1/orders
content-type: application/json
{"brief":{"name":"Salthouse Smokehouse","trade":"wood-smoked fish","style":"woodcut"}}
# 402 + PAYMENT-REQUIRED (USDC on Base)
# pay, retry with PAYMENT-SIGNATURE
# 202 + order_id; poll GET /api/v1/orders/{id}The six pages
- Logo API for AI agents: production files, not a PNG
What an agent gets from the Dosie Foxie API: SVG, EPS, PDF, six lockups, favicon, spec.json, QA and a licence. Pay per pack in USDC on Base.
- x402 logo generator: a pack, paid per request
How x402 works for a logo pack: HTTP 402, USDC on Base, exact scheme, no account or API key, and a production pack when the payment settles.
- MCP logo server: a brand-file tool for agents
The live Dosie Foxie MCP server: six tools over the same contract as the HTTP API, the exact names it answers to, and why a tool call cannot pay its own x402 invoice.
- SVG logo API: true vector, not a traced bitmap
What a real SVG logo API should return: outlined type, one ink per file, six lockups, a favicon, a print PDF, spec.json and a QA report.
- Brand file API: the 12 deliverables, in one call
The production-file checklist an agent should get back: vectors, both layouts, mono/reverse, favicon, app icon, avatars, print PDF, spec.json and a font licence.
- How to give an AI agent a logo
A practical loop for agent builders: write a structured brief, get three directions, pick one, pay per pack with x402, and hand the files to the user.
Machine-readable
OpenAPI 3.1 · llms.txt · llms-full.txt · A2A agent card · sample pack (free)
What the pack contains
| Deliverable | Format | Use |
|---|---|---|
| Primary lockup | SVG + EPS | website, invoice, email |
| Stacked lockup | SVG + EPS | square spaces, packaging |
| Icon | SVG + EPS | favicon, app icon, avatar |
| Wordmark | SVG + EPS | when the mark is already present |
| Mono | SVG + EPS | one-colour print, embroidery |
| Reverse | SVG + EPS | dark backgrounds, signage |
| Print PDF | vector handoff to a printer | |
| PNG 512 + 1024 | PNG | web, social, decks |
| Favicon | ICO | browser tab |
| Maskable app icon | PNG 512 | PWA / app icon |
| Social avatars | PNG 400 | profiles |
| Spec + mark | JSON + SVG | re-render and edit |
Who it is for
- Agent builders that need a production pack, not a picture.
- AI website and app builders that need a logo per project.
- Domain, LLC and storefront onboarding flows that need a brand file set.
- Platforms that want an API key, credits and an invoice instead of a wallet.