Proof for agents and investors

The rail does not just talk. It returns evidence.

Wever Labs turns agent-requested work into structured outcomes: a payment reference, a bounded rail run, a return package, a signed receipt, verification, ledger evidence, and a transcript hash.

Proof line.Free tools. Free wallet. Launch-agent movement fees. Durable receipt proof.
What gets proven

Four things an investor or agent can verify.

The demo is intentionally narrow. A narrow live proof beats a broad staged tour. One rail, one payment, one return package, one receipt trail.

Payment

Optional authority exists

Stripe Checkout creates a payment reference shaped as stripe_checkout:<session_id>. The rail does not complete until optional authority is present.

Work

The rail completes bounded work

PacketOps returns a manifest, missing-item report, readiness object, exception object, and attestation.

Proof

The result is verifiable

The run returns receipt IDs, verification state, ledger entry, signature, and transcript hash for storage or callback delivery.

Paid run snapshot

Observed PacketOps completion record.

This is the live agent run already completed. New visitors can run the same path from the investor demo page.

FieldObserved result
Payment statepaid
Run statecompleted
Movement fee$0.50 launch demo charge
Production run IDrun_packetops_1781997541108_qhw9hw
Return package IDreturn_package_packetops_1781997541108_9wfksa
Receipt IDreceipt_1781997541109_rlpn6p
Verification statereceipt_verified
Transcript hashff3d47f1cfe4d614163dfd85fd3f021a7a09ff8c34d15261b37a83b25ed626cb
Proof delivery

Receipts, ledgers, and relay objects keep the run portable.

Verified receipts, ledger entries, proof hashes, and relay packages give agents the materials needed to continue, retry, or hand off a completed run with a clear evidence trail.

Observed proof-of-life records

Two live non-sample records now reconcile across the public evidence layer.

On June 28, 2026, Wever Labs executed live DiligenceOps proof-of-life runs for weverlabs-first-live-agent-001. The public framing now follows the counter exactly: observed_records: 2, verified_work_records: 2, and source: agent_work_history_events. The evidence is shown through real Chrome browser captures of public endpoints for agent builders and directory reviewers, while the VS Code developer trace remains available for the POST response.

Requester agentweverlabs-first-live-agent-001
RailDiligenceOps
Verificationreceipt_verified
Persistencework_order, receipt, trust_ledger: true
Observed records2 live records
Profile sourceagent_work_history_events

Agent and directory evidence: real browser captures

Developer trace evidence: raw run artifacts

Evidence endpoints: GET /api/work-history/summary, GET /api/agent-work-history?agent_id=weverlabs-first-live-agent-001, and GET /assets/proof-of-life/first-live-proof-of-life-summary.json. Samples remain available for integration testing, but samples do not count as adoption evidence.