API reference by product
Extract also runs as a parameter of Fetch,
extract=auto. See Introduction to Extract for that path.
Endpoint reference
Every endpoint also has its own page, generated from the OpenAPI spec: typed parameters, request samples, a response example for each status code, and a playground that sends the request with your key.OpenAPI spec
The Zenrows API is described in OpenAPI 3.1 at www.zenrows.com/openapi.json, covering Fetch (including theextract parameter), the Extract endpoints, Crawl and Batch. The endpoint reference above is generated from a copy of this spec kept with these docs. Load it into an API client, a code generator, or an agent’s tool definitions for exact parameter names and types. The spec is listed in the RFC 9727 API catalog at www.zenrows.com/.well-known/api-catalog. See API Versioning and Deprecation for how versions are retired.
Authentication
Every request carries your Zenrows API key. Fetch reads it from theapikey query parameter, Batch reads it from the X-API-Key header, and Crawl and the Extract endpoints accept either. See Zenrows API Authentication for each surface and for where to find your key.
SDKs
Official, typed SDKs wrap the same API for Fetch and Batch, and Extract runs through the Fetch client. See Zenrows SDKs for the languages and install steps.MCP server
The Zenrows MCP Server gives AI tools, agents and applications the same capabilities over the Model Context Protocol, athttps://mcp.zenrows.com/mcp. Its tools are listed in the MCP tool reference.