Where Sume documents plans, wallet and rates: which page answers what

Sume documents billing across five docs pages, and each answers a different question: Billing and credits for the wallet and top-ups, Usage for the ledger, Generation admission for plan limits, Errors and rate limits for the status codes, and the model pages for the list x 1.25 rule. The docs give you the mechanics, not a plan price list.

That last point matters when you plan a budget. The docs say the API pricing page on sume.com is generated from the same pricing constants as the API bills, so use that page or the model catalog for rates, and use the docs for how money moves.

Question to page

Read 2026-10-09 from the repo docs on origin/main.

A five-line check of the whole flow

The fastest way to learn the model is to run one job. Read the balance, submit a 10-second Wan 3.0 720p clip (price $1.25), and read the usage rows for that job: you should see a reserved row, then a captured row of $1.25 after completion.

import os, requests

H = {"Authorization": f"Bearer {os.environ['SUME_API_KEY']}"}
r = requests.get("https://api.sume.com/v1/balance", headers=H, timeout=30)
r.raise_for_status()
micros = r.json()["data"]["balance"]["available_amount_usd_micros"]
print(f"balance: ${micros / 1_000_000:.2f}")
# then submit one job and read its ledger rows:
# GET /v1/usage?job_id=<id>  -> reserved, then captured

What the docs deliberately do not say

They do not publish how much a plan costs per month, and they do not list a per-model price table in prose. The usage page says the metered rates live on the API pricing page. They also warn against inventing prepaid top-ups through the API: top-ups are a dashboard operation.

Trust order for a number: the live catalog (pricing_skus), then the pricing page, then a blog table like the ones here. A blog table has a read date for a reason.

Gotchas

• Older docs and links call Billing & subscription 'Credits'; the product nav label is Billing & subscription.
• Concurrency comes from the plan; a top-up does not change it.
• The ledger shows reservations, captures, refunds, top-ups and grants, and the entries change with the workspace and environment.