DocsDeveloper guide

Developer guide

For developers embedding FindIP into their own service or self-hosting an MCP server in a custom LLM environment. If you're a regular user connecting Claude / ChatGPT / Gemini, start with the AI connect guide.

Embed the REST API in your service

Use this when you're integrating search into an environment that doesn't support MCP — web apps, mobile apps, internal tools. Just put your API key in an HTTP header.

1. Issue an API key

Issue one for free in the dashboard.

2. Endpoint reference

Semantic search, stats, and auth endpoint reference.

cURL
# Semantic search example
curl -X POST https://api.findip.ai/api/v1/search/semantic \
-H "X-API-Key: psk_live_..." \
-H "Content-Type: application/json" \
-d '{
  "query": "solid electrolytes that suppress lithium-dendrite growth",
  "top_k": 5
}'

Custom MCP hosting

The FindIP MCP server is Node.js-based and supports two hosting modes.

  • NPM package (stdio): Inject the CLI directly into your local desktop app's settings. Requires the API key as an env var.
  • SSE / Streamable HTTP endpoint: For web services or distributed environments where multiple agents share a single MCP server. Auth via OAuth or API key.

NPM package (stdio)

# Global install
npm install -g @findip/patent-search-mcp

# Run directly
FINDIP_API_KEY=psk_live_... npx @findip/patent-search-mcp

Claude Desktop custom config

{
"mcpServers": {
  "findip-mcp": {
    "command": "npx",
    "args": ["-y", "@findip/patent-search-mcp"],
    "env": {
      "FINDIP_API_KEY": "psk_live_..."
    }
  }
}
}

Note

The @findip/patent-search-mcp NPM package is currently in private beta. Until the official release we recommend the remote SSE URL (https://api.findip.ai/mcp).

See also

FindIP — Semantic Patent Search