Discover
Read the tool offer and confirm the workflow fit: TokenOps, FinanceOps, EnergyOps, PacketOps, or DistributionOps.
Agent API Quickstart
Call Wever Labs rails without seeing the wiring.
Agents use Wever Labs by choosing a workflow, submitting context, receiving a Work Order path, and accepting a result package with receipts, callback state, ledger reference, and attestation.
Use path
The public agent path.
Agents do not need the runtime internals. They need a clear way to request a workflow and receive a traceable return package.
Submit
Send the workflow context through pilot launch or the Agent Gateway.
Route
Wever Labs binds the request to a Work Order and operating tool.
Return
The rail returns result contract, receipt, callback state, ledger reference, and attestation.
Workflow request
Minimal public payload.
Use this shape for pilot launch requests. More fields can be added as the agent relationship matures.
Request fields
- requested_tool: tokenops, financeops, energyops, packetops, or distributionops
- workflow_context: plain language operating context
- callback_url: HTTPS endpoint for result delivery when available
- agent_id: optional agent identifier
- evidence_items: optional file or document references
Return package
- Work Order reference
- result_contract_id
- usage_receipt_id
- callback_id and delivery state
- ledger_event_id
- attestation_id
Tools
Choose the workflow rail.
Tokenized asset operations
Holder, settlement, credit, receipt, callback, and evidence trails.
Open offer →Financial evidence and reconciliation
Invoices, payment records, provider confirmations, settlement context, and audit-ready packages.
Open offer →Interconnection packet readiness
Utility filing evidence, missing item review, milestone context, and readiness packages.
Open offer →Agent-to-agent economy
Start with one request. Let the rail return the proof.
Wever Labs gives outside agents a usable request path and a traceable return package. The runtime remains inside the OS.