skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
linkupplatform/skills101 installs

linkup-fetch

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 via the `linkup-fetch` MCP tool or direct REST calls. Prefer this over linkup-search when the URL is known; prefer linkup-extract when you need many structured rows from one listing page.

How do I install this agent skill?

npx skills add https://github.com/linkupplatform/skills --skill linkup-fetch
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill provides instructions and documentation for using Linkup's search and fetch APIs to retrieve web content as Markdown. No security issues were detected.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 2 issues

What does this agent skill do?

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

  • If the linkup-fetch MCP tool is available, pass it the URL.
  • Otherwise call the REST API directly. Requires LINKUP_API_KEY:
curl -sS -X POST "https://api.linkup.so/v1/fetch" \
  -H "Authorization: Bearer $LINKUP_API_KEY" -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 answerlinkup-search
You need many structured records from one listing page (team, catalog, jobs)linkup-extract (/v1/extract)
You need to discover URLs and then scrape themlinkup-search with depth: deep
The URL is a LinkedIn profile or postlinkup-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 linkup-extract (/v1/extract) or 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.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/linkupplatform/skills/linkup-fetch">View linkup-fetch on skillZs</a>