From your codeNo repository

Run an agent per customer task

A typed answer, by webhook

Your backend starts one session per customer request with an org key, and Rush posts the result to your webhook when the turn ends.

Best for

Uses

From your code

POST /o/{org}/sessions

{
  "harness": "claude",
  "input": "Draft a reply to this support ticket from the attached thread. Keep it under 150 words."
}

Fig. The request. Field names are the API's; the values are an example.

Watch it work, then read what comes back

GET /o/{org}/sessions/{session}/events

event: thinkingThe customer asked about a refund window.

event: messageDrafted a 120-word reply.

event: resultturn ended

Fig. The live stream while it works. Event names are the stream's.

POST your webhook · run.completed

type: run.completed
data.status: completed
data.result: Thanks for reaching out. Your order is within the 30-day window…
data.total_cost_usd: 0.06

Fig. The webhook Rush posts when the turn ends.

01
Create a key
An org admin creates a key under Settings, API keys. Store the rk_live_… secret on your server as RUSH_API_KEY.
02
Give the key a webhook
Set a public https endpoint on the key. The response carries the whsec_… signing secret once.
03
Start one session per task
POST /o/{org}/sessions with harness and input. Without a repository it runs in a sandbox of its own, with a computer and a browser.
04
Verify and store the result
Each finished turn posts run.completed, run.failed or run.cancelled, signed per Standard Webhooks. Check the signature, then store data.result.