How do new agent effort tiers and URL fetching costs impact grounded AI development?
The changelog adds direct page fetching, new agent effort tiers and pricing details for developers building grounded AI applications.
Key points
- Passing a URL with web grounding mode fetches text before searching, costing $0.001 per successful fetch.
- Agent effort levels now include ultra-preview, with high and xhigh tiers increasing step limits and token caps.
- The API renamed the preset parameter to effort, maintaining backward compatibility with the deprecated alias.

Perplexity updated its API changelog to include direct URL fetching capabilities and new agent effort levels. These changes allow developers to control how the system retrieves and processes web content before generating answers.Perplexity added features to let developers fetch specific web pages and control agent complexity.The API now supports direct URL fetching with web grounding and expanded effort level configurations. The update also clarifies pricing for these additional retrieval steps.
The announcement
The Decisions API allows passing a page URL as state when mode is set to web_grounding. The fetched text replaces the URL before search. The response provides the retrieved page in fetched_results and search evidence in search_results. Developers can configure max_staleness to specify the maximum age of a page in seconds since its last crawl. If the stored copy is older, the system triggers a fresh crawl. Each successful URL fetch costs $0.001, separate from search and input token fees.reported
The context
The Agent API effort levels received significant updates. The fast tier defaults to openai/gpt-5.6-luna when openai/gpt-6-luna is not available.reported Low and medium efforts increased max output tokens to 128,000 and raised web_search token limits to 4,000.reported The high effort level uses openai/gpt-6.1-terra, increasing max steps to 40.reported The xhigh setting retains anthropic/claude-opus-5-5 as its primary model, with openai/gpt-6.1-sol serving as the fallback, while increasing the maximum step count to 300.reported A new ultra-preview effort level targets broad research tasks.
Reading between the lines
The API renamed the preset parameter to effort, though preset remains a deprecated alias. Responses now return both fields to ease migration. The undocumented ultra effort name is removed and now returns an error. The wide-research alias now selects xhigh. The maximum value for max_steps has increased from 100 to 500.reported Users of frozen configurations should update their values to align with the public API fields for each effort level.
The business case
Platform architects must account for the $0.001 per fetch cost when designing grounded workflows.reported The increased step limits in high and xhigh tiers allow for more complex reasoning chains, potentially increasing latency and token usage. The removal of the undocumented ultra effort simplifies versioning but requires code updates. The fallback models in fast and xhigh tiers provide resilience but may alter output characteristics.
Why it matters
- Direct URL fetching adds a predictable, per-request cost layer for grounded applications.
- Increased token and step limits in effort tiers enable more complex agent workflows.
- The rename from preset to effort requires minor code updates for API consumers.
- Fallback model specifications clarify which underlying models handle requests during outages.
Topics: API, agents, pricing, grounding, Perplexity
Updated
Then / now / next
The API used preset as the primary parameter for effort levels and lacked direct URL fetching.
The API supports URL fetching with web grounding and renamed preset to effort with new tiers.
Monitor for SDK updates to natively support the mode parameter and new effort levels.
Story timeline
- Then The API used preset as the primary parameter for effort levels and lacked direct URL fetching.
- 04 Nov 2026 Perplexity API Changelog page updated:
- 05 Nov 2026 Perplexity API Changelog page updated: Filters
- 05 Nov 2026 Perplexity API Changelog page updated:
- 05 Nov 2026 Perplexity launches its own take on AI agents for work
- Now The API supports URL fetching with web grounding and renamed preset to effort with new tiers.
- Next Monitor for SDK updates to natively support the mode parameter and new effort levels.
The strongest doubt
Counterpoint from the sources
The Python and TypeScript SDKs do not yet have a mode parameter, requiring manual request body updates.
For readers
Developers
- Update code to use effort instead of preset and handle the new fetched_results field.
- Account for $0.001 per URL fetch cost in budget calculations.
Business
- Higher step limits in xhigh may increase latency and costs for complex tasks.
- Fallback models provide resilience but may affect output consistency.
Researchers
- The ultra-preview effort level targets broad research and data-gathering tasks.
- Direct URL fetching allows for more precise grounding of research queries.
Ask the article
Local keyword search of this article; no generated answers.Did this article give you the evidence you needed?
Your choice stays on this device. No public tally.Questions readers ask
How much does URL fetching cost in the Perplexity API?
A successful URL fetch incurs a $0.001 charge, separate from costs for searches and input tokens.
What is the new ultra-preview effort level for?
It is intended for extensive research and data collection tasks that prioritize comprehensive coverage.
Does the API still support the preset parameter?
The preset parameter remains supported as a deprecated alias, with responses including both the effort and preset fields.
Connected stories
Reading receipt
- Passing a URL with web grounding mode fetches text before searching, costing $0.001 per successful fetch.
- Agent effort levels now include ultra-preview, with high and xhigh tiers increasing step limits and token caps.
- The API renamed the preset parameter to effort, maintaining backward compatibility with the deprecated alias.
Still open: When will the Python and TypeScript SDKs natively support the mode parameter?
Still open: How will the ultra-preview effort level impact latency for long-running tasks?