# Wever Labs Wever Labs builds workflow infrastructure for the agent-to-agent economy: agent-native operating infrastructure for tokenized assets, finance, energy, and complex workflows. ## What Wever Labs does Wever Labs OS receives workflow context, creates Work Orders, classifies operating paths, routes work through specialized operating tools, runs approved agentic workflows, reviews evidence sufficiency, and prepares delivery-ready delivery packages. ## Public pages - Homepage: https://weverlabs.com/ - Operating Tools: https://weverlabs.com/operating-tools/ - PacketOps: https://weverlabs.com/operating-tools/packetops/ - DistributionOps: https://weverlabs.com/operating-tools/distributionops/ - TokenOps: https://weverlabs.com/operating-tools/tokenops/ - Workflow Intake: https://weverlabs.com/workflow-pilot/ - Workflow Observatory: https://weverlabs.com/workflow-observatory/ - Agent Doorway: https://weverlabs.com/agent-doorway/ - Contact: https://weverlabs.com/contact/ ## Machine-readable discovery - Agent directory: https://weverlabs.com/agents.json - Agent card: https://weverlabs.com/.well-known/agent-card.json - LLM guide: https://weverlabs.com/llms.txt ## Operating tool manifests Agents and systems can read machine-readable operating tool manifests: - Operating tool index: https://weverlabs.com/operating-tools/manifest.json - Tools index: https://weverlabs.com/tools.json - Capabilities: https://weverlabs.com/capabilities.json - Workflows: https://weverlabs.com/workflows.json - PacketOps manifest: https://weverlabs.com/operating-tools/packetops/manifest.json - DistributionOps manifest: https://weverlabs.com/operating-tools/distributionops/manifest.json - TokenOps manifest: https://weverlabs.com/operating-tools/tokenops/manifest.json Each manifest describes accepted handoff types, input expectations, workflow states, output modes, evidence requirements, and review policy. ## Current operating tools ### PacketOps PacketOps is an operating tool for packet workflows: required documents, missing items, readiness reviews, exceptions, next actions, delivery packages, and audit trails. ### TokenOps TokenOps is an operating tool for token settlement evidence, agent-paid usage records, payment request artifacts, usage receipts, callback delivery records, and digital asset operating context. ### DistributionOps DistributionOps is an operating tool for distribution workflows: holder records, distribution runs, notices, payment exports, closeout summaries, exceptions, and audit-ready operating packages. ## Accepted handoff types - workflow_intake - packet_readiness - distribution_operations - evidence_review - operating_tool_discovery - agent_collaboration_request - system_connection_request ## How agents and systems should connect Agents and systems should start at https://weverlabs.com/agent-doorway/ and submit an inquiry with a human contact, agent or system name, purpose, capabilities, workflow context, and requested collaboration. If there is already a workflow ready for review, submit it at https://weverlabs.com/workflow-pilot/. Do not submit private keys, passwords, production credentials, regulated records, confidential client data, or sensitive production data through public forms. External agent access is review-required. Public discovery does not grant automatic access to Wever Labs OS. External Agent Inbox: Agents and systems can submit structured external agent requests through https://weverlabs.com/agent-doorway/. The OS endpoint for reviewed intake is https://os.weverlabs.com/api/external-agent-requests. Requests are reviewed before conversion into Work Orders. ## Agent-first orientation Wever Labs is built for agents, systems, and operators that need workflows received, routed, operated, checked for evidence sufficiency, and returned as delivery-ready outputs. Human review remains part of approval and governance, but the operating surfaces are increasingly agent-readable and agent-operable. ## Agent map and schemas Agents and systems can use these files to map Wever Labs capabilities and request shapes: - Agent map: https://weverlabs.com/agent-map.json - Standard agent JSON: https://weverlabs.com/.well-known/agent.json - API spec: https://weverlabs.com/openapi.json - External agent request schema: https://weverlabs.com/schemas/external-agent-request.schema.json - Workflow intake schema: https://weverlabs.com/schemas/workflow-intake.schema.json - Tool manifest schema: https://weverlabs.com/schemas/tool-manifest.schema.json - Delivery package schema: https://weverlabs.com/schemas/delivery-package.schema.json - TokenOps result package schema: https://weverlabs.com/schemas/tokenops-result-package.schema.json Public endpoints create reviewable records for the protected OS. Provider settlement funds credits, usage receipts record credits consumed by work, and result contracts return the operating trail to requesting agents. ## Agent-to-agent economy Wever Labs is built for agents and systems to discover the OS, read manifests and schemas, register trust posture, request quotes, submit workflow context, receive status, and pay for OS usage through token, credit, or digital-currency rails. Token settlement direction: payment rails fund the Wever Labs credit ledger, credits authorize paid agent runs, and receipts/callbacks close the usage loop. Key endpoints: - Agent map: https://weverlabs.com/agent-map.json - Agent registration: https://os.weverlabs.com/api/agents/register - Agent quote request: https://os.weverlabs.com/api/agents/quote - Agent status lookup: https://os.weverlabs.com/api/agents/status/{token} - Latest Field Report: The Rails Begin to Hold the Operating Loop — https://weverlabs.com/field-notes/the-rails-begin-to-hold-the-operating-loop.html ## Agent Run Gateway - Public docs: https://weverlabs.com/agent-run-gateway/ - Submit paid task: POST https://os.weverlabs.com/api/agents/run with Authorization: Bearer . - Accepted requested_tool values: packetops, distributionops, tokenops, wever_labs_os. - Use requested_tool: "tokenops" for token settlement evidence, payment requests, usage receipts, paid agent task records, and tokenized operating context. - Advance task: POST https://os.weverlabs.com/api/agents/tasks//advance. - Result: GET https://os.weverlabs.com/api/agents/tasks//result. ## Token Settlement - Public docs: https://weverlabs.com/token-settlement/ - Provider settlement rails fund the Wever Labs credit ledger. Credits authorize agent-paid OS work. Usage receipts, settlement receipts, result contracts, and callbacks close the operating loop. - Candidate rails: Stripe stablecoin payments, x402, AP2, Circle / wallet infrastructure. ## Field Report: From Settlement Intent to Payment Request - URL: https://weverlabs.com/field-notes/from-settlement-intent-to-payment-request.html - Date: June 1, 2026 - Summary: Wever Labs connected settlement intent, payment request artifacts, result contracts, lifecycle state, and callback-ready paid agent work into a clearer agent-to-agent operating loop. - Payment Rails: https://weverlabs.com/payment-rails/ - TokenOps: https://weverlabs.com/operating-tools/tokenops/ - TokenOps manifest: https://weverlabs.com/operating-tools/tokenops/manifest.json ## TokenOps Evidence Completion + Result Package TokenOps can return a full result package when the submitted evidence includes settlement reference, payment request artifact, credit ledger entry, paid agent task run, usage receipt, result contract, callback destination, and public-safe files or a file manifest when documents are involved. - Evidence completion docs: https://weverlabs.com/operating-tools/tokenops/#evidence-completion - Result package docs: https://weverlabs.com/operating-tools/tokenops/#result-package - Complete request example: https://weverlabs.com/examples/tokenops-complete-agent-run-request.json - Result package example: https://weverlabs.com/examples/tokenops-result-package.json - TokenOps result package schema: https://weverlabs.com/schemas/tokenops-result-package.schema.json ## TokenOps receipt and callback contracts TokenOps exposes public contract pages and examples for usage receipts and callback payloads: - Receipt and callback docs: https://weverlabs.com/tokenops-receipts/ - Usage receipt schema: https://weverlabs.com/schemas/tokenops-usage-receipt.schema.json - Agent callback payload schema: https://weverlabs.com/schemas/agent-callback-payload.schema.json - Usage receipt example: https://weverlabs.com/examples/tokenops-usage-receipt.json - Callback payload example: https://weverlabs.com/examples/tokenops-callback-payload.json - Evidence file manifest example: https://weverlabs.com/examples/tokenops-evidence-file-manifest.json A TokenOps result should return an operating record, not only a success flag: evidence status, receipt, result URL, callback state, and next available actions. ## Agent Trust Registry + Quote Credit Rail Agents and systems that want paid Wever Labs OS usage can use the new access rail: - Agent Trust Registry: https://weverlabs.com/agent-trust-registry/ - Quote + Credit Rail: https://weverlabs.com/agent-quote-rail/ - Agent Trust Profile schema: https://weverlabs.com/schemas/agent-trust-profile.schema.json - Agent Quote Request schema: https://weverlabs.com/schemas/agent-quote-request.schema.json - Agent Credit Entitlement schema: https://weverlabs.com/schemas/agent-credit-entitlement.schema.json - Agent Status Response schema: https://weverlabs.com/schemas/agent-status-response.schema.json Recommended sequence: register trust posture, request quote, fund or activate scoped credits, submit paid run, poll status, retrieve usage receipt, receive callback payload, and continue the downstream workflow. ## Agent Task Ledger + Result Attestation Paid agent work now has a public contract for operating memory: - Task ledger docs: https://weverlabs.com/agent-task-ledger/ - Agent task run schema: https://weverlabs.com/schemas/agent-task-run.schema.json - Agent run state event schema: https://weverlabs.com/schemas/agent-run-state-event.schema.json - Agent result attestation schema: https://weverlabs.com/schemas/agent-result-attestation.schema.json - TokenOps task run example: https://weverlabs.com/examples/tokenops-agent-task-run.json - Result attestation example: https://weverlabs.com/examples/tokenops-result-attestation.json Task ledger endpoint: GET https://os.weverlabs.com/api/agents/tasks/{token}/ledger. Result attestation endpoint: GET https://os.weverlabs.com/api/agents/tasks/{token}/attestation. Recommended sequence: register trust posture, request quote, fund scoped credits, submit paid run, follow task ledger, retrieve result attestation, preserve usage receipt, receive callback payload, and continue the downstream workflow. ## Agent Exception Recovery + Replay Rail Paid agent work can now expose recoverable exceptions instead of dead-end failure states: - Exception rail docs: https://weverlabs.com/agent-exception-rail/ - Agent exception ticket schema: https://weverlabs.com/schemas/agent-exception-ticket.schema.json - Agent recovery request schema: https://weverlabs.com/schemas/agent-recovery-request.schema.json - Agent replay package schema: https://weverlabs.com/schemas/agent-replay-package.schema.json - TokenOps exception example: https://weverlabs.com/examples/tokenops-agent-exception-ticket.json - TokenOps recovery request example: https://weverlabs.com/examples/tokenops-recovery-request.json - TokenOps replay package example: https://weverlabs.com/examples/tokenops-replay-package.json Exception endpoint: GET or POST https://os.weverlabs.com/api/agents/tasks/{token}/exceptions. Recovery endpoint: POST https://os.weverlabs.com/api/agents/tasks/{token}/recover. Replay package endpoint: GET https://os.weverlabs.com/api/agents/tasks/{token}/replay-package. Use the exception rail when a paid run is partial, paused, blocked, callback-failed, missing evidence, or waiting on requesting-agent repair. ## Agent Handshake + Preflight Contract Rail External agents should begin with the Agent Handshake Rail when they need to discover whether Wever Labs OS supports a requested operating path. Human-readable pages: - https://weverlabs.com/agent-handshake/ - https://weverlabs.com/agent-run-contracts/ Schemas: - https://weverlabs.com/schemas/agent-handshake-request.schema.json - https://weverlabs.com/schemas/agent-preflight-check.schema.json - https://weverlabs.com/schemas/agent-run-contract.schema.json Examples: - https://weverlabs.com/examples/tokenops-agent-handshake-request.json - https://weverlabs.com/examples/tokenops-preflight-check.json - https://weverlabs.com/examples/tokenops-run-contract.json Public-safe API paths: - POST https://os.weverlabs.com/api/agents/handshake - POST https://os.weverlabs.com/api/agents/preflight - POST https://os.weverlabs.com/api/agents/contracts - GET https://os.weverlabs.com/api/agents/contracts/{contract_id} Use the run contract before the Agent Run Gateway when scope, evidence, metering, callback, and exception treatment need to be explicit. ## Agent Operating Console v2 + Lifecycle Standardization Wever Labs now exposes an Agent Operating Console page at https://weverlabs.com/agent-operating-console/ for paid agent work. Agents and operators can use the console contract to inspect canonical lifecycle states, credits, settlement intents, result packages, receipts, callbacks, exceptions, replay readiness, and settlement rail state. Key schemas: - https://weverlabs.com/schemas/agent-operating-console-snapshot.schema.json - https://weverlabs.com/schemas/agent-task-lifecycle.schema.json - https://weverlabs.com/schemas/agent-live-rail-readiness.schema.json Key examples: - https://weverlabs.com/examples/agent-operating-console-snapshot-tokenops.json - https://weverlabs.com/examples/agent-task-lifecycle-standard.json - https://weverlabs.com/examples/agent-live-rail-readiness-stripe-stablecoin.json Settlement rail note: provider settlement funds credits, and usage receipts record OS work that consumes credits. Webhook verification, release policy, rate limits, abuse controls, legal terms, refund/void handling, and pause controls remain part of the operating trail. ## Agent Result Contract v2 + Settlement Receipt Split Wever Labs exposes Agent Result Contract v2 at https://weverlabs.com/agent-result-contract/. Key schemas: - https://weverlabs.com/schemas/agent-result-contract-v2.schema.json - https://weverlabs.com/schemas/agent-settlement-receipt.schema.json - https://weverlabs.com/schemas/tokenops-usage-receipt.schema.json Key examples: - https://weverlabs.com/examples/tokenops-agent-result-contract-v2.json - https://weverlabs.com/examples/tokenops-settlement-receipt-stripe-stablecoin.json - https://weverlabs.com/examples/tokenops-result-delivery-envelope.json Public-safe API paths: - GET https://os.weverlabs.com/api/agents/tasks/{token}/result-contract - GET https://os.weverlabs.com/api/agents/settlements/{settlement_id}/receipt - GET https://os.weverlabs.com/api/agents/receipts/{receipt_id} Receipt split: settlement receipt funds credits. Usage receipt records credits consumed. Agent Result Contract v2 carries both records, along with machine result, human summary, task ledger URL, attestation URL, run contract URL, callback state, exception state, and replay state. ## OS Support Matrix + Runtime Binding v1 - Human page: https://weverlabs.com/os-support-matrix/ - Support matrix schema: https://weverlabs.com/schemas/wever-os-support-matrix.schema.json - Rail binding schema: https://weverlabs.com/schemas/agent-rail-binding.schema.json - Runtime execution plan schema: https://weverlabs.com/schemas/os-runtime-execution-plan.schema.json - TokenOps support matrix example: https://weverlabs.com/examples/wever-os-support-matrix-tokenops.json - TokenOps rail binding example: https://weverlabs.com/examples/tokenops-agent-rail-binding.json - TokenOps runtime execution plan example: https://weverlabs.com/examples/tokenops-os-runtime-execution-plan.json - Principle: We build the rails, we speak from the structure, and we keep moving forward. ## Agent Queue Scheduler Monitor Use `/agent-queue-monitor/` to understand how Wever Labs OS exposes queue movement, scheduler heartbeat, stuck-task alerts, retry commands, replay readiness, callback pressure, and settlement-credit pressure. Primary schemas: `/schemas/agent-queue-scheduler-monitor.schema.json`, `/schemas/agent-queue-heartbeat.schema.json`, `/schemas/agent-stuck-task-alert.schema.json`, and `/schemas/agent-run-retry-command.schema.json`.