The Anything API lets you describe a task in plain English, and Notte will build, deploy, and run a web automation function for you — all through a single HTTP request. The response is an SSE stream so you can follow the agent’s progress in real time.Documentation Index
Fetch the complete documentation index at: https://notte-experiment-visibility-md-links.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Try it now
Open the Anything API web app.
Get your API key
Create an account on the Console to get started.
Quick start
done event contains the function_id of the created function, which you can re-run later via the Notte CLI or SDK.
Request
A natural-language description of the task you want automated.
POST /api/anything/start
| Header | Required | Description |
|---|---|---|
Authorization | Yes | Bearer <NOTTE_API_KEY> |
Content-Type | Yes | application/json |
Response
The response is atext/event-stream. Each line follows the SSE spec:
Event types
| Type | Description | Key fields |
|---|---|---|
status | Agent lifecycle updates | status |
thinking_delta | Agent reasoning (streamed) | delta |
text_delta | Agent response text (streamed) | delta |
tool_start | Agent started using a tool | name |
tool_result | Tool execution result | content |
message_complete | An assistant message was persisted | role |
notte_session_data | Browser session info | viewer_url |
function_uploaded | A Notte Function was created | function_id, function_name, created_at |
done | Agent finished | total_cost_usd, function_id, metadata |
error | Something went wrong | error, detail |
timeout | Agent timed out | reason, detail |
cancelled | Agent was cancelled | reason |
Terminal events
The stream ends after one of these events:done, error, timeout, or cancelled.
Example: done event
Re-running the created function
Once the agent finishes, it typically creates a reusable Notte Function. Use thefunction_id from the done event to run it again:
Consuming the SSE stream
Python
consume_sse.py
TypeScript
Error handling
| Status | Meaning |
|---|---|
401 | Missing or invalid API key |
400 | Missing query field or invalid JSON |
502 | Agent failed to start or SSE stream unavailable |
error event in the SSE stream instead of an HTTP error status.
Pricing
Each request is billed based on the LLM usage incurred by the agent. Thetotal_cost_usd field in the done event reports the exact cost for that run.
