Produce a report or file, no repo
A file you download
Send a request with no repository; the agent works in its own computer and returns a file as one of the session's artifacts.
Best for
- Research, analysis and drafts that end in a document
- Work on files you attach instead of a repository
Uses
- An org API key
From your code
POST /o/{org}/sessions{
"harness": "claude",
"input": [
{
"type": "text",
"text": "Compare these two vendor contracts and write a one-page summary of the differences as summary.md."
},
{
"type": "document",
"name": "vendor-a.pdf",
"source": {
"type": "url",
"url": "https://example.com/vendor-a.pdf"
}
}
]
}Watch it work, then read what comes back
GET /o/{org}/sessions/{session}/eventsevent: tool_useread · vendor-a.pdf (14 pages)event: thinkingTermination terms differ by 60 days.event: tool_usewrite · summary.mdevent: messageWrote summary.md.GET /o/{org}/sessions/{session}- status
completed- artifacts
[{ name: "summary.md", url: … }]- total_cost_usd
0.19
Steps
- 01
Send the request
inputis a string, or text and file blocks: an image, a document or a file you uploaded first. - 02
Follow it or wait
Hold the event stream, poll the session, or let your webhook tell you when it ends.
- 03
Download the artifact
Files the agent writes for you come back as the session's artifacts; download one by its id.
In the API and the docs
Related
All use casesRun 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.
Open the recipeInvestigate an incident
A report with evidence
Hand the agent an incident and read access to its sources; it comes back with a report that cites what it found, and no code change.
Open the recipe