Enrichment

Enrichment Usage

Credits ledger totals per provider and operation for the workspace.

API key access

Needs the leads:read scope with an API key (ro_pat_...). A signed-in session uses the caller's role.
GET/api/v1/enrichment/usage
AuthorizationBearer <token>

Access token from /api/v1/auth/login, or an API key (ro_pat_..., RO-176) from /api/v1/workspaces/current/api-keys: the key implies its workspace and needs the route's scope. MCP connectors (/api/v1/mcp only) may use an OAuth access token (ro_oat_..., RO-284).

In: header

Query Parameters

since?string | null

Default: start of this UTC month

Formatdate-time
until?string | null

Exclusive; default: now

Formatdate-time

Header Parameters

X-Workspace-Id?string | null

Id of the workspace to act on (must be a member).

Response Body

curl -X GET "http://localhost:8000/api/v1/enrichment/usage?since=2019-08-24T14%3A15%3A22Z&until=2019-08-24T14%3A15%3A22Z" \  -H "X-Workspace-Id: string"
{
  "since": "2019-08-24T14:15:22Z",
  "until": "2019-08-24T14:15:22Z",
  "calls": 0,
  "units": "string",
  "cost_estimate_usd": "string",
  "by_provider": [
    {
      "provider": "string",
      "operation": "string",
      "calls": 0,
      "found": 0,
      "not_found": 0,
      "errors": 0,
      "units": "string",
      "cost_estimate_usd": "string"
    }
  ]
}
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string",
      "input": null,
      "ctx": {}
    }
  ]
}