Usage ledger

GET /api/v1/mystery/billing/usage packs:read

The usage ledger behind GET /billing, newest first. Each row is one billable event with its amount, token, invoice state (invoiced_at / invoice_ref are null until the daily invoice stamps them) and full source metadata — for POOL_ITEM_PULLED that includes the on-chain transaction hash, the destination wallet and the pricing source used at pull time.

Try it GET /api/v1/mystery/billing/usage
response
200 43ms preloaded server-side with the default context
object · 3 keys 
{
  "success": true,
  "data": {
    "usage": []
  },
  "pagination": {
    "limit": 50,
    "offset": 0,
    "has_more": false
  }
}
curl (tracks the inputs above) 
curl -X GET 'https://service.rip.fun/api/v1/mystery/billing/usage' \
  -H 'X-API-Key: rip_…'

Request fields

FieldTypeRequiredDescription
typequery string—BUYBACK_USDC_FRONTED or POOL_ITEM_PULLED
invoicedquery string—"false" = accrued only (what you owe), "true" = already invoiced
limit / offsetquery number—Pagination (default 50, max 100)

Response fields (data)

FieldDescription
usage[].usage_type / amount_usdcWhat and how much
usage[].token_id / metadataThe item + source detail (tx hash, recipient, value source)
usage[].invoiced_at / invoice_refnull until the daily invoice claims the row

Errors

StatusCodeWhen
400invalid_usage_type?type= is not a known usage type

See Errors for the response envelope and the full code list.