Linkup for AI agents
Linkup is a web search API that returns relevant, sourced results for building research and retrieval workflows that need current information from the web. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Linkup.
Search the web for a topic
Run a search query to gather sourced web results for a research question.
Fetch a specific webpage
Fetch the content of a known URL to extract details for a summary, read-only.
Check remaining search credits
Look up the account's credit balance before running a large batch of searches.
4 Linkup actions, graded by risk.
Every Linkup action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- linkup.get_credits_balanceGet Credits Balance
- linkup.searchSearch Linkup
- linkup.fetch_webpageFetch Webpage
write
1Create and change things. Allow, or ask the user first.
- linkup.create_responseCreate Response
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Linkup in three steps.
- 01Your users connect LinkupThey add their Linkup api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Response” can wait for the user to approve.
- 03Any agent can actYour agent calls Linkup through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('linkup', { read: 'allow', write: 'ask', // create_response destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Linkup connects.
Users add their Linkup api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Linkup connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Linkup from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore web data and scraping apps.
Linkup and Arc0, answered.
Can I use Linkup with Claude, ChatGPT or Cursor?
Yes. Connect Linkup to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Linkup actions you allow.
How do users connect Linkup?
Users add their Linkup api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Linkup actions can my agent take?
4 in total: 3 read, 1 write and 0 destructive, such as “create Response”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Linkup?
Yes. Allow read actions and deny writes in the Linkup policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Linkup too?
Yes. The same Linkup connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Linkup into your agent.
Your users connect Linkup once, under your brand. Your agent gets 4 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan