See where AI spend goes by team,
workflow, model, and vendor.
P402 Monitor turns the metering ledger into department, employee, workflow, model, vendor, and customer dashboards with outcome and evidence status.
Read-only over the ledger. Monitor never changes runtime behavior.
AI spend has no owner.
Without attribution, finance cannot tell which department, workflow, model, or vendor caused which cost. Monitor breaks every event out by owner so spend, outcome, and evidence land in one ledger.
- 01Connect P402 metering.Route AI calls through P402, or post meter-only events from your backend. Monitor reads the same ledger Meter writes.
- 02Group events by owner taxonomy.Aggregate by department, employee, workflow, model, vendor, customer, outcome, or evidence status, in any combination.
- 03Filter by department, workflow, model, vendor, or customer.Drill into the subset that matters. Compare against a chosen baseline window to see drift.
- 04Export the breakdown for finance review.CSV and finance report bundles for procurement, finance, and audit, without exposing prompts.
Attribute economics, not content.
Monitor reads the same metadata-only events Meter records. Prompt and response storage are off by default. The dashboards render owner, workflow, model, vendor, customer, outcome, and evidence without touching tenant content.
metadata_onlyOwner, cost, tokens, budget, policy, outcome, and evidence status. No prompts. No responses. Default.fingerprint_onlyAdds a hash fingerprint of prompt and response for dedup and replay protection. Content stays out.redacted_tracePrompt and response retained after a redaction pass for fields the tenant policy allows.private_gatewayYour environment hosts the inference, P402 records the economic event over a signed channel.full_traceOpt-in. Prompts and responses retained verbatim with the event. Requires explicit tenant policy.
Same metering layer, four shipped workflows.
Each vertical demo is a working surface on the same metering layer. Use them to see the event detail, ownership attribution, policy result, and evidence status against a concrete workflow.
Spot the workflow that quietly eats your margin.
Monitor groups your AI events by workflow, model, vendor, and customer, with cost and outcome on every row. Find the retry storm, the long-context call, or the failing workflow without a separate analytics pipeline.
Give finance one ledger for AI spend.
One ledger across departments, employees, workflows, models, vendors, and customers. Finance, procurement, and audit work from the same event detail, with privacy mode, policy result, outcome, and evidence status on every event.
Does Monitor change runtime behavior?+
No. Monitor is read-only over the metering ledger. It groups, filters, and exports events that Meter already recorded. It does not gate, throttle, or reroute calls.
What dimensions are available?+
Department, employee, workflow, model, vendor, customer, outcome, evidence status, and drift. Every dimension is sourced from the event ownership Meter captured at request time.
Does it work without prompts?+
Yes. Monitor reads the same metadata-only events Meter records by default. No prompts, no responses, and no tenant content is required to render attribution.
Can finance export this?+
Yes. Each view exports to CSV and to a finance report bundle. Finance, procurement, and audit can review the same ledger without engineering pulling reports by hand.
How does it differ from cloud cost tools?+
Cloud cost tools report infrastructure spend after the billing period closes. Monitor reads AI economic events at request time, with owner, workflow, model, vendor, outcome, and evidence already attached.
What is the first integration step?+
Create a P402 key and send one metered event, or route an existing OpenAI-compatible request through P402. The first event lands in the ledger and Monitor renders against real data.
Give every token an owner.
Start with one metered event. Monitor renders the ledger by department, workflow, model, vendor, and customer the moment events land.