Reserp integration
Reserp is a Google Search results API: send a complete Google Search URL (query, country, language, date filters, images, shopping, news or local tabs, page offset) and get the page back either as one flat list of every external result link with its accompanying text, or as typed blocks in page order (organic results, ads, shopping, local places, news, videos, People also ask, AI overview and more). Each successful call is billed as one request, empty pages included, drawn from the prepaid balance while it is positive and otherwise from the 500 free requests a month; invalid, unauthenticated, rate-limited and allowance-exhausted requests are not billed. The previous v1 routes are not exposed. Authentication is a Reserp API key sent as a Bearer token in the Authorization header.
Say what should happen.
The workflow builds itself.
What you can do with Reserp
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
search_googleSearch googlePOSTAgents: ask firstRuns one Google search from a complete Google Search URL and returns every external result link on the page (organic, ads, carousels, sitelinks) in one flat list with its text. Billed as one request. Page on with pagination.next_url.search_google_structuredSearch google structuredPOSTAgents: ask firstRuns one Google search from a complete Google Search URL and returns the page as typed blocks in page order (organic, ads, shopping, local, news, videos, People also ask, AI overview...). Best effort: fields may be missing. Billed as one request.
Use Reserp from Claude Code, Cursor or Codex
Connect Reserp in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Reserp operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Reserp
- Create your workspace
Sign up free. Nothing to install.
- Connect Reserp once
Add your Reserp connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Reserp integration FAQ
What can you do with the Reserp integration?
LiveContext exposes 2 operations on Reserp, covering search result.
