Billing and statement fields

How billing works

Synchronous calls: an estimate is held before the request, the exact amount is settled from the upstream usage after the response, and the difference is released immediately. Async tasks: the cap is held at submission and settled at actual tokens after the terminal state. All amounts are recorded in micro-USD and every statement line can be recomputed.

Deduction order: plan quota → resource packs → gift balance → available balance → credit line.

Statement fields

Reconciling in the console

The Usage page aggregates by day; the Request logs page lets you search every request by model, status and time; the Ledger page shows account entries (top-ups, consumption, holds, settlements, releases, reversals, rebates).

Export call logs as CSV

GET/api/v1/usage/logs.csv

Downloads your own call logs as CSV using the same filters as the log list. The response is a text/csv; charset=utf-8 attachment named like usage-logs-20260902.csv, stamped with the UTC day it was produced. The body starts with a UTF-8 byte-order mark so spreadsheets open it without mangling the text.

curl -OJ "$LINK42_CONSOLE/api/v1/usage/logs.csv?model=seedance-2.0&status=200" \
  -b "$LINK42_SESSION_COOKIE"

created_at,request_id,api_key_prefix,protocol,requested_model,upstream_model,status_code,error_code,input_tokens,output_tokens,cached_tokens,reasoning_tokens,charged_usd,duration_ms,ttft_ms

• One export writes at most 20,000 rows and truncates the rest. Split the range to pull a longer history.
• charged_usd is US dollars with six decimals. ttft_ms is empty for non-streaming requests.
• The file is streamed 500 rows at a time. If a later page fails to load, the download ends at the last complete page instead of turning into an error response.

Export ledger entries as CSV

GET/api/v1/ledger/entries.csv

Downloads your own ledger entries as CSV using the same filters as the ledger list. The file is named like ledger-20260902.csv, also carries the UTF-8 byte-order mark, and is capped at the same 20,000 rows.

curl -OJ "$LINK42_CONSOLE/api/v1/ledger/entries.csv?type=consume&start=2026-08-01T00:00:00Z&end=2026-09-01T00:00:00Z" \
  -b "$LINK42_SESSION_COOKIE"

created_at,transaction_id,tx_type,account_type,amount_usd,balance_after_usd,api_key_prefix,model,request_id,order_no,description

• amount_usd and balance_after_usd are US dollars with six decimals, and a minus sign marks a debit. account_type is one of available, frozen, gift or credit.
• An invalid window, where start is not before end, answers 422 invalid_time_range; a type outside the enumeration answers 422 invalid_ledger_type.

Agent wholesale quote

POST/api/v1/agent/wholesale/preview

An agent orders at their own price multiplier: credit tops up the agent's own balance, while plan and pack buy a subscription or a resource pack for a bound customer. Preview only prices the request — it creates no order and moves no money.

The payable amount is the list price multiplied by the price multiplier, rounded to micro-USD. multiplier_ppm is parts per million, so 1000000 means no discount, and discount_micro_usd is the difference between the list price and the payable amount.

curl -X POST "$LINK42_CONSOLE/api/v1/agent/wholesale/preview" \
  -H "Content-Type: application/json" \
  -b "$LINK42_SESSION_COOKIE" \
  -d '{"kind": "plan", "plan_id": 7, "customer_user_id": 3120}'

{
  "data": {
    "kind": "plan",
    "plan_id": 7,
    "pack_id": null,
    "item_name": "Growth Monthly",
    "customer_user_id": 3120,
    "list_price_micro_usd": 99000000,
    "multiplier_ppm": 820000,
    "payable_micro_usd": 81180000,
    "discount_micro_usd": 17820000
  },
  "request_id": "req_01J…"
}

• The field combination must match the kind exactly: credit cannot carry plan_id, pack_id or customer_user_id; plan and pack cannot carry credit_micro_usd and cannot name the agent as their own customer. Anything else answers 422 wholesale_invalid.
• A customer not bound to this agent answers 422 wholesale_customer_not_bound. A missing agent profile answers 404 agent_not_found and a suspended one answers 403 agent_suspended. A multiplier outside the configured range answers 422 wholesale_multiplier_out_of_policy, which an operator has to fix on the profile.

Agent wholesale orders

POST/api/v1/agent/wholesale/orders

Once the quote looks right, create the order with the same body plus a payment channel. The order belongs to the agent; when the money lands, a plan or pack is delivered to the beneficiary customer, while credit goes to the agent's own balance.

The response is {order, wholesale, replayed}. order is a regular payment order carrying that channel's checkout details (pay_url, a QR code, or a USDT deposit address); wholesale is the record keeping the list price, the multiplier, the payable amount and the beneficiary.

curl -X POST "$LINK42_CONSOLE/api/v1/agent/wholesale/orders" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 9d7258b0da1c42df" \
  -b "$LINK42_SESSION_COOKIE" \
  -d '{"kind": "plan", "plan_id": 7, "customer_user_id": 3120, "provider": "stripe"}'

• The first create answers 201. Replaying the same idempotency key answers 200 with replayed set to true, and no second order is opened.
• GET /api/v1/agent/wholesale/orders pages this agent's wholesale orders and accepts status and kind filters.
• If the payment order is created but the wholesale record cannot be stored, the platform closes that order immediately with close_reason wholesale_record_failed, so the purchase can never be delivered to the agent by mistake.