> ## Documentation Index > Fetch the complete documentation index at: https://docs.zenrows.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > The Zenrows API (Fetch, Extract, Crawl and Batch) is described in OpenAPI 3.1 at https://www.zenrows.com/openapi.json and listed in the RFC 9727 API catalog at https://www.zenrows.com/.well-known/api-catalog. Every endpoint also has its own page under /api-reference with its schema. Use the spec for exact parameter names and types. To call Zenrows from an agent, connect the MCP server at https://mcp.zenrows.com/mcp. To search these docs from an agent, connect the docs MCP server at https://docs.zenrows.com/mcp. Agent skills for Zenrows are published at https://github.com/ZenRows/cli and install with `npx skills add ZenRows/cli`. # List the domains your account submitted > Every domain this account has submitted for preparation, with the monthly allowance alongside it. This lists what you submitted, not every domain Extract serves (see `listExtractDomains`). Costs no credits. Documented at https://docs.zenrows.com/extract/endpoints. ## OpenAPI ````yaml /api-reference/openapi.json get /extract/prepared-domains openapi: 3.1.0 info: title: Zenrows API version: 1.0.0 summary: >- Reach any page, including the protected web, and return it as HTML, Markdown, plaintext, PDF or structured JSON. description: >- Zenrows is web data infrastructure for agents and applications. Three HTTP surfaces are described here: - **Fetch and Extract**: one synchronous request per page, at `https://api.zenrows.com/v1/`. Authentication is the `apikey` query parameter. - **Crawl**: collect the URLs behind one start page, at `https://api.zenrows.com/v1/crawls`. Authentication is the `X-API-Key` header or the `apikey` query parameter. - **Batch**: asynchronous jobs of up to 100,000 URLs, at `https://async.api.zenrows.com/v1`. Authentication is the `X-API-Key` header. **Browser** is not described here because it is not HTTP: you connect Puppeteer or Playwright to a WebSocket endpoint. See https://docs.zenrows.com/browser-sessions/introduction. **Cost.** A request costs 1 credit, 5 with JavaScript rendering, 10 with premium proxies, 25 with both, and 1 to 25 under `mode=auto`. Failed requests are never charged. The free tier is 5,000 credits a month, no card. **Versioning and deprecation.** The version is in the URL path (`/v1`, the only version so far). Inside a version Zenrows only adds: new endpoints, optional parameters, response fields and headers. Nothing is removed or changed. Retiring a version is announced at least twelve months ahead, and every response from a deprecated version carries the `Deprecation` (RFC 9745) and `Sunset` (RFC 8594) headers. Policy: https://docs.zenrows.com/api-versioning. **Getting a key without a human.** `POST https://app.zenrows.com/api/agent/signup` returns a usable key; the spec is at https://www.zenrows.com/auth.md and a setup playbook at https://www.zenrows.com/SKILL.md. termsOfService: https://www.zenrows.com/legal/terms-of-use contact: name: Zenrows support email: support@zenrows.com url: https://www.zenrows.com/contact license: name: Proprietary url: https://www.zenrows.com/legal/terms-of-use servers: - url: https://api.zenrows.com/v1 description: Fetch and Extract (synchronous) security: - apiKeyQuery: [] tags: - name: Fetch description: Retrieve one page, optionally rendered, proxied, converted or extracted. - name: Extract description: Which domains Extract serves, and getting a new one prepared. - name: Crawl description: Collect the URLs behind one start page, and each page's HTML when asked. - name: Batch description: Submit many URLs as one job and collect the results. - name: Account description: Plan, credits and concurrency for the calling key. - name: Onboarding description: Get a working key with no human in the loop. externalDocs: description: Zenrows documentation url: https://docs.zenrows.com paths: /extract/prepared-domains: get: tags: - Extract summary: List the domains your account submitted description: >- Every domain this account has submitted for preparation, with the monthly allowance alongside it. This lists what you submitted, not every domain Extract serves (see `listExtractDomains`). Costs no credits. Documented at https://docs.zenrows.com/extract/endpoints. operationId: listExtractPreparations responses: '200': description: The account's submissions and allowance. content: application/json: schema: type: object properties: allowance: type: object description: >- Domains this account can still ask to have prepared this month. A failure that returns its slot is not counted in `used`. properties: used: type: integer limit: type: integer remaining: type: integer month: type: string description: >- The UTC calendar month the count applies to, `YYYY-MM`. The allowance resets when it rolls over. example: 2026-09 domains: type: array items: $ref: '#/components/schemas/ExtractPreparation' '401': description: The API key is missing or invalid. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/problem+json: schema: $ref: '#/components/schemas/Error' example: code: AUTH002 detail: Invalid API key. instance: /v1 status: 401 title: Invalid apikey provided (AUTH002) type: https://docs.zenrows.com/api-error-codes#AUTH002 security: - apiKeyQuery: [] - apiKeyHeader: [] components: schemas: ExtractPreparation: type: object description: A domain's preparation for Extract. properties: domain: type: string status: type: string enum: - preparing - ready - failed description: Whether the domain can be used yet. Branch on this. state: type: string description: The current step. Gains steps over time. examples: - received - discovering - preparing - verifying - ready - failed roles: type: array description: >- Progress per kind of page. Only present for the account that submitted the domain. items: type: object properties: role: type: string status: type: string url: type: string detail: type: string description: Why this kind of page stopped, when it did. failure: type: object description: Present when `status` is `failed`. properties: code: type: string examples: - interrupted - preparation_exhausted - discovery_failed - unpreparable - preparation_failed - verification_failed - unsupported detail: type: string slot_consumed: type: boolean description: Whether the attempt used an allowance slot. submitted_at: type: string format: date-time updated_at: type: string format: date-time Error: type: object description: >- Zenrows error envelope, sent as `application/problem+json` (RFC 9457 problem details). `code` is the stable identifier to branch on; `type` links to its entry in the catalogue at https://docs.zenrows.com/api-error-codes. Read back from live responses. properties: code: type: string example: AUTH002 status: type: integer example: 401 title: type: string example: Invalid apikey provided (AUTH002) detail: type: string example: Invalid API key. type: type: string format: uri example: https://docs.zenrows.com/api-error-codes#AUTH002 instance: type: string description: >- The request path or a request URN. Quote it when reporting a problem. example: /v1 headers: XRequestId: description: Identifier for this request. Quote it when reporting a problem. schema: type: string example: 67fa4e35647515d8ad61bb3ee041e1bb securitySchemes: apiKeyQuery: type: apiKey in: query name: apikey description: >- Fetch, Extract, Crawl and the account endpoint accept the key as the `apikey` query parameter. Keys are per account and self-serve: create one in the Zenrows dashboard (app.zenrows.com), or, for an agent with no human present, `POST https://app.zenrows.com/api/agent/signup`. apiKeyHeader: type: apiKey in: header name: X-API-Key description: >- Batch, Crawl, the Extract endpoints and the account endpoint read the same key from the `X-API-Key` header. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.