> _ P402 PROVE

Prove every AI
economic event.

P402 Prove exports evidence bundles, finance reports, and event proof for every AI call recorded by Meter, with privacy mode, policy result, and outcome attached.

See evidence Export sample evidence

Bundles render in the default metadata-only privacy mode. Prompt content stays out unless the tenant policy opts in.

The problem

Audit cannot start from invoices.

Provider invoices show totals, not events. Compliance, finance, and procurement reviews need per-event proof with owner, privacy mode, policy result, outcome, and signature status. Prove emits those bundles directly from the ledger.

What Prove emits

Event detail

Per-event owner, workflow, model, vendor, tokens, and cost.

Privacy posture

Privacy mode the event was recorded under, on every row.

Policy result

Approved, warned, denied, or requires review at record time.

Outcome

Accepted, rejected, revised, escalated, or failed.

Receipt

Settlement receipt status when the event is payable.

Signature

Signature over the event set, verifiable without P402.

Evidence bundle

Signed package of events and manifest for audit review.

Finance report

Finance-ready report grouped by owner, workflow, and vendor.

CSV appendix

Row-level export for procurement and ad-hoc analysis.

How it works

01
Filter the ledger by owner, time window, or workflow.
Narrow the event set to the scope the reviewer needs. Owners, workflows, models, vendors, and customers are all available.
02
Choose evidence bundle, finance report, or CSV appendix.
Three packages. Evidence bundles for audit, finance reports for the close, CSV appendices for procurement and ad-hoc analysis.
03
Verify privacy mode and policy result on each event.
Every row reports the privacy mode at record time and the policy result the event produced. No event lacks attribution.
04
Export the package for audit or finance review.
Signed package with manifest. Auditors can verify integrity without contacting P402.

Privacy

Evidence over economics, not content.

Prove emits bundles from the same metadata-only events Meter records by default. Every row carries the privacy mode it was recorded under. Prompt content stays out unless the tenant policy opts in to a retaining 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.

Read the trust posture

Proof

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.

Healthcare

Medicaid prior authorization with HIPAA-aligned demo mode and human review gate.

Legal

M&A contract due diligence across an 8-document synthetic data room.

Real estate

Tenant application screening with fraud scoring and HUD fair-housing audit trail.

Enterprise

Department, employee, model, and workflow attribution across one organization.

For developers

Hand audit a verifiable trail without giving up prompts.

Every event Meter records can be exported as a signed evidence bundle. Audit gets per-event owner, policy result, outcome, and signature status. Prompts stay in the privacy mode the tenant chose.

Start free

For enterprise

Give compliance evidence finance can sign off on.

Finance reports group AI spend by owner, workflow, and vendor. Evidence bundles carry per-event policy result, outcome, and signature status. One package serves finance, procurement, and audit at once.

Run AI Spend Audit

FAQ

What goes into an evidence bundle?+

Event detail, owner, workflow, model, vendor, tokens, cost, budget, policy result, outcome, privacy posture, receipt status, and signature status. The bundle is exported as a signed package for audit and finance review.

Are prompts ever exported?+

Only if the tenant policy opts in to a privacy mode that retains them. The default privacy mode is metadata-only, and evidence bundles render every economic field without prompt or response content.

Does Prove require settlement?+

No. Prove emits evidence from the metering ledger directly. If receipts or settlement are present they appear on the event. If not, the bundle still carries owner, policy result, outcome, and evidence status.

Can the bundle be hash-verified?+

Yes. Each bundle includes a signature over the event set and a manifest of the included rows. Auditors can verify integrity without contacting P402.

How does it differ from log retention?+

Log retention stores traces. Prove emits the economic event around each call with owner, policy result, outcome, and evidence status attached, packaged for finance and audit review.

What is the first step?+

Create a P402 key and send one metered event. Open Prove, filter the ledger, and export a sample evidence bundle, finance report, or CSV appendix.

Get started

Export evidence finance can sign off on.

Filter the ledger, pick the package, export the bundle. Audit, finance, and procurement work from the same evidence.