Use when you already know the exact URL and need its content as clean Markdown - a pricing page, article, docs page, or a URL found in a previous step. ALSO read this when writing code that calls the Linkup Fetch API. Uses the Linkup Fetch API through the automatically provisioned MaraClaw engine proxy. Prefer this over linkup-search when the URL is known.
Resources
1Install
npx skillscat add maraclaw/photon/linkup-fetch Install via the SkillsCat registry.
Linkup Fetch
When you already have the exact URL, use Fetch instead of search. It is faster and cheaper, and returns the page as clean Markdown (with JavaScript rendering and optional image extraction).
How to call it
MaraClaw automatically supplies LINKUP_API_BASE (the engine proxy base, including /api/linkup) and the agent-scoped LINKUP_PROXY_TOKEN. Use only this proxy for Linkup requests.
POST the URL to $LINKUP_API_BASE/v1/fetch.
curl -sS -X POST "$LINKUP_API_BASE/v1/fetch" \
-H "Authorization: Bearer $LINKUP_PROXY_TOKEN" -H "Content-Type: application/json" \
-d '{"url":"https://example.com/pricing","renderJs":true}'Default JavaScript rendering to on - many sites load content client-side, and the small latency cost is almost always worth the reliability. Turn it off only when speed matters more on a known-static page.
When to use fetch vs the alternatives
Use linkup-fetch when... |
Use instead... |
|---|---|
| You have one URL and want its content as Markdown | - |
| You don't know which URL has the answer | linkup-search |
| You need structured records from a known page | linkup-search with outputType: structured |
| You need to discover URLs and then scrape them | linkup-search with depth: deep |
| The URL is a LinkedIn profile or post | linkup-search (Fetch cannot authenticate into LinkedIn) |
Important: fetch reads page content; it cannot produce structured JSON from a page. If you need structured fields from a known page, use the Search API with outputType: structured.
After fetching
- Extract only the fields the task needs; don't dump the whole page back to the user.
- Keep the source URL so every claim can be verified.
For the full endpoint reference, read references/LINKUP_API_REFERENCE.md (Fetch API section) in this skill's directory.