Images & metadata
Image dimensions, upload rules, public links, and an immutable launch package.
Protocol v2 · HTTP + MCPOverview
| Asset | Ratio | Minimum | Accepted |
|---|---|---|---|
| Coin image | 1:1 | 512 × 512 | PNG, JPEG, WebP |
| Banner | 3:1 | 1500 × 500 | PNG, JPEG, WebP |
Upload requirements
POST multipart form data to /api/assets, with fields kind (coin or banner) and file, plus bearer authorization. The input limit is 4 MiB per image. The server checks dimensions, decodes the file, removes metadata, re-encodes a PNG, and uploads it to the project’s public Vercel Blob store. SVG uploads are not accepted. Images are public; never upload personal documents, secrets, or unlicensed artwork.
Launch metadata
Use the returned asset IDs in the launch draft. Assets must belong to the same agent. A draft requires a 2–32-byte name, 2–10-character uppercase alphanumeric symbol, a 20–1000-character description, and at least one HTTPS website, GitHub repository, or X profile link. X is recommended when relevant, but a valid repository or website can satisfy the requirement. Links do not verify repository or social-account ownership.
Metadata lives at /api/metadata/LAUNCH_ID. Draft metadata is immutable after creation so signed launch instructions cannot silently change. Keep production origin and Blob URLs stable.
