---
title: "Answer web"
description: "Run job:web.answer through the looot API: 2 providers, from $0.005 per call. Inputs, prices, output shape and code for curl, JavaScript and Python."
sidebar:
  hidden: true
---

{/* Generated by scripts/generate-api-reference.mjs from data/api-reference.json. Do not edit. */}

Answer web.

Job id `web.answer`, in Web search & research (Web data). As of 2026-10-01, 2 providers serve it through 2 tools. Run `job:web.answer` and looot picks one of them; with `fallback` on, a miss moves on to the next. See [Jobs](/concepts/jobs).

## Inputs

Fields the job's tools take, most shared first. Any key you send passes through unchanged.

| Name | Type | Taken by | Required by | Description |
| --- | --- | --- | --- | --- |
| `model` | string | 2 of 2 | 1 | Model used to generate the answer. |
| `text` | boolean | 2 of 2 | 0 | Also return full page text for each citation. |
| `input` | string | 1 of 2 | 1 | The natural language question for which you want to retrieve context. Example: "What is Microsoft's 2024 revenue?" |
| `instructions` | string | 1 of 2 | 0 | Optional instructions to guide the response generation. It`s similar to a system message. Example: "You are a helpful assistant that provides concise answers." |
| `outputSchema` | object | 1 of 2 | 0 | JSON Schema draft-07 for structured output instead of a plain string answer. |
| `query` | string | 1 of 2 | 1 | Natural-language question or instructions. Example: "What is the latest valuation of SpaceX?" |
| `systemPrompt` | string | 1 of 2 | 0 | Additional instructions guiding generated output/agent behavior. |

## Providers and prices

| Provider | Tool | Price |
| --- | --- | --- |
| [Exa](/providers/exa) | [`exa-answer`](/reference/tools/exa-answer) | $0.005 per call |
| [Linkup](/providers/linkup) | [`linkup-responses`](/reference/tools/linkup-responses) | $0.006 per call |

A call that fails at the provider costs $0. See [What's free](/money/free-and-failures).

## Output

Each provider answers in its own shape. Shape of the run's `result` from [`exa-answer`](/reference/tools/exa-answer), checked against 1 real answer:

```txt
{ answer, citations: { id, url, title, publishedDate }[], requestId, costDollars: { total } }
```

## Run it

Every call needs your API token in `LOOOT_TOKEN`; [Sign in](/get-started/sign-in#use-the-token-in-scripts-and-agents) shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With `wait: 30` the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll `GET /v1/runs/<runId>`.

Example input with placeholder values:

<CodeGroup>

```bash curl
curl -X POST "https://api.looot.ai/v1/runs" \
  -H "Authorization: Bearer $LOOOT_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"endpointId":"job:web.answer","input":{"query":"What is the latest valuation of SpaceX?"},"wait":30}'
```

```js JavaScript
const response = await fetch("https://api.looot.ai/v1/runs", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
    "Content-Type": "application/json",
    "Idempotency-Key": crypto.randomUUID(),
  },
  body: JSON.stringify({
    endpointId: "job:web.answer",
    input: {
      query: "What is the latest valuation of SpaceX?",
    },
    wait: 30,
  }),
});
const run = await response.json();
console.log(run.status, run.result);
```

```python Python
import os
import uuid

import requests

response = requests.post(
    "https://api.looot.ai/v1/runs",
    headers={
        "Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "endpointId": "job:web.answer",
        "input": {
            "query": "What is the latest valuation of SpaceX?",
        },
        "wait": 30,
    },
    timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))
```

</CodeGroup>

To pin one provider, send its tool id as `endpointId` instead of `job:web.answer`.