Microsoft Copilot
Beta status
During the beta, FindIP officially supports the Claude connection only. This guide is provided for reference and this integration will be officially supported soon. For the smoothest experience right now, use Claude Desktop.
In Microsoft 365 Copilot environments, register the FindIP REST API as a Copilot Studio custom connector and your enterprise users can run patent searches in natural language right inside their internal Copilot.
Prerequisites
Microsoft 365 Copilot + Copilot Studio licenses. You'll need admin permissions to register custom connectors, plus a FindIP API key. For enterprise rollout, we recommend reaching out via Enterprise inquiry.
Setup steps
Power Platform → Custom connectors
make.powerapps.com → in the left nav, Custom connectors → New custom connector → Create from blank.
Enter basic info
Host = api.findip.ai, Base URL = /api/v1, Scheme = HTTPS.
Configure authentication
Authentication type = API Key, Parameter label = X-API-Key, Parameter name = X-API-Key, Location = Header.
Define the action
Operation ID = SemanticSearch, POST /search/semantic, define query / top_k in the request body.
Register as a Copilot Studio tool
Copilot Studio → select your Copilot → Actions → Add → Connector → add the FindIP connector you just built. Describing the tool as "Semantic patent search across KR/US/JP/CN/EP" enables automatic routing.
Sample prompt
Prompt
"We're evaluating a new wireless-charging module for launch. Summarize the live, in-force patents in similar areas registered in Korea and the US over the past 5 years."
Troubleshooting
Can we issue per-user API keys?
Switching to OAuth 2.0 lets you issue per-user tokens. We provide a separate OAuth issuance guide for Enterprise plans.