Web search
Two tools of Evanesca's MCP server, web_search and web_fetch, let your agent search and read the web. They go through Linkup, a French company, and each call is billed: €0.0076 a search, €0.0015 a page.
SoonOpening soon: what follows describes the service as it will work.
The two tools
The REST API has no web-search endpoint: both tools live on the MCP server, next to the models. web_search returns up to 8 results, each with the text of its page — not just a snippet — cut at 15,000 characters, so your agent can often answer from the first call. web_fetch is the follow-up when a result's text is not enough.
| Tool | Arguments | What it returns | Price |
|---|---|---|---|
web_ | query (string, required); depth (“fast” or “standard”, the default) | Up to 8 results, each with the text of its page, cut at 15,000 characters. | €0.0076 |
web_ | url (string, required): an http or https address | The page's text, as markdown, cut at 15,000 characters. | €0.0015 |
Call them
An MCP client calls them by itself when its model decides to. By hand, it is one JSON-RPC tools/call request per POST, with your key — or, through a connector, its web right (the rights). Both also need credit above zero.
curl https://evanesca.app/api/mcp \
-H "Authorization: Bearer $EVANESCA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": { "name": "web_search", "arguments": { "query": "Swiss adequacy decision", "depth": "fast" } }
}'curl https://evanesca.app/api/mcp \
-H "Authorization: Bearer $EVANESCA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": { "name": "web_fetch", "arguments": { "url": "https://www.linkup.so/privacy-policy" } }
}'What goes to Linkup
web_search and web_fetch call Linkup, a French company — Linkup Technologies SAS, registered office in Fresnes, France — on Evanesca's own Linkup account: the same engine as the chat's web search. Linkup receives only what the tool needs — the query your agent writes, or the address of the page to read — never the conversation, and Evanesca keeps no copy of the queries or the results. Evanesca has not verified where Linkup's servers run; its own privacy policy applies, read on 13 Oct 2026.
In Evanesca's chat, web search is off by default. Over MCP, it happens only when your agent calls web_search or web_fetch: then the query it writes, or the address of the page to read, goes to Linkup. The model call itself stays in Europe.
What it costs
Each call is billed to your credit, VAT included: €0.0076 a search, €0.0015 a page — about €7.56 for 1,000 searches. Over MCP that is all you pay for them: your client's own model reads the results. In the chat and in Agent mode, the tokens the model spends reading the results come on top (billing).