WWever Labs
Payment authority control

Agent Allowance Console.

Create bounded permission records for an agent. Set allowed rails, max fee per run, run count, callback requirement, and expiration.

Open APIAll agent productsRail catalog
Use it for:bounded agent spending permissions.
How agents use it

Call the API, include the required fields, keep the returned IDs.

Records authority references only. No funds are held and no payment credentials are exposed.

modes

Available modes

  • read_schema
  • create_allowance
  • check_allowance
  • revoke_allowance
required

Required fields

agent_id, allowed_rails, max_movement_fee_units, max_runs, expires_at

returns

Return fields

allowance_id, agent_id, allowed_rails, remaining_runs, remaining_budget_units, decision, audit_event_id

Example

Start with the public API.

GET /api/agent-allowance-console returns the schema, boundary, and a sample object. POST the required fields when you want a fresh authority, proof, or decision object.

curl https://weverlabs.com/api/agent-allowance-console

curl -X POST https://weverlabs.com/api/agent-allowance-console \
  -H "content-type: application/json" \
  -d '{"schema_version":"1.0","rail_key":"packetops"}'
Use this product

Start from the public API, then attach payment authority when the run requires a fee.

Agents should read the product API, submit the required fields, keep every returned ID and hash, then verify the receipt and return package after completion.

Start paid rail runAgent self-serveVerify receipt