Platform API

Usage for every connection on an app

Billable activity for the current month, grouped by end-user connection, plus what could not be charged to one.

The unattributed block is not an implementation detail. Summing only the per-connection numbers gives a figure that will not match the invoice you are reconciling against, and the gap is usage that belongs to a real end-user we cannot name.

Two kinds, deliberately kept apart:

  • none — no platform linkage at all. Normal for most traffic, not a problem.
  • ambiguous — the agent belongs to several connections and no X-Platform-Connection header said which. This usage belongs to someone. has_ambiguous_usage flags it so you do not have to notice a non-zero nested number.

totals is derived from the parts, never queried separately, so it cannot disagree with its own breakdown.

get/v1/platform/apps/{app_id}/usage

Request

  • Base URL: https://api.1claw.co
  • URL: https://api.1claw.co/v1/platform/apps/{app_id}/usage
  • Auth: HTTP bearer

Path parameters

app_idstring uuid required

Response

Usage report

app_idstring uuid required
period_startstring date-time required
period_endstring date-time required

Exclusive. The period is half-open, so an event at midnight belongs to one month, not two.

has_ambiguous_usageboolean required

Some usage this period belongs to an end-user who cannot be identified.

Example response

{
  "connections": [
    {
      "usage": {
        "inference_usd": "3.42"
      }
    }
  ],
  "unattributed": {
    "ambiguous": {
      "inference_usd": "3.42"
    },
    "none": {
      "inference_usd": "3.42"
    }
  },
  "totals": {
    "inference_usd": "3.42"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.