Image Hosting

<think> The userwants us to translate a skill description into concise Chinese. Return JSON only like {"description_zh":"..."}. The description: "Upload images to img402.dev and get a public URL. Three tiers: free (1MB, 7-day, no auth), $0.01 USDC (5MB, 1-year, x402), or $1 USDC (5MB, permanent, x402)...." We need to translate into concise Chinese. The JSON should contain a key "description_zh" and value is the Chinese translation. Weneed to be careful about content: it's a description of a service that includes paying with USDC, referencing x402. The user isbasically requesting a translation. It's allowed content. No policy violation. So we can comply. Provide concise Chinese translation. The translation should be concise. Perhaps:"上传图片至 img402.dev 并获取公开链接。提供三个层级：免费版（1MB，7天有效期，无需认证），0.01 USDC（5MB，一年有效期，x402），或 1 USDC（5MB，永久有效，x402）。" Better to use Chinese punctuation?Might use Chinese punctuation: "上传图片至 img402.dev 并获取公开链接。三个层级：免费（1 MB，7 天，无认证），0.01 USDC（5 MB，1 年，x402），或 1 USDC（5 MB，永久，x402）。" But betterto keep it concise. The description is short; we can translate it exactly. Thus the JSON: { "description_zh": "上传图片至 img402.dev 并获取公开链接。三个层级：免费（1 MB，7 天，无认证），0.01 USDC（5 MB，1 年，x402），或 1USDC（5 MB，永久，x402）。" } We need to make sure we use double quotes and correct JSON. Ensure it's valid. Onepossible nuance: x402 is likely some specific identifier for the payment channel, we can keep as "x402". In Chinese we cankeep it as "x402". Also "USDC" can be left as "

Image Hosting — img402

Upload an image to img402.dev and get a public URL. No account, no API key, no config.

Pick a tier

| Tier | Price | Max size | Retention | Use when | |------|-------|----------|-----------|----------| | Free | $0 | 1 MB | 7 days | Trying things out, ephemeral sharing, PR review screenshots | | 1-year | $0.01 USDC | 5 MB | 1 year | Diagrams, docs, references | | Permanent | $1.00 USDC | 5 MB | Permanent* | Blog hero images, public docs, brand assets |

* Service-life retention. If img402 ever shuts down, there's a 90-day on-site notice before takedown. See Terms § 2A.

Quick reference

# Upload (multipart)
curl -s -X POST https://img402.dev/api/free -F image=@/path/to/image.png

# Response
# {"url":"https://i.img402.dev/aBcDeFgHiJ.png","id":"aBcDeFgHiJ","contentType":"image/png","sizeBytes":182400,"expiresAt":"2026-02-17T..."}

Workflow

Get image: Use an existing file, or generate/download one.

Check size: Must be under 1MB. If larger, resize:

sips -Z 1600 /path/to/image.png    # macOS — scale longest edge to 1600px
convert /path/to/image.png -resize 1600x1600 /path/to/image.png  # ImageMagick

Upload:

curl -s -X POST https://img402.dev/api/free -F image=@/path/to/image.png

Use the URL: The url field in the response is a public CDN link. Embed it wherever needed.

Constraints

Max size: 1MB
Retention: 7 days
Formats: PNG, JPEG, GIF, WebP
Rate limit: 1,000 free uploads/day (global)
No auth required

Paid tiers

When the user needs a longer-lived URL, use the paid flow. Two-step: pay for an upload token via x402, then upload the image with the token.

# Step 1: Get an upload token (requires x402 payment)
POST https://img402.dev/api/upload/token            # $0.01 USDC → 1-year retention
POST https://img402.dev/api/upload/token/permanent  # $1.00 USDC → permanent retention
# → {"token": "a1b2c3...", "expiresAt": "..."}

# Step 2: Upload with the token (same endpoint either way)
curl -s -X POST https://img402.dev/api/upload \
  -H "X-Upload-Token: a1b2c3..." \
  -F image=@/path/to/image.png
# → {"url":"...", "id":"...", "contentType":"...", "sizeBytes":..., "expiresAt":"..."|null}

For permanent uploads the response has expiresAt: null. Same flow otherwise.

x402 payment is handled by an x402-capable client (the Payments MCP tool, @x402/client, or any other). The client handles the 402 challenge, signs the on-chain payment, and retries automatically. See https://img402.dev/blog/paying-x402-apis for details.

Public access

Uploaded images are reachable by anyone with the URL — there is no auth on serving. Do not upload screenshots of internal systems, personal information, secrets, API keys, or anything else that shouldn't be public. Once uploaded, the only way to remove an image is to wait for expiry (free / 1-year tiers) or email privacy@img402.dev.