Skip to main content
Agents are good at asking for more than they need. Titan bounds every call so a loose prompt cannot turn into an unbounded crawl or an unbounded bill.

​
Caps

Exceeding a hard cap returns limit_exceeded before any run starts, so it costs nothing:
Some values clamp rather than fail—max_results above 100 is reduced to 100, and timeout_seconds above 30 is reduced to 30.

​
URL safety

Every URL is validated and normalized before work begins. Rejected: Rejections return unsafe_url and cost nothing. In titan_fetch, individual bad URLs land in failed[] while the rest of the batch proceeds; if every URL is rejected, the call fails and starts no run.

​
Redirects are re-checked

A public URL that redirects to a private address is stopped at the redirect. Every hop passes the same checks as the original, so a redirect chain cannot be used to reach something the first URL could not.

​
Crawl boundaries

Two boundaries are enforced independently of your parameters: Same origin. Every URL a crawl returns is on the seed host. Cross-origin URLs are filtered out at the edge, even if a script produced them, and reported:
Dropped records are not billed. robots.txt. Honored by default via respect_robots_txt: true.

​
No arbitrary code

The MCP server does not accept user-supplied scripts. Extraction runs from Titan-curated templates only, and titan_run_template is restricted to the eight-template allowlist. An agent cannot be prompted into executing code you did not intend, because there is no path to execute code at all. Browser cookies and credentials are likewise not accepted—agent tool calls fetch public web content.

​
Rate limits

The Titan control plane applies request-rate limits per caller. If your agent runs into them, back off—the platform limiter returns 429 with reset headers. Individual providers also rate-limit. A blocked search returns provider_rate_limited, which is retryable with backoff, or you can switch search_provider. Search providers do not fall back automatically; that choice stays yours. See Rate limits for the platform limits.

​
Choosing limits deliberately

​
What is not covered

These limits are the agent-facing contract. Worker-side throughput, proxy fairness, and queue depth also shape how fast a run completes, but they are operational concerns rather than limits your agent can hit directly.

​
Next steps