Give finance a real ledger for
AI spend.
P402 turns AI usage into a dashboard for department, employee, workflow, model, vendor, budget, outcome, and evidence status. Finance reviews the same event ledger compliance signs off on.
Metadata-only by default. Five privacy modes. P402 meters economics, not content.
AI spend lives outside finance.
AI provider invoices arrive after the fact, aggregated by month, with no department, employee, workflow, or vendor breakout. Finance owns the cost without the attribution. P402 records ownership when the call happens, then exposes it to finance, procurement, audit, and the budget owner in one ledger.
- 01Connect existing AI providers through P402.Route AI calls through P402, or post meter-only events from your backend. Existing OpenAI, Anthropic, Gemini, Bedrock, and OpenRouter integrations land in the same ledger.
- 02Tag events with owner taxonomy already used in finance.Department, employee, workflow, vendor, customer, and budget identifiers map to the same taxonomy finance already reports against. No new owner model required.
- 03Review department, workflow, model, vendor, and customer spend in the dashboard.Group and filter events by any combination of owners. Compare against a baseline window to see drift in cost, mix, or outcome.
- 04Export evidence bundles and finance reports for review.CSV and finance report bundles for procurement, finance, and audit. Evidence bundles surface policy result, privacy mode, and outcome per event without exposing prompts.
Meter economics, not content.
Enterprise dashboards run over the same metadata-only events Meter records. Prompt content is off by default. Finance, procurement, and audit review the ledger without touching tenant content. Sensitive workflows can run under private gateway mode.
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.
One ledger for AI spend by department, workflow, model, and vendor.
Stop reconciling AI provider invoices against engineering tickets after the month closes. P402 records attribution at event time. Finance opens the dashboard and sees AI spend by department, workflow, model, vendor, customer, and budget, with outcome and evidence already attached.
Evidence finance, audit, and legal can sign off on.
Every event records the privacy mode, policy result, owner, model, and outcome. Evidence bundles export the same record to finance, audit, and legal. Compliance reviews posture and exceptions in the same ledger finance reports from.
How does P402 attribute AI calls to a department or employee?+
Owner metadata is attached at the moment of the call. Department, employee, workflow, model, vendor, customer, budget, and policy result are recorded with the event, not reconstructed from invoices weeks later.
Does P402 store prompts?+
No, by default. P402 runs in metadata-only mode out of the box. Owner, cost, tokens, budget, policy result, outcome, and evidence status are recorded. Prompt and response content stay out unless the tenant opts in to a different mode.
How does this differ from a FinOps tool?+
FinOps tools report cloud spend after the billing period closes. P402 records the AI economic event when it happens, with owner, workflow, model, vendor, customer, budget, and outcome already attached. Finance reads the same ledger compliance signs off on.
Can P402 cover multiple providers?+
Yes. P402 wraps any HTTP-callable model behind one ledger. OpenAI, Anthropic, Gemini, Bedrock, OpenRouter, and direct provider calls land in the same attribution surface, with consistent owner and budget taxonomy.
What is required to start?+
Create a P402 key and route existing AI calls through it, or post meter-only events from your backend. The first event lands in the ledger and the dashboard renders against real data.
Who in the organization owns this?+
Finance owns the budget and the report. Engineering owns the integration. Compliance reviews the evidence bundles and privacy posture. P402 keeps the same event ledger as the source of truth for all three.
Run an AI Spend Audit, then keep the dashboard.
The audit produces the AI Spend Accountability Report. The same metering layer continues as a live ledger for finance, procurement, audit, and the budget owner.