Skip to content
looot docs
Esc
↑↓navigate↵open⌘Jpreview
On this page

Zyte API

Zyte API on looot as of 2026-09-28: 1 job through 1 endpoint, how you reach it, what it costs, and how to run it.

Zyte API

Web data1 job, 1 endpoint

What it’s good for

Zyte API is in Web data. Reach for it to get extract.

As of 2026-09-28 (catalog revision 85280) it serves 1 job through 1 endpoint.

Jobs

Job id What it does Endpoints
extract.get Get extract 1

Access

  • Runs on looot’s key for 1 endpoint: nothing to set up, the run spends your looot balance. You can connect your own key instead; see Bring your own key.

Price basis

1 per call (from $0.00044). A call that fails at the provider costs $0; see What’s free.

Free first in fallback

No. Every endpoint bills on each answer, found or not, so a fallback walk pays for a miss here. See Free first.

Run it

A job run takes shared input names, not Zyte API’s own field names; looot maps them for each provider. For job:extract.get, url is taken by 1 of its 3 providers. See Job inputs.

Example input for looot run or the MCP run tool, with placeholder values:

looot run job:extract.get --input '{"url":"https://example.com"}'
{
  "endpointId": "job:extract.get",
  "input": {
    "url": "https://example.com"
  },
  "idempotencyKey": "<new unique key>"
}

A job run picks among all the job’s providers. To run Zyte API itself, name one of its endpoints (MCP search with {"filters": {"provider": "zyte-api"}} lists them), for example zyte-api-extract: looot inspect zyte-api-extract prints its exact input fields and price.

In the live catalog

Zyte API’s name and logo are trademarks of their owner, shown to identify the provider.

Was this page helpful?