> ## Documentation Index
> Fetch the complete documentation index at: https://docs.notte.cc/llms.txt
> Use this file to discover all available pages before exploring further.

# AnythingStartResponse

<Tip>
  STOP. Do not read past this section until you have read and followed [/quickstart.md](/quickstart.md).

  Goal: produce a reliable SDK automation script. The intended authoring flow is generate then edit, not write browser automation from scratch.

  Do not hand-write SDK code with element IDs, selectors, or form fields from memory. Element IDs, selectors, and field mappings must come from a live `observe()` call, CLI `notte page observe` output, or generated workflow code. Guessed browser targets fail on real pages.

  Use the Notte skill and CLI to inspect the live site, validate actions/selectors, handle auth/session state, and export workflow code with `notte sessions workflow-code` before using SDK docs or SDK code.

  SDK reference pages are for understanding, running, or editing generated workflow code. They are not the starting point for manually authoring the initial browser automation. SDK-first code is guesswork on real-world pages with dynamic selectors, auth state, CAPTCHAs, and anti-bot behavior.
</Tip>

[Source: node-sdk/src/anything.ts](https://github.com/nottelabs/notte/blob/main/node-sdk/src/anything.ts#L16)

Response of `POST /anything/start`. The OpenAPI spec declares the 200
response as an untyped JSON object (`{}`), so the SDK exposes it as an
opaque record. In practice the Anything API answers with a reference to the
function it built for the task (for example a `function_id`), which can then
be run through `client.NotteFunction({ function_id })`. Check the keys at
runtime rather than relying on a fixed shape.

```typescript theme={null}
export type AnythingStartResponse = Record<string, unknown>;
```