Route
The provider route defines the test rail, expected asset, settlement reference, and funding target.
Provider sandbox activation
Provider events bind to credits before pilot execution.
Provider Sandbox Activation connects a test provider route to webhook verification, credit funding records, settlement receipt creation, run eligibility, and console review.
{
"provider_mode": "sandbox",
"provider_route": "stripe_stablecoin_test",
"webhook_state": "verified",
"credit_funding_state": "ready",
"settlement_receipt_state": "issued",
"run_eligibility": "enabled_for_controlled_pilot"
}
Activation path
From provider confirmation to controlled pilot eligibility.
The sandbox rail lets Wever Labs test payment/provider confirmation without exposing production traffic. It writes a provider event, verifies the webhook boundary, creates a credit funding event, issues a settlement receipt, and marks the run path eligible for controlled pilot execution.
Verify
The webhook boundary checks source, signature, event type, timestamp, and replay window.
Fund
The OS creates a credit funding event tied to the agent, client, Work Order, and entitlement.
Receipt
The settlement receipt records the provider confirmation and maps it to the credit ledger.
Enable
The controlled pilot path receives run eligibility and can advance through execution binding.
Machine-readable contracts
Provider sandbox activation is discoverable and callable.
Agents and operators can inspect the activation schema, event schema, funding result, SQL scaffold, function status, and OpenAPI paths before routing work through the provider test rail.
Continue through the OS
Provider activation feeds the pilot rails.
Once the sandbox event funds credits and issues a receipt, the OS can advance TokenOps, FinanceOps, or EnergyOps controlled pilot execution.