| Resource | Where it lives |
|---|---|
| Pipecorn API documentation | docs.pipecorn.com/api-reference/overview |
| Pipecorn OpenAPI spec | pipecorn.com/openapi.json |
| Pipecorn API authentication | docs.pipecorn.com/essentials/authentification |
| Pipecorn MCP server | docs.pipecorn.com/mcp/overview |
| Pipecorn CLI | docs.pipecorn.com/cli/overview |
| Pipecorn SDK | Generate a client from the OpenAPI spec |
| Docs for LLMs | docs.pipecorn.com/llms.txt |
Pipecorn API documentation
The Pipecorn REST API runs at https://app.pipecorn.com/api/v2. It gives code the same data as the app: lead and company search, waterfall enrichment of emails and mobiles, buying signals, personas and lists. The API reference documents every endpoint with its parameters and example responses, and you can send test requests from the page.
Your first request reads your credit balance. It costs nothing:
curl https://app.pipecorn.com/api/v2/credits \
-H "X-API-KEY: $PIPECORN_API_KEY"Before you build a client, read the pages on rate limits, errors and credits versus plan limits. A 402 means the credit balance is empty, and a plan limit is a separate quota that buying credits does not raise.
Pipecorn OpenAPI spec
The whole API is described in one OpenAPI 3 file at https://pipecorn.com/openapi.json. Every operation has an operationId, so you can load it into Postman, an agent framework or a code generator as it is. Synchronous enrichment on https://api.pipecorn.com/v2 has its own spec at https://pipecorn.com/openapi/sync-enrichment.json.
Pipecorn API authentication
The REST API takes an API key in the X-API-KEY header. Create a key in Settings β API keys in the app. The free plan needs no card. The authentication guide covers key management, and auth.md tells an agent which method to use on each surface.
Pipecorn MCP server
AI assistants connect to Pipecorn over the Model Context Protocol at https://mcp.pipecorn.com/mcp. Claude and ChatGPT sign in with OAuth. Claude Code, Cursor and custom clients send the API key in an X-API-Key header. The MCP documentation has the setup steps for each client and the list of tools.
Pipecorn CLI
The pipecorn command wraps the REST API for terminals, cron jobs and CI. Install it with npm install -g @pipecorn/cli or from Homebrew, then read the CLI documentation. The source is on GitHub.
Pipecorn SDK
Pipecorn does not publish a language SDK. The API is plain JSON over HTTPS, so any HTTP client works. If you want typed methods, generate a client in your language from the OpenAPI spec. This builds a TypeScript client:
npx @openapitools/openapi-generator-cli generate \
-i https://pipecorn.com/openapi.json \
-g typescript-fetch \
-o ./pipecorn-clientChange -g to python, go, ruby or java for another language. Shell scripts can use the CLI instead, and AI agents can use the MCP server.
Resources for AI agents
- pipecorn.com/llms.txt lists the pages on this site, and llms-full.txt holds the whole developer documentation in one file.
- The agent guide says which surface to use and how to avoid spending a user's credits by mistake. The same rules ship as an agent skill.
- Machine-readable discovery: the API catalog, the MCP server card and the ARD manifest.