TokenOps MVP
13 of 13 runtime proof records persisted.
The public site explains the company and operating tools. The protected OS is where Wever Labs runs work orders, agents, outputs, PacketOps, DistributionOps, and delivery packages.
Use this private agent operator home to load OS state, monitor Scout, review rail commerce, dispatch runtime, manage credits, and keep Agent test Workspace proof records current.
Use this page as the bookmarked agent operator doorway. Public agents and agent principals use the rails. Agent verification, proof inspection, activation checks, and provider preparation stay here.
13 of 13 runtime proof records persisted.
13 of 13 runtime proof records persisted.
13 of 13 runtime proof records persisted.
Runtime proof surface and run endpoint added.
Runtime proof surface and run endpoint added.
Review MVP pass state, proof surface links, and launch lane status for trusted agent test operation.
Use these when you need the actual persisted proof trail for each MVP tool.
Proof trail, receipts, callback record, ledger reference, and attestation.
Open TokenOps proof surface →Reconciliation result package, receipts, callback record, ledger reference, and attestation.
Open FinanceOps proof surface →Interconnection packet readiness package, receipts, callback record, ledger reference, and attestation.
Open EnergyOps proof surface →Packet readiness alignment, run endpoint, result contract, receipt, callback, ledger reference, and attestation.
Open PacketOps proof surface →Distribution readiness alignment, run endpoint, result contract, receipt, callback, ledger reference, and attestation.
Open DistributionOps proof surface →These links keep provider-connected preparation separate from public request intake.
Check public launch, internal runtime agent test, rail checkout requests, and provider readiness state.
Check activation status →Record sandbox state, credit readiness, settlement receipt posture, callback failure handling, and agent operator release gate.
Open provider preparation →Keep provider connection, release, and money-adjacent steps gated by the agent operator.
Open provider binding →Run the selected rail after product selection, payment reference, and agent operator route decision are ready.
Open runtime dispatch →Monitor target scoring, published rail signals, message templates, and signal feed status.
Open Scout signals →Review Scout target records, fit scores, recommended rails, workspace candidates, and target state.
Open Scout console →Seed real agent directories, MCP directories, A2A ecosystems, marketplaces, and workflow platforms.
Open target pack →Dashboard status is a summary. Proof surfaces remain the source of record. Provider-connected movement remains gated by agent operator agent verification.
Public manifests expose the rails. The protected OS binds them to runtime state: contracts, credits, settlement receipts, lifecycle records, task ledgers, result contracts, usage receipts, callbacks, exceptions, replay packages, and console snapshots.
Review rail product requests, checkout confirmations, invoices, purchase orders, and agent credits from one agent operator doorway.
Agent-scoped shortcuts for the product-to-proof loop.
Review Stripe sandbox webhook status and payment reference events.
Open webhook verification →Bind organization, rail product, success criteria, checkout, payment reference, and proof IDs.
Open agent test workspace →Record agent-facing targets, recommend a rail, score fit, and draft discovery submission for agent verification.
Open Scout →Review Scout targets, change decision state, create workspace records, and keep the discovery lane moving.
Open Scout Console →