P402
P402.io·Meter
DocsPricingDashboard
> _ P402 TRUST

Trust for AI spend
accountability.

P402 records the economic facts of AI work, not the private content behind it.

Read docsRequest security review

Metadata-only by default. No prompt storage required.

Data boundary

Meter economics, not content.

P402 records the economic facts of each AI call. Prompts, responses, files, documents, and source code stay inside the customer environment by default.

Not required
  • Prompts
  • Responses
  • Messages
  • Raw traces
  • Files
  • Documents
  • Source code
  • Transcripts
  • Chat history
What P402 records

Per-event economic facts.

tenant
Owning tenant for the AI call. Indexed on every event.
workflow_id
The workflow that produced the call. Filterable in the ledger.
customer_id
The end customer associated with the AI work, when applicable.
feature_id
The product feature that initiated the call.
model
The model that served the call.
provider
The upstream provider behind the model.
tokens
Input and output token counts for the call.
cost
Cost in USD, computed at the moment of the call.
budget result
Whether the call passed, capped, or was denied by budget.
policy result
Whether the call passed, was rewritten, or was denied by policy.
outcome status
Accepted, revised, escalated, or failed once reported.
receipt or evidence status
Whether a receipt or evidence bundle was issued for the call.
Privacy modes

Five modes. Metadata-only is the default. full_trace is opt-in and requires explicit tenant policy.

metadata_onlyDefault+
Best for: CFOs, regulated teams, healthcare, finance, legal, privacy-sensitive SaaS
P402 receives
  • request_id
  • tenant_id
  • api_key_id
  • department_id
  • employee_id
  • customer_id
  • feature_id
  • workflow_id
  • task_type
  • action_type
  • model
  • provider
  • input_tokens
  • output_tokens
  • cost_usd
  • latency_ms
  • cache_hit
  • budget_id
  • policy_id
  • governance_decision
  • deny_code
  • output_status
  • quality_score
  • evidence_status
P402 never receives
  • prompt text
  • response text
  • files
  • documents
  • chat history
  • PHI
  • PII
  • secrets
  • source code
Supports
  • Meter
  • Monitor
  • Control
  • budget enforcement
  • department, employee, feature, customer margin
  • forecasting
  • basic optimization
  • evidence exports
Limits
  • Semantic cache is off in P402 cloud for metadata_only
  • Limited prompt-level optimization
  • Limited context-bloat analysis
  • Limited duplicate-work detection
fingerprint_only+
Best for: Teams that want duplicate detection without exposing content
P402 receives
  • metadata above, plus:
  • HMAC prompt fingerprint, tenant-secret HMAC, not plain SHA-256
  • HMAC response fingerprint
  • token shape
  • optional prompt length bands
  • optional document hash
P402 never receives
  • raw prompt or response content
  • embeddings, treated as sensitive, opt-in only
Supports
  • Duplicate request detection
  • Retry loop detection
  • Repeated task detection
  • Cache opportunity estimates
  • Same-input cost analysis
Limits
  • Semantic cache is off in P402 cloud for fingerprint_only
  • No prompt-level rewrite suggestions
  • No semantic similarity grouping unless embeddings explicitly enabled
redacted_trace+
Best for: Developers and enterprises wanting stronger optimization with bounded exposure
P402 receives
  • redacted prompt sample
  • redacted response sample
  • trace summary
  • tool-call summary
  • retrieval summary
  • policy summary
P402 never receives
  • unredacted PII, PHI, secrets, API keys, emails, phone numbers, addresses, or custom-regex-matched content, redacted client-side before send
Supports
  • Context waste detection
  • Prompt compression recommendations
  • Retry-loop diagnosis
  • Tool-call waste analysis
  • Quality review
  • Better model selection by action
Limits
  • Redaction is the tenant responsibility before send
  • Opt-in per tenant, project, key, or workflow
  • Semantic cache is off unless the tenant explicitly opts in
private_gateway+
Best for: Large enterprise, regulated enterprise, high-value customers
P402 receives
  • economic events
  • recommendation summaries
  • savings proofs
  • policy results
  • evidence hashes
  • aggregate analytics
P402 never receives
  • raw prompts, planned to stay in customer VPC
  • raw responses, planned to stay in customer VPC
  • embeddings unless explicitly exported
Supports
  • Customer-controlled routing path
  • Deeper optimization scope
  • Tenant-scoped trace inspection
  • Tenant-scoped redaction
  • Tenant-scoped policy enforcement
  • Enterprise evidence export
Limits
  • Enterprise deployment path, availability subject to agreement and deployment scope
  • Operational responsibilities defined per engagement
  • No P402-cloud semantic cache for private_gateway
full_trace+
Best for: Small developer teams wanting maximum debugging and optimization
P402 receives
  • prompt
  • response
  • tool calls
  • trace
  • retrieval context
  • output status
  • quality score
P402 never receives
  • data the customer does not send
Supports
  • Deepest optimization
  • Full trace replay
  • Per-request quality review
Limits
  • Never the default, must be explicitly enabled
  • Short retention required
  • Semantic cache is off unless the tenant explicitly opts in
  • Project-level enablement, planned for enterprise deployment
  • Role-gated access, planned for enterprise deployment
  • Audit log of access, planned for enterprise deployment
Security posture
Server-side tenant resolution
Tenant identity is resolved on the server. The client never decides which tenant a call belongs to.
API key scoping
Keys are returned exactly once at creation. Only the SHA-256 hash is stored. P402 cannot recover a lost key.
Audit logs
Sensitive operations write structured audit records. Findings use INSERT ... ON CONFLICT for idempotency.
No client-trusted plan state
Plan and entitlement state is read on the server. The client cannot promote a session.
No prompt storage by default
Metadata-only is the default mode. Prompt and response content stay inside the customer environment.
No Stripe secrets in the client bundle
Payment provider secrets remain server-side. The client bundle ships no provider keys.
Webhook signature verification where billing applies
Billing webhooks read the raw body and verify the provider signature before any state change.
Least-privilege defaults
New keys, sessions, and tenants start with the smallest scope that allows the documented use.
Verifiable on-chain

Settlement and identity contracts on Base Mainnet, chain ID 8453. Verify independently on Basescan.

USDC
Base Mainnet
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

ERC-20 asset used for settlements. Circle-issued.

P402 Treasury
Base Mainnet
0xFa772434DCe6ED78831EbC9eeAcbDF42E2A031a6

Receives USDC from settled payments. Platform fee destination.

P402Settlement
Base Mainnet
0xd03c7ab9a84d86dbc171367168317d6ebe408601

Marketplace settlement contract. Applies a platform fee on settlement.

SubscriptionFacilitator
Base Mainnet
0xc64747651e977464af5bce98895ca6018a3e26d7

Recurring subscription billing via EIP-2612 permit. Month 1 sets allowance, months 2+ draw without new signatures.

ERC-8004 Identity
Base Mainnet
0x8004A169FB4a3325136EB29fA0ceB6D2e539a432

On-chain agent identity registration and DID resolution.

ERC-8004 Reputation
Base Mainnet
0x8004BAa17C55a88189AE136b182e5fdA19dE9b63

On-chain agent reputation scoring. Read by the routing engine for trust-weighted decisions.

Custody model

P402 never holds user funds. The facilitator executes signed authorizations, it does not custody assets.

User and payer

Signs the EIP-3009 authorization. Controls validAfter, validBefore, nonce, and value. The user never submits a transaction, the facilitator does.

Risk boundary

User sets authorization bounds. Once signed, the facilitator can execute within those bounds before validBefore.

P402 Facilitator

Hot wallet that executes transferWithAuthorization on USDC. Pays gas on behalf of the user. Does not hold user funds.

Risk boundary

If compromised, could execute valid but not-yet-settled authorizations. Mitigated by short validBefore windows and replay protection.

Treasury

Receives settled USDC. Read-only from the protocol perspective, receives only, never sends.

Risk boundary

Separate from the facilitator wallet. Compromise of the facilitator does not affect treasury funds.

Resource server

Defines paymentRequirements: amount, payTo, asset, resource URL. Calls verify then settle through the P402 facilitator API.

Risk boundary

Must validate the verify response before serving content. Failure to check valid: true results in serving without confirmed payment.

Procurement

Enterprise review paths.

  • Security review path
    Walkthrough of the data boundary, privacy modes, on-chain contracts, and custody model.
    available on request
  • DPA path
    Data processing agreement covering subprocessor list, retention, and tenant-level deletion.
    available on request
  • BAA path
    Business associate agreement scoped to metadata-only or private-gateway mode.
    available after security and contracting review
  • MSA path
    Master services agreement for enterprise deployment, including support and SLA terms.
    available for enterprise
  • Audit export path
    Evidence bundles, finance reports, and per-event proof exports for audit and dispute review.
    available
  • Data retention review
    Review and configuration of retention windows for economic events and any opt-in trace data.
    available
  • Private deployment review
    Customer-hosted inference path. Economic events recorded over a signed channel.
    available for regulated buyers
Request security review
Evidence

Proof without prompt storage.

  • Receipts
    x402 settlement records on Base. See /receipts for the surface.
  • Outcome records
    Accepted, revised, escalated, or failed status tied to the event. See /prove for the surface.
  • Audit exports
    Structured exports of events and decisions for finance, audit, and legal review.
  • Proof bundles
    Per-event evidence bundle linking attribution, cost, policy, and settlement when applicable.

Evidence does not require prompt storage.

Billing and trust boundary

Billing state is separate from prompt content.

Billing state and plan state are stored separately from any AI event content. Payment providers are used only for subscription and invoice operations. Build checkout is controlled by the billing rollout. Enterprise billing remains sales-assisted.

FAQ
Do you store prompts?+

No prompt storage is required. Metadata-only mode is the default.

Do you store responses?+

No response storage is required. Metadata-only mode is the default.

Can we use metadata-only mode?+

Yes. It is the default. The economic event lands in the ledger without prompt or response content.

Can we complete a security review?+

Yes. Request a security review through the access route. DPA path is available on request.

Is settlement required?+

No. Meter works without settlement. Receipts are added when AI work is payable.

Is P402 SOC 2 certified?+

SOC 2 is a roadmap item until an audit report exists. P402 does not claim certification before audit.

Does P402 support HIPAA workloads?+

BAA path is available after security and contracting review. Healthcare buyers should request the path before production use.

Can we use P402 in healthcare or finance?+

Yes. Use metadata-only or private-gateway mode. Request the regulated-buyer review path.

Can we export audit evidence?+

Yes. Evidence bundles, finance reports, and per-event proof are exportable. See /prove for the surface.

Get started

Run the review. Read the docs.

Request security reviewRead docs