Changelog
New

Usage by client: see which client ran each job

Every job now records where it came from (dashboard, SDK, CLI, MCP, n8n, or direct API), with a usage-by-client breakdown in the dashboard and a new billing endpoint.

API Dashboard SDK

Jobs now record the client that submitted them. When you have traffic arriving from several places at once (the dashboard, the SDK in your backend, an MCP agent, an n8n workflow, the CLI, or direct API calls), you can now see how usage splits across them instead of guessing.

The Usage page in the dashboard has a new “Usage by client” panel that breaks down job count and spend per client over the selected period. There’s also a new API endpoint for pulling the same data programmatically.

  • New endpoint: GET /billing/usage-by-client returns job count and amount charged grouped by originating client.
  • New SDK method: client.billing.usageByClient({ days }).
  • The dashboard, SDK, CLI, and n8n node identify themselves automatically. Direct API calls are attributed as api, and you can label your own integration by sending an X-Rendobar-Client header.

Attribution is best-effort telemetry for analytics. It never affects auth, routing, or billing.

Spend, grants, and refunds are explained in credits and billing. The breakdown also surfaces per job in the redesigned Jobs page.

Share