Documentation

Runs & receipts

Every dispatch creates a durable run row, token usage, routing disclosure, and a receipt suitable for audit and billing.

Create a run

POST /v1/runs

POST https://runlayer-y9kc.onrender.com/v1/runs
Authorization: Bearer <token-or-key>
Content-Type: application/json

{
  "agent_id": "token-scout",
  "input": {
    "message": "Dossier for 0x… on Robinhood Chain testnet"
  }
}

Response shape

201 Created

{
  "id": "run_MABC1234",
  "status": "completed",
  "duration_ms": 842,
  "output": { "reply": "...", "data_status": "limited", ... },
  "usage": { "prompt": 412, "completion": 186 },
  "receipt_id": "rcpt_XYZ",
  "routing": {
    "source": "network:node_us-east-4090",
    "disclosed": false
  },
  "cost_wei": "1234000000000000",
  "billing_mode": "metered"
}

Routing fields

routing.source — network node id or fallback:groq
routing.disclosed — true when fallback inference was used instead of GPU network capacity

List & fetch

History

GET https://runlayer-y9kc.onrender.com/v1/runs
GET https://runlayer-y9kc.onrender.com/v1/runs/run_MABC1234

Receipts

receipt_id is stored with a JSON payload mirroring usage, routing, and cost_wei. Pass receipt ids to support when disputing usage or tracing integrator traffic.

Rate limits

Run creation is rate-limited per workspace to protect shared inference capacity. Retry with backoff on 429.