compute
API · v1

Build on Compute.

Use Compute from your own apps, bots and from Claude: read coin data, generate images ($0.03 each), render Blender scenes, and launch or trade coins with your own wallet signing every transaction.

Keys and credits

A key acts as your wallet on the API only. Images and renders are paid from your prepaid credits, the same balance the studio uses. A key can never sign a transaction, move funds or spend a coin’s budget. Up to 5 keys per wallet.

Loading your keys…

Use with Claude

Add Compute to Claude as a connector and ask in plain words: “make a square image of a lighthouse at dusk”, “what are the most-used coins this week?”, “render frames 1 to 24 of my scene”. Claude uses your key and your credits.

Claude Code

claude mcp add --transport http compute https://computepad.io/api/mcp \
  --header "Authorization: Bearer cmp_YOUR_KEY"

Claude Desktop

Settings → Developer → Edit Config, add this to claude_desktop_config.json, then restart Claude.

{
  "mcpServers": {
    "compute": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://computepad.io/api/mcp", "--header", "Authorization:${COMPUTE_AUTH}"],
      "env": { "COMPUTE_AUTH": "Bearer cmp_YOUR_KEY" }
    }
  }
}

What Claude can do

  • compute_status

    Whether image generation and rendering are on, and their prices.

  • list_coins

    Coins launched on Compute, newest first.

  • coin_leaderboard

    The most-used coins, ranked by GPU time or images made (never by price).

  • coin_market

    Price, market cap, 24-hour volume and liquidity for one coin. Use the coin id from list_coins.

  • coin_gpu_budget

    How much GPU budget a coin has and what has filled it.

  • get_credits

    The prepaid credit balance that pays for images and renders.

  • generate_image

    Make an image with FLUX.1 [schnell] on an NVIDIA GPU, paid from the user's credits ($0.03 each). Waits up to about 50 seconds and shows the result; if it is still running, call get_image later.

  • get_image

    Status of an image, and the image itself once it is done.

  • create_render_upload

    Step 1 of a render: get an upload link for a .blend file. Give its exact size in bytes and its SHA-256. Then upload the file with an HTTP PUT to the returned url, with exactly the returned headers.

  • start_render

    Step 2 of a render: render frames of an uploaded scene, paid per frame from the user's credits. Returns a render id; check it with get_render.

  • get_render

    Status of a render, and a download link for its frames (a zip of PNGs) once it is done.

  • launch_coin

    Coins launch from the user's own wallet, which must sign. This returns the Compute launch page where they review and sign; it does not launch anything by itself.

Quickstart

# Read the newest coins
curl https://computepad.io/api/v1/coins -H "Authorization: Bearer $COMPUTE_API_KEY"

# Generate an image (charged $0.03 to your credits)
curl -X POST https://computepad.io/api/v1/images \
  -H "Authorization: Bearer $COMPUTE_API_KEY" -H "Content-Type: application/json" \
  -d '{"prompt":"a lighthouse at dusk","preset":"landscape","idempotencyKey":"my-request-0001"}'

# Poll it, then download it
curl https://computepad.io/api/v1/images/JOB_ID -H "Authorization: Bearer $COMPUTE_API_KEY"
curl https://computepad.io/api/v1/images/JOB_ID/output -H "Authorization: Bearer $COMPUTE_API_KEY"

Endpoints

Coin data

  • GET/api/v1/status

    Network, and image and render prices. No key needed.

  • GET/api/v1/coins

    Launched coins, newest first. ?limit= and ?cursor=.

  • GET/api/v1/coins/leaderboard

    Most-used coins by GPU time or images. ?by=gpu|images ?window=24h|7d|all.

  • GET/api/v1/coins/{id}/market

    Price, market cap, 24-hour volume, liquidity and change.

  • GET/api/v1/coins/{id}/chart

    Price candles. ?interval= ?limit=.

  • GET/api/v1/coins/{id}/holders

    Largest holders, read from the chain.

  • GET/api/v1/coins/{id}/gpu-budget

    The coin’s GPU budget and what fills it.

Images

Paid from your credits.

  • GET/api/v1/credits

    Your prepaid credit balance.

  • POST/api/v1/images

    {prompt, preset, seed?, idempotencyKey?}. Returns 202 and a job.

  • GET/api/v1/images

    Your recent images.

  • GET/api/v1/images/{id}

    One image and its status.

  • GET/api/v1/images/{id}/output

    A download link for a finished image, valid 5 minutes.

Renders

Blender scenes to PNG frames, paid per frame from your credits.

  • POST/api/v1/renders/uploads

    {bytes, sha256} of your .blend. Returns a URL and headers to PUT the file to.

  • POST/api/v1/renders

    {uploadId, frameStart, frameEnd, resolutionPercent, samples}. Returns 202 and a render.

  • GET/api/v1/renders/{id}

    One render and its status.

  • GET/api/v1/renders/{id}/output

    A download link for the zip of frames, valid 5 minutes.

Launch and trade

Every transaction comes back unsigned. Your own wallet signs it; Compute never holds your keys.

  • POST/api/v1/projects

    Create the coin’s project: name, ticker, description, artwork.

  • POST/api/v1/projects/{id}/metadata

    Publish its token metadata. Returns the metadata URI for the launch.

  • GET/api/v1/gpu-catalog

    GPUs a coin can be paired with, and the launch prepay terms.

  • PUT/api/v1/projects/{id}/gpu-pairing

    Pair the coin with a GPU before launch.

  • POST/api/v1/launches

    {requestId, projectId, metadataUri, devBuyLamports?}. Prepares the launch.

  • POST/api/v1/trades/quote

    {route, mint, side, amount, slippageBps}. A signed, short-lived quote.

  • POST/api/v1/trades

    {requestId, projectId, quote}. Prepares the trade.

  • GET/api/v1/operations/{id}/prepared

    The unsigned transaction to sign.

  • POST/api/v1/operations/{id}/signing

    Tell Compute you are about to sign.

  • POST/api/v1/operations/{id}/submit

    {signedTransactionBase64}. Submits your signed transaction.

  • POST/api/v1/operations/{id}/relay

    Rebroadcasts it until it lands or expires.

  • GET/api/v1/operations/{id}

    Where the launch or trade stands.

Limits and rules

  • Rate limits. 300 reads and 30 writes a minute per key, and 120 Claude calls a minute. Launches and trades share your wallet’s website limits. Over a limit you get 429.
  • Spending limits. The studio’s daily caps and concurrency limits apply to every key. An empty balance returns 402 and charges nothing. Add credits with USDC or SOL from the wallet page.
  • Retries. Send an idempotencyKey with each image or render. Repeating it returns the same job instead of charging twice.
  • Content. Prompts and images pass the same content checks as the studio. A rejected prompt is not charged.
  • Wallet transactions. Launches and trades return an unsigned transaction. Sign it with the same wallet that owns the key; anything else is refused.
  • Errors. Every error is JSON: {"error":{"code":"…","message":"…"}}.
  • Keys. Keep keys on your server or in your Claude config, never in a website or app bundle. Revoke one here and it stops working immediately.