Activity

What your calls cost at list price, the tokens they used and the calls refused, day by day, split by event_type.

7 dayssample

Units recordedpeak 960 on Oct 20

Refusedpeak 3 a day

Oct 19Oct 20Oct 21Oct 22Oct 23Oct 24Oct 25

By event_type the last 7 days, 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_typesample

event_type	Share of units	Units	Records
crawler	50% of units	2,120	42
enricher	28% of units	1,187	47
researcher	18% of units	763	19
summarizer	4% of units	170	14

Shares are of all 4,240 units recorded in the window. The same split is on GET /usage?by=event_type.

Day by day the last 7 days, newest first

7 dayssample

Day	Metered	Refused	Refused units
Oct 25 Sun	440	1	173
Oct 24 Sat	600	2	346
Oct 23 Fri	760	2	346
Oct 22 Thu	360	1	173
Oct 21 Wed	480	2	346
Oct 20 Tue	960	3	519
Oct 19 Mon	640	2	346

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>.