Usage metering
Send one event per billable action. Clocknext turns it into credits drawn, outcomes billed, and usage you can show a customer.
A signal is any event worth charging for: an agent run, a tool call, a batch of tokens, a resolved ticket. Define it once, send it from wherever it happens, and it flows into pricing, wallets, and margin without a second pipeline.
Definitions
Define a signal and what it draws: one credit per agent run, a credit per thousand tokens, a unit per document. Change the rate later without re-instrumenting anything.
Signal definition
Signal
agent.run
Draws
1 credit per run
Used in
4 plans
Active
Ingest
One endpoint takes events from your backend or straight from your agent framework. Same signal, same result, whichever path it arrives on.
Event
Endpoint
POST /v1/events
Signal
agent.run
Customer
acme
Accuracy
Send an idempotency key with each event. A retried call is recognised and rejected rather than billed twice, so a network blip doesn't turn into a refund conversation.
Duplicate check
Idempotency key
run_8f2a
First seen
14:22:05
Billed
Once
Rejected
Four steps, from your code to their bill.
Name the event and say what one of them draws down.
Send the event when the action happens, with a customer ID and an idempotency key.
The signal is matched to the customer's plan and converted into credits, outcomes, or units.
Usage rolls up per cycle, with provider cost attributed to the same signal.
Usage metering is part of a bigger platform designed to make AI billing a breeze.
Usage metering ships with Clocknext's other primitives, ready to feed pricing, wallets, and margin.