WEVER LABS / TRUST CENTER

Trust Center

What the Wever Labs trust stack checks, how funds are handled, and where the guarantees stop.

WHAT THE TRUST STACK GUARANTEES

Checks with stated limits.

Each component checks a specific part of the record. The scope of a receipt matters as much as its signature.

01

Receipt Passport

wever_receipt-passport

Signed verification receipts

Issues and verifies signed receipts from supported retained Wever records.

Limit. A valid signature binds the recorded evidence and result. It does not prove arbitrary outside claims or fulfillment.

Read the public contract ↗
02

Proof Inbox

wever_proof-inbox

Proof capture

Captures and retrieves wallet-scoped proof. Supported signed tokens are checked against retained records.

Limit. Arbitrary submitted evidence remains labeled unverified. Capturing a claim does not establish that it is true.

Read the public contract ↗
03

Agent Trust Scorecard

wever_agent-trust-scorecard

Trust scoring

Scores supported retained evidence and labels unknowns, with the basis available for review.

Limit. The score is limited to the evidence checked. It is not a universal reputation, identity or future-performance guarantee.

Read the public contract ↗
04

Agent-to-Agent Handoff Pack

wever_agent-to-agent-handoff-pack

Handoff integrity

Signs a wallet-bound task, state and declared permissions for a named recipient so the handoff can be checked for integrity.

Limit. The recipient must enforce authority independently. A pack grants no resource access, payment authority or execution capability, and is not automatically delivered.

Read the public contract ↗
05

AP2 Mandate Gateway

wever_ap2-mandate-gateway

Signed, allowlisted, replay-resistant mandates

Verifies signed payment mandates against configured issuer and merchant allowlists, holder-wallet binding, checkout scope, nonce and expiry. Durable single-use checks resist replay and produce a signed historical verification receipt.

Limit. This is a bounded AP2 verification profile. Verification does not execute a purchase, move purchase funds or grant spending authority. An AP2 receipt is not an escrow release mandate.

Read the public contract ↗
06

Escrow-lite

wever_agent-escrow-lite

Conditional release and expiry refund

Releases funds only to the fixed payee after validating the signed release mandate required by the escrow policy. On expiry, refunds go only to the original payer.

Limit. This is managed custody. Refund and settlement completion depend on chain confirmation, provider availability and bounded recovery. It is not a trustless smart contract or an instant-refund guarantee.

Read the public contract ↗

SECURITY PRACTICES

How we operate.

Dedicated settlement wallet

Wever Labs uses a dedicated settlement wallet on Ledger. The operator sweeps funds manually.

Business funds stay separate

Business revenue is kept separate from personal funds.

Escrow custody is separate

Managed escrow uses a separate service-held wallet. The Ledger settlement wallet is neither the escrow funding destination nor the escrow signer. No hardware-backed escrow key claim is made.

Company traffic is labeled

Company-authored traffic is labeled and never counted as adoption. Synthetic acceptance runs remain tests, not outside customers or revenue.

HONEST LIMITS

What we do not claim.

Verified usage and attribution ↗

No provider affiliation

Wever Labs is not integrated with or endorsed by any exchange, wallet provider or card network.

Consumer trust remains the bottleneck

Technical checks establish only their stated scope. They do not establish consumer confidence or consent beyond the authorization actually verified.

69% of consumers are interested in delegating tasks such as subscription management, grocery shopping and meal planning to agentic AI. (PYMNTS, January 2026)

Only 23% of U.S. consumers trust generative AI to handle payments on their behalf. (Visa, September 2026)

Claims follow verified usage

We make no adoption or revenue claims beyond verified data on /usage/. That page explains coverage and attribution limits; missing or zero counts are not proof of no activity.

PUBLIC RECORD

Service status and incident history

See /status/ for observed service health and the recorded incident history. Its monitoring scope and history limits are stated there.

View status and incidents ↗

Updated October 6, 2026. Machine-readable summary ↗