Skip to main content
This page is structured for direct use as integration context for a coding agent, or as a function-calling tool definition. Operational guidance is repeated inline so the page is self-contained.

Linkup /fetch integration guide

You are integrating the Linkup /fetch API: a real-time page content extractor. Given a URL, it returns clean LLM-ready markdown. Optional JavaScript rendering is available for client-side-rendered pages, along with optional raw HTML and image URL extraction. "pro" delivers significantly higher success rates on hard-to-retrieve pages. Limits: HTML up to 20 MB, PDF up to 100 MB. HTML and PDF only. Latency is typically ~1s.

When to use it

Use /fetch when the URL is already known: typically after /search has narrowed the candidates, or when a user has supplied the URL directly. Other endpoints in the API:
  • Search (/search): when no URL is available and web content must be located.
  • Research (/research): autonomous research agent. Async, 2–20 minutes depending on depth.
  • Tasks (/tasks): asynchronous batch wrapper around Search, Fetch, and Research.

Setup

Example (Python; adapt to the project’s language)

Tool definition (OpenAI function-calling format)

Remove the "type": "function" envelope and rename parameters to input_schema for the Anthropic format.

Operational guidance (inline)

mode selection

Use "standard" for mode by default and "pro" for hard-to-retrieve pages. "pro" delivers significantly higher success rates on hard-to-retrieve pages. It costs more. mode and renderJs solve different problems: mode controls how the page is accessed, while renderJs controls whether JavaScript is executed.

renderJs selection

For agentic pipelines, set renderJs to true by default to ensure the full content of each page is extracted. A page that requires JavaScript rendering and does not receive it returns near-empty markdown. Set renderJs to false only when all the URLs to be accessed have been confirmed to render server-side.

When to use Fetch

Fetch is purpose-built to extract the content of a webpage that has been identified. Linkup’s Fetch can be used as a stronger alternative to typical fetch tools because it can render JavaScript.

The Search → Fetch pattern

Use Search to find candidate URLs and Fetch to retrieve them in full when the agent needs to reason over the full page content rather than the snippets returned by Search.

Constraints

  • Fetch supports HTML and PDF. Other binary URLs (ZIPs, images, videos) return a 400 error.
  • Fetch returns a 400 error for HTML pages over 20 MB and PDFs over 100 MB.
  • Fetch does not authenticate. It returns the response a logged-out visitor would see.
  • Setting extractImages to true adds latency; enable it for workflows that consume image URLs.
  • includeRawHtml should be true only when the raw HTML is required.

TypeScript notes

  • Import: import { LinkupClient } from 'linkup-sdk'.
  • Method: await client.fetch({ url, mode, renderJs }). Single object argument.
  • Field names are camelCase: mode, renderJs, includeRawHtml, extractImages.