Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LINKUP_API_KEYYesYour Linkup API key (required).
LINKUP_TIMEOUTNoSeconds per HTTP request (default 180).180
LINKUP_BASE_URLNoBase URL for the Linkup API (default https://api.linkup.so/v1).https://api.linkup.so/v1

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Linkup web access (docs read 2026-11-13; prices in USD per call, billed from a prepaid balance).

Routing:

  • Known URL, want the page: linkup-fetch (0.001 to 0.011). Add renderJs for JavaScript sites, mode "pro" for hard pages, schema for typed JSON from that one page.

  • Question answerable by a web search: linkup-search. depth "fast" (about 1 s, keyword-only, 0.005) is the default; "standard" (1 to 3 s, one agentic pass, follows instructions, can scrape one URL in the query); "deep" (5 to 30 s, several iterations, sequential instructions, 0.05 to 0.055). outputType "searchResults" when you will reason over the sources yourself, "sourcedAnswer" for a cited answer, "structured" with a JSON schema for typed output.

  • Multi-source synthesis that one search cannot resolve: linkup-research, asynchronous, 2 to 20 minutes, 0.25 (S) to 2.50 (XL) per task, default L = 1.50. Set mode explicitly (answer, investigate, research). Then linkup-wait-research or linkup-get-research. Never re-create a task to retry a wait; every creation is billed.

  • Bulk or mixed work (up to 100 items per batch, same price per item): linkup-tasks-create, then linkup-tasks-list or linkup-tasks-get.

  • Balance: linkup-credits-balance. A 429 means rate limit or no credit left.

  • Reference: linkup-guide (topics) and the resources linkup://guide and linkup://openapi.json.

Rules from Linkup's docs: put date ranges in fromDate/toDate, not in the query; prefer a few trusted includeDomains; keep structured schemas flat; poll research at 2 s backing off to 10 s, never above 1 request per second; failed calls are not billed. Extract and Rewind are closed betas (403 unless enabled for the organisation).

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
linkup-searchA

Search the web with Linkup (POST /v1/search, synchronous).

Cost per call: flash, fast or standard 0.005 USD (searchResults) or 0.006 (sourcedAnswer, structured); deep 0.05 or 0.055. Rate limit 10 requests per second per organisation. A query without results returns HTTP 400 and is not billed. LinkedIn profile, company and post pages can only be read through this endpoint (give the exact URL in the query with standard or deep), not through linkup-fetch.

linkup-fetchA

Fetch one web page as clean markdown with Linkup (POST /v1/fetch, synchronous).

Price per call: standard 0.001 (no JS) or 0.005 (render_js); pro 0.005 or 0.01; a schema adds 0.001. Returns markdown and favicon always; data with a schema; images with extract_images; rawContent and contentType with include_raw_content. The endpoint is anonymous, reads this one URL only and follows no links. HTTP 400 is returned for binary files other than PDF, unreachable targets, oversize pages, instructions without schema, and failed structured extraction; such calls are not billed.

linkup-researchA

Start an autonomous research task with Linkup (POST /v1/research). Asynchronous: returns at once with id and status "pending"; the agent then plans, searches many sources in parallel, verifies and synthesises, in 2 to 20 minutes. Collect the result with linkup-wait-research (polls for you) or linkup-get-research.

Price per task by reasoning_depth: S 0.25 USD (2 to 5 min), M 0.50 (3 to 7 min),
L 1.50 (5 to 10 min, the default), XL 2.50 (10 to 20 min). Failed tasks are not billed.
Do not create a second task to "retry" a slow one; wait on the id you have.

Use it for questions a single search cannot resolve: verified answers with an audit trail
of citations, a focused investigation of one subject, or a broad report by theme. For a
quick fact use linkup-search. Set mode explicitly for predictable latency, cost and
shape. Phrase the question precisely: angles to cover, leads to pursue, facts to verify,
entities to compare, constraints, and the structure you expect back. Put dates in
from_date/to_date, give a few trusted include_domains when they exist.
linkup-get-researchA

Read one research task (GET /v1/research/{id}). Free.

status is pending, processing, completed or failed. When completed, output holds the answer and sources (sourcedAnswer) or the JSON object (structured); when failed, error holds the reason. Poll at 2 s backing off to 10 s and never faster than once per second, or use linkup-wait-research, which does that for you.

linkup-wait-researchA

Wait for a research task and return it when it is completed or failed (GET /v1/research/{id} in a loop).

Polls at Linkup's recommended cadence: 2 s, doubling up to 10 s, never above 1 request per second, and reports progress to the client. If max_wait_seconds elapses first, the task is returned with its current status (pending or processing) and done=false: call this tool again with the same id. Free; the task itself was billed when created.

linkup-list-researchA

List the organisation's research tasks (GET /v1/research). Free.

Returns data (tasks, each with id, status, input, error, createdAt, updatedAt and an output_preview, or the full output with include_output) and metadata (page, pageSize, total, totalPages). Results are kept for a bounded period; store what you need.

linkup-tasks-createA

Create a batch of asynchronous tasks (POST /v1/tasks). Each task is billed exactly like the direct call: search 0.005 to 0.055, fetch 0.001 to 0.011, research 0.25 to 2.50 (100 research tasks at the default depth L cost 150 USD), extract variable (2 to 10 typical). There is no batch discount; Tasks is for bulk, long-running or mixed work, not for single calls.

Returns the task envelopes (id, type, status pending, input, output null). Then poll with linkup-tasks-list (bulk, every 5 s for research, 1 to 2 s for search and fetch) or linkup-tasks-get (one task). A failing task does not fail the batch and is not billed. The organisation has a concurrency quota (see quota in linkup-tasks-list); above it the API answers 429. Results are kept for a bounded period: store them when they complete.

linkup-tasks-getA

Read one task of any type (GET /v1/tasks/{id}). Free. status: pending, processing, completed, failed. output has the same shape as the matching synchronous endpoint; for extract tasks it holds resultUrl (download with linkup-extract-download).

linkup-tasks-listA

List the organisation's tasks of all types (GET /v1/tasks). Free. Returns data (task envelopes with an output_preview, or full outputs with include_output), metadata (page, pageSize, total, totalPages) and quota (inFlight: tasks pending or processing now; limit: maximum concurrent tasks allowed). Prefer this bulk poll over many linkup-tasks-get calls; the poll cap is 1 request per second.

linkup-credits-balanceA

Return the prepaid balance in USD (GET /v1/credits/balance). Free. Linkup credits eligible accounts back up to 20 USD a month; when the balance is used up the API answers 429. Extract tasks need a balance of at least 10 USD.

linkup-extractA

Start an Extract task (POST /v1/extract) that turns a listing page into rows of data, delivered as an NDJSON file. CLOSED BETA: the API answers 403 unless Linkup has enabled it for the organisation. Variable price, typically 2 to 10 USD per completed task, shown as creditsUsed in the output; failed tasks are free; a balance of at least 10 USD is required. Asynchronous: poll with linkup-get-extract every 30 s, then download with linkup-extract-download. For one JSON object from one known page use linkup-fetch with schema instead.

linkup-get-extractA

Read one extract task (GET /v1/extract/{id}). Free. When completed, output holds creditsUsed, rowsReturned and resultUrl (an NDJSON download link valid for 24 hours); the rows are not in the response.

linkup-list-extractB

List extract tasks (GET /v1/extract). Free. Closed beta.

linkup-extract-downloadA

Download the NDJSON result of a completed extract task and return its rows as JSON. Free (the download link in the task output is a plain file URL, valid 24 hours).

linkup-rewind-searchA

Search the web as it was at the end of a given UTC day (POST /v1/rewind/search). CLOSED BETA: 403 unless enabled for the organisation. Returns results with content, name, url, validFrom and validTo (the first day the revision was no longer visible, null if current).

linkup-rewind-fetchA

Return a page as it was at the end of a given UTC day (POST /v1/rewind/fetch). CLOSED BETA: 403 unless enabled; 404 when no revision is visible that day; 422 when the day is not available.

linkup-responsesA

Generate a web-grounded answer in the OpenAI Responses format (POST /v1/responses). This is the endpoint behind using Linkup as an OpenAI-compatible base URL. Returns output_text and output messages with url_citation annotations. Its price is not published on the pricing page (read 2026-11-13); check linkup-credits-balance before and after if it matters. For most uses linkup-search with sourcedAnswer is the simpler call.

linkup-guideA

Explain the Linkup API: endpoints, parameters, prices, latencies, limits, polling rules and best practices, condensed from Linkup's documentation (read 2026-11-13). Free, no network.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Linkup API guideThe full Linkup API guide (same text as linkup-guide with topic all).
Linkup OpenAPI snapshotSnapshot of https://api.linkup.so/v1/openapi.json taken on 2026-11-13.

TDQS

A3.9/5.0

Scored across 18 tools

Disambiguation4/5

Most tools map to a distinct endpoint and resource (search, fetch, research, tasks, extract, rewind, credits), and descriptions explicitly steer between them (e.g. 'for a quick fact use linkup-search'). Residual overlap exists between linkup-search/sourcedAnswer, linkup-responses and linkup-research, and between linkup-research and linkup-tasks-create with a research type, which could still cause misselection.

Naming Consistency3/5

Names mix verb-first and resource-first ordering inconsistently: linkup-get-research / linkup-list-research / linkup-get-extract sit alongside linkup-tasks-get / linkup-tasks-list, and linkup-credits-balance is noun_noun. All are kebab-case and readable, but the same operation is spelled two different ways across resource families.

Tool Count4/5

18 tools is on the heavy side, but the surface spans several genuinely distinct feature areas (search, fetch, async research, batch tasks, extract, rewind, responses, billing, guide), each needing its own create/read/list or download. A few—linkup-responses, linkup-guide, and the closed-beta rewind pair—are marginal additions rather than core.

Completeness4/5

The surface covers the main lifecycle well: create/poll/list/wait for research, bulk create/get/list for tasks, extract create/get/list/download, credits, and an offline guide. The notable gap is the absence of cancel/delete operations for research, task, or extract resources, which matters for long-running, billable async work.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues