Advanced Extract Settings

The advanced_settings object on the Extract API lets you tune fetch behavior (cached vs live), excerpt sizing, and full content extraction. Extract uses a dynamic fetch policy by default and may request the source website when indexed content does not meet its freshness criteria. For an agent that searches indexed documentation without a live source-page fetch, see Search indexed web content for coding agents. Extract does not offer a documented cache-only security guarantee.

On /v1/extract, fetch_policy, excerpt_settings and full_content must be inside advanced_settings. Sending the v1beta top-level excerpts, full_content or fetch_policy fields to /v1/extract returns a 422. See the migration guide.

Fields

Field	Type	Notes	Example
fetch_policy	object	Controls when to return indexed content (faster) vs fetching live content (fresher). Extract uses a dynamic policy by default. For field details, see Fetch Policy below.	`{"max_age_seconds": 3600}`
excerpt_settings	object	Controls excerpt sizes. Provide `max_chars_per_result` for fine-grained control, or omit to use defaults.	`{"max_chars_per_result": 10000}`
full_content	bool or object	Controls full content extraction. Defaults to `false` (disabled). Set to `true` to enable with defaults, or provide a settings object.	`false` or `{"max_chars_per_result": 50000}`

Fetch Policy

The fetch_policy parameter controls when to return indexed content (faster) or fetch fresh content from the source (fresher). Fetching fresh content may take up to a minute and is subject to rate limits to manage the load on source websites.

Field	Type	Default	Notes
max_age_seconds	int	dynamic	Maximum age of indexed content in seconds. If older, fetches live. Minimum 600 (10 minutes). If unspecified, uses dynamic policy based on URL and objective.
timeout_seconds	number	dynamic	Timeout for fetching live content. If unspecified, uses a dynamic timeout based on URL and content type (typically 15s-60s).
disable_cache_fallback	bool	false	If `true`, returns an error when live fetch fails. If `false`, falls back to older indexed content.

Excerpt and Full Content Settings

Both excerpt_settings and full_content are configured inside the advanced_settings object. Enable full content with custom excerpt sizes:

{
  "urls": ["https://example.com"],
  "advanced_settings": {
    "excerpt_settings": {
      "max_chars_per_result": 5000
    },
    "full_content": {
      "max_chars_per_result": 50000
    }
  }
}

Enable full content with default excerpts:

{
  "urls": ["https://example.com"],
  "advanced_settings": {
    "full_content": true
  }
}

Notes:

When full_content is enabled, you’ll receive both excerpts and full content in the response
Excerpts are always focused on relevance; full content always starts from the beginning
Without objective or search_queries, excerpts will be redundant with full content. The request still succeeds, but may return less relevant content and may include a warning.
max_chars_total (top-level) controls total excerpt size but does not affect full content

Getting started

Web Tools

Web Agents

Developer Tools

Platform Integrations

Data Integrations

Additional Resources

Advanced Extract Settings

Fields

Fetch Policy

Excerpt and Full Content Settings

​Fields

​Fetch Policy

​Excerpt and Full Content Settings

Fields

Fetch Policy

Excerpt and Full Content Settings