canonical: https://jentic.com/apis/coldiq.com/coldiq # ColdIQ API The ColdIQ API is a unified interface to sales-prospecting and contact-enrichment providers: it runs people and company searches, enriches contacts and organizations, verifies and finds email addresses, and reports your credit balance, all behind one bearer-authenticated API. Use it to enrich leads and build prospect lists from many data sources through a single integration. ## For AI agents Search and enrich people and companies, verify and find email addresses, and check your credit balance across ColdIQ's integrated prospecting data providers. ## Scope Does not send emails, run outreach sequences, or manage a CRM. Use for ColdIQ contact search, enrichment, and email verification only. ## Capabilities - Run web and people searches through providers such as Exa, Apollo, and Findymail - Enrich a person or company record with contact and firmographic data - Verify an email address to reduce bounces before sending - Find email addresses from a name, domain, or business profile - Bulk-enrich lists of contacts in a single request - Check your remaining ColdIQ credit balance ## Use cases ### AI agent lead enrichment An AI agent takes an inbound lead, enriches the person and their company with contact and firmographic data, and verifies the email before it enters a campaign. Through Jentic the agent finds the right provider operation by intent and calls it with the stored token, without choosing among hundreds of provider-specific endpoints itself. Example prompt: Enrich the contact jane@acme.com with her job title and company, and verify the email is deliverable ### Prospect list building A sales team builds a targeted prospect list by searching people who match a job title and industry, then enriching each with a verified email. The API spans multiple search providers so the list can be assembled and deduplicated from the source with the best coverage. Example prompt: Search for heads of sales at software companies and return each with a verified work email ### Email verification at scale Before a large send, a deliverability workflow verifies every address to remove likely bounces. The API exposes verification endpoints so a batch of emails can be checked and scored, protecting sender reputation ahead of the campaign. Example prompt: Verify a list of email addresses and drop the ones flagged as likely to bounce ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/v1/me/credits` | Get the remaining credit balance | | POST | `/v1/exa/search` | Run an Exa web search | | POST | `/v1/fullenrich/contact/enrich/bulk` | Bulk-enrich contacts via FullEnrich | | POST | `/v1/findymail/verify` | Verify an email for potential bounce | | POST | `/v1/apollo/people/search` | Search people via Apollo | | POST | `/v1/limadata/enrich/person` | Enrich a person via LimaData | ## Key resources - **Search** — Run people, company, and web searches across integrated providers - **Enrichment** — Enrich a person or company, individually or in bulk, with contact and firmographic data - **Email and credits** — Verify and find email addresses and check the remaining credit balance ## Why Jentic - **Setup:** Calling the ColdIQ API by hand means holding a bearer token, choosing among hundreds of provider-specific endpoints, and normalizing each provider's response shape. Through Jentic you install once, import ColdIQ from the API Directory, store the token once, and your agent calls the operation it needs. - **Permission scoping:** You choose which of ColdIQ's operations your agent may call, so you can allow single-record enrichment and verification while leaving credit-spending bulk jobs out. Every call is logged, so an expensive bulk search the agent should not run is simply absent from its allowed set. - **Credential handling:** Your ColdIQ API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'verify an email' or 'enrich a company', and Jentic returns the matching ColdIQ operation with its input schema, so the agent picks the right provider endpoint out of hundreds without reading the reference. ## Related APIs - **Exa Search** — Neural web search and content retrieval API. - **PeopleFinders Pro** — People search and contact lookup API. - **Salesloft** — Sales engagement platform for running outreach cadences. - **Orbit** — Tracks community members and their activity. ## FAQ ### Is there a ColdIQ MCP server? You don't need an MCP server to connect your agent to the ColdIQ API. Jentic connects it directly from the API Directory: import ColdIQ, store your API token once, and your agent searches, enriches, and verifies contacts on demand. ### Can I limit what my agent is allowed to do with the ColdIQ API? Yes. Write a rule that allows only the single-record enrichment and email-verification operations, so the agent can enrich contacts without launching credit-heavy bulk jobs. You pick which of the hundreds of ColdIQ operations it may call, and every call is logged. ### What authentication does the ColdIQ API use? The ColdIQ API authenticates with a bearer token, per its OpenAPI spec. Through Jentic the token is stored once by your self-hosted instance and injected at call time, so it never reaches the agent's context. ### Can I verify an email address with the ColdIQ API? Yes. Send the email to a verification endpoint such as Findymail's verify operation, and ColdIQ returns whether it is likely to bounce. You can also find missing emails from a name and company before verifying them. ### What are the rate limits for the ColdIQ API? The OpenAPI spec does not specify rate limits. ColdIQ meters usage in credits per provider call, so check your credit balance before running large enrichment jobs. ### How do I connect the ColdIQ API to my AI agent? Search the Jentic API Directory for the ColdIQ operation you need, such as enriching a person, and import it. To run it on your own infrastructure, install Jentic One from its GitHub repo, then your agent calls the API with your token injected at execution time.