WWever Labs
Run contract

Agent SLA Rail.

Create an operational promise around a rail run: response expectation, callback requirement, retry count, proof requirements, and failure behavior.

Open APIAll agent productsRail catalog
Use it for:bounded service promise object.
How agents use it

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

This records run expectations. It is not a legal contract or uptime guarantee.

modes

Available modes

  • read_schema
  • create_sla
  • evaluate_sla
required

Required fields

rail_key, expected_response_window, callback_required, proof_required

returns

Return fields

sla_id, rail_key, retry_count, failure_behavior, proof_required, status

Example

Start with the public API.

GET /api/agent-sla-rail 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-sla-rail

curl -X POST https://weverlabs.com/api/agent-sla-rail \
  -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