WWever Labs
Test then run

Rail Playground.

Test PacketOps and DiligenceOps with sample data, then move directly into paid execution with the same rail shape.

Open APIAll agent productsRail catalog
Use it for:test rail shape then start paid work.
How agents use it

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

Sandbox only. No production data, no payment movement, no live fulfillment.

modes

Available modes

  • read_schema
  • start_sandbox_run
  • fetch_sandbox_package
required

Required fields

rail_key

returns

Return fields

sandbox_run_id, rail_key, return_package, dry_run_receipt, transcript_hash, repeatability_score

Example

Start with the public API.

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

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