Web search in Zapier with x402serps
MCP Client by Zapier connects to remote MCP servers (Streamable HTTP or SSE) with OAuth or a Bearer token, but it has no custom headers. Use a credit key, or call the REST API from Webhooks by Zapier.
Option A: MCP Client by Zapier
- Add an MCP Client by Zapier action and create a connection.
- Server URL
https://x402serps.com/api/mcp, Transport Streamable HTTP. - Bearer Token:
xs_YOUR_KEY. - Choose the tool (e.g.
web_search) and map fields.
Option B: Webhooks by Zapier → Custom Request
Method: POST
URL: https://x402serps.com/api/v1/search
Data: {"q": "your query", "num": 10}
Headers: Content-Type | application/json
Authorization | Bearer xs_YOUR_KEY (or X-Trial | 1 to test)Pay per call with x402 instead: tool calls without a trial header or key return the x402 payment requirements, which an x402-aware client can pay in USDC on Base or Solana. Search is $0.004 a call. Buy a credit key on the pricing page.
Pricing · Docs · MCP · Integrations · Help