From idea to first request

Give your agent
a way into the web.

Three small steps. One API key. Search and fetch through REST or MCP.

Set up Cloud access

01 /

Create your account

Sign in with an email code.
Add a passkey whenever you like.

Create an account
02 /

Add some credit

Start from €5 in prepaid credits.
Only successful operations are charged.

Add credit
03 /

Make an API key

Create a key and copy it when it appears.
Store it somewhere secure.

Create a key
Make the connection

A familiar API.
An open protocol.

Send a search request with REST, or add Searchbase to an MCP client that supports remote HTTP servers and bearer authentication.

Set SEARCHBASE_API_KEY in your environment. MCP clients that support variable expansion read it from there; configuration format varies by client.

curl https://api.searchbase.md/api/v1/search \
  -H "Authorization: Bearer $SEARCHBASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"independent web search","limit":5}'
Read a page

Have a URL?
Get the content.

Fetch a web page as Markdown. The MCP equivalent is fetch_url; search uses web_search.

Cloud fetch runs JavaScript on every page. Pages that need a sign-in or interaction, or that block automated access, may return limited content. Fetch respects robots.txt, and a failed fetch returns a code that says why.

REST / FETCH
curl https://api.searchbase.md/api/v1/fetch \
  -H "Authorization: Bearer $SEARCHBASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com"}'
A useful request ID. No saved search content.
Every API response includes X-Request-ID. When you need help, email support@searchbase.md and include it. Keep API keys in authorization headers, never in URLs. Read our privacy approach.

New MCP clients should use Streamable HTTP at https://mcp.searchbase.md/mcp/http. For clients requiring SSE, use https://mcp.searchbase.md/mcp/sse with the same bearer header on the connection and follow-up requests. Initialization, tool discovery, and ping are free.