as_of timestamp and an informational-use notice.
Three ways to use it
Build with the API
Call the endpoints from your app or your own AI assistant.
Connect over MCP
Connect Claude, ChatGPT, Cursor or any MCP client and sign in.
Add the agent skill
Teach Claude Code, Codex or Cursor to use PartFinder. No code.
Developer guides
Research a part
Risk score, supply and lead times, datasheet, disruptions and alternates for one part number.
Find alternate parts
Parts that could replace one part, each with its own current supply.
Search for parts
A part number or a description in; the part and comparable parts out, with specs and stock.
Compare parts
Parts side by side on their datasheet specifications, with a verdict per specification and stock.
Analyze a BOM
Send a parts list or a CSV/XLSX file and get a risk report for every line.
Track supply-chain disruptions
Current events by country, region and category, and shipping conditions at ports and sea routes.
Request a quote
Email a supplier, read their reply with the quote laid out, and answer in the same thread.
Get notified
Signed webhooks when a supplier replies, an email bounces, or a search or a comparison ends.
Serve your own customers
A key for each of your customers. Each one sees only its own requests for quote, BOMs, searches and comparisons.
Build PartFinder into your own assistant
Give your product’s own AI assistant these endpoints as tools.
API Reference
Every endpoint with its parameters and response schemas.
API keys are created in the PartFinder Console. Keys belong to an organization, not a person. They keep working when team members change.