x402serps logox402serps

Web search in ChatGPT with x402serps

ChatGPT adds remote MCP servers from Plugins \u2192 Add custom MCP server (older workspaces: Settings \u2192 Connectors with developer mode on). It supports SSE and streaming HTTP with OAuth or no authentication, but it can't send custom headers, so it can't pass the X-Trial header or a Bearer key to x402serps.

What works today: a custom GPT Action

  1. Create a GPT → Configure → Create new action.
  2. Import the schema from https://x402serps.com/openapi.json.
  3. Authentication: API Key, Auth Type Bearer, value xs_YOUR_KEY.
  4. Save and test with "search the web for x402 protocol".

Custom MCP server (when header auth isn't needed)

Plugins → + → Add custom MCP server, Server URL https://x402serps.com/api/mcp, Authentication No authentication. ChatGPT will list the tools, but calls return an x402 payment request because ChatGPT can't attach a trial header, key or x402 payment. Use the GPT Action above, or a client that sends headers such as Codex CLI.

Developers: OpenAI Responses API

The Responses API's mcp tool does accept headers:

{
  "type": "mcp",
  "server_label": "x402serps",
  "server_url": "https://x402serps.com/api/mcp",
  "headers": {
    "Authorization": "Bearer xs_YOUR_KEY"
  },
  "require_approval": "never"
}

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

Related