Activity
What your calls cost at list price, the tokens they used and the calls refused, day by day, split by event_type.
Units recordedpeak 440 on Oct 25
Refusedpeak 1 a day
Oct 25
By event_type the last 24 hours, heaviest first
The units recorded in this window, in the units your code reported, grouped by the event_type each record carried. record() in both SDKs sends its agent_id as the event_type, so for those calls this is a split by agent; meter() and a direct POST /events carry the event name your code passed.
| event_type | Share of units | Units | Records |
|---|---|---|---|
| crawler | 220 | 4 | |
| enricher | 123 | 5 | |
| researcher | 79 | 2 | |
| summarizer | 18 | 2 |
Shares are of all 440 units recorded in the window. The same split is on GET /usage?by=event_type.
Day by day the last 24 hours, newest first
| Day | Metered | Refused | Refused units |
|---|---|---|---|
| Oct 25 Sun | 440 | 1 | 173 |
Every number on this page is on the API too:
GET /decisions for refusals, /tasks for budgets and /tasks/:task_ref for a job's list-price estimate, /usage?by=event_type for the split by event_type and its estimate, /customers for balances, /keys for keys, each with Authorization: Bearer <your key>.