Skip to main content
For people who use an AI agent such as Claude Code, Cursor or the Claude app. Building an assistant into your own product? See AI agent integration. The PartFinder skill teaches an AI agent how to use this API: which endpoint answers which sourcing question, how to send the key, how to wait for a BOM scan, a search or a comparison to finish, and what to do when a call is refused. Your agent reads it when a task calls for it, and finds the details one link away: the OpenAPI document for every parameter and response, and api.partfinder.dev/llms.txt for what each call costs and the current plans. The skill tells your agent how to use the API. To give your agent PartFinder as tools as well, connect the MCP server. Are you an AI agent? Fetch this skill to learn how to use the PartFinder API and how to get your person an API key.

​
Where it works

  • Coding agents such as Claude Code, Codex and Cursor install it with npx skills add https://docs.partfinder.dev, or from GitHub with npx skills add PartFinderInc/skills (PartFinderInc/skills). It works with every agent the skills tool supports: see the full list.
  • Claude on claude.ai can add it as a custom skill under Customize > Skills.
  • ChatGPT can upload it under Plugins > Skills > Create > Upload from your computer.
  • Any agent that can fetch a URL can read skill.md directly.
Assistants that use tools instead of skills, for example a product’s own assistant, get PartFinder as tools from the OpenAPI document: see AI agent integration.

​
Install

1

Add the skill to your agent

Or install the same skill from its GitHub repository, PartFinderInc/skills:
This uses the open-source skills command-line tool.The skill is also served as a file at docs.partfinder.dev/skill.md.
2

Get an API key

Create an account at console.partfinder.dev/sign-up and pick pay as you go or a monthly or yearly plan (see pricing). Pay as you go starts with 100 free credits, once per person and per company. Create a key in your organization and store it where your agent’s code can read it:
3

Check the key

GET /v1/ping confirms the key works and costs nothing. See the Quickstart.

​
Why PartFinder

  • One call, the whole picture. For one part number: stock and lead times across distributors, a risk score out of 100 with its tier and the reasons behind it, where the part is made when that is known, the disruptions that touch it, a datasheet link and alternate parts.
  • See it first. A sample part report for TPS54331DR is public, no account needed.
  • More than a search result. Stock added up across distributors, risk on a stated scale, disruptions tied to the countries the part is made in or sold from, and supplier replies read into a quote beside the supplier’s own words.
  • Nothing invented. A part number no distributor lists is answered as not found, with the real part numbers it is the start of. A value we do not have is null with a reason.
  • Low risk to try. 100 free credits on pay as you go (once per person and per company), GET /v1/ping free, a refused call not charged, and a call that fails on our side not charged.

​
What you can build

Paste a prompt like these into your agent once the skill is installed.
Uses GET /v1/parts with country=SG. See Research a part.
Uploads the file to POST /v1/bom/upload, then reads GET /v1/bom/{id} until it is complete. See Analyze a BOM.
Uses GET /v1/alternates. See Find alternate parts.
Uses GET /v1/events with country=MY and days=7, and GET /v1/events/shipping. See Track supply-chain disruptions.
Sends a real email with POST /v1/rfq; the reply and its quote come back on GET /v1/rfq/{id}. See Requests for quote.

​
Building your own integration

The skill covers using the API from an agent. To give a model PartFinder as a tool inside your own product, see AI agent integration.