Usage and activity

Usage and activity shows what the workspace used and spent: units and money for each request, kept apart, as the platform counts them. Every member reads it.

A date range (24 hours, 7, 14, 30 or 90 days, or your own), the model or deployment, the key or tool, the project label, the pool, the lane, the pricing mode, on demand or batch, the outcome, and the billing unit.

• Over time: requests, units and spend per day, spend in USD on its own axis.
• Units: per model and billing unit, uncached and cached input apart.
• Money: per model and pricing mode, in USD.
• Failed requests: by error class, for the range and each period that saw one. A refused or failed request is counted with its class, and its charge follows the retry rule.
• Activity: each request with its units and money, newest first.

Opening a request shows when it ran, the model or deployment it asked for and the model that served it, the engine, the credential (the key or the person's tool), the project, its requirements (the pool, after fallback where it was taken, the lane, the pricing mode, the region), the request-data policy it ran under, the route, its outcome and error, its latency, the quote and rate version, the charged units and amount, and the attempts behind it, each with its outcome and whether it was charged. Never the device or the worker that ran it. A request sent to a router shows the router and the model it chose. A correcting row adjusts an earlier request, whose own row stays as it was.

Task inputs uploaded through POST /v1/uploads, as metadata. Deleting one deletes the object at once, and asks for a recent sign-in.

The CSV of the current filter, units and money in separate columns.