Get customers
Answer customers
Work for you
Reach people
Give agents tools
Run and ship
Discover companies, funding rounds, investors and people; enrich contacts and read saved alerts
Use this endpoint when the requested result is a set of funding rounds, or when deal criteria must match any historical round rather than only each company's latest round. It supports round-level analysis across the full deal history. For most company-sourcing requests, prefer `POST /companies`: it returns company metadata together with the full latest deal. Its `latest_deal` filters apply only to each company's most recent round. For example, use `/companies` for "find AI companies in San Francisco whose latest round was Seed," but use `/deals` for "analyze every Seed round announced last year." Deal records contain full round details, but related companies and investors are identified by IDs instead of full entity profiles. Use `GET /company?id=...` to retrieve company metadata and `GET /deals/{id}/investors` to retrieve the full investor lineup for a returned deal. ## Request Body Structure Send a JSON body with up to 4 filter sections plus pagination/sort at the top level: - `identifiers` - Look up specific deals by UUID - `deal` - Filter by deal attributes (financing type, size, date) - `company` - Filter by company attributes (location, industry, size) - `investors` - Filter by investor participation (firms or people, by UUID)
7 fields
Use this endpoint when a deal UUID is already known and full details for that one funding round are required. The response identifies related entities by ID rather than embedding their full profiles. Use `GET /company?id=...` for company metadata and `GET /deals/{id}/investors` for the complete investor lineup.
1 field
Use this endpoint after identifying a deal when investor IDs in the deal record need to be resolved into the complete investor lineup. It returns firm investors, associated people, angel investors, lead status, and profile links for one deal. Do not use this endpoint to discover investors across many deals. Use `POST /investors` when the desired result is a list of firms, or `POST /people` with investor filters when the desired result is individual investors.
Use this endpoint when one company is already identified and its full profile and latest funding round are required. Prefer a domain or LinkedIn URL when available; they can be passed directly here without calling `/company/search` first. Use `/company/search` for fuzzy company-name resolution or an uncertain identifier. Use `POST /companies` to discover or batch-retrieve multiple companies. Provide ONE of the following query parameters to identify the company: - `id` - Company UUID - `domain` - Company domain or full URL (e.g., "stripe.com" or "https://stripe.com") - `linkedin` - LinkedIn company URL - `crunchbase` - Crunchbase organization URL The response includes the company's latest funding round details with participating investors.
4 fields
Use this endpoint when a company is already identified and its complete funding history is required. Prefer a domain or LinkedIn URL when available; it can be passed directly without first calling `/company/search`. This route retrieves history for one identified company. Use `POST /deals` instead to discover rounds across the market with deal, company, or investor filters. Provide ONE of the following query parameters to identify the company: - `id` - Company UUID - `domain` - Company domain or full URL (e.g., "stripe.com" or "https://stripe.com") - `linkedin` - LinkedIn company URL - `crunchbase` - Crunchbase organization URL The response includes the company's deals with pagination. If the identifier matches multiple companies, deals from all matches are returned.
6 fields
Use this endpoint primarily to resolve a fuzzy company name or an uncertain identifier into matching company records. If a reliable domain or LinkedIn URL is already available, skip this search and pass it directly to `GET /company` for one full profile or to `POST /companies` for a batch lookup. Exactly one parameter must be provided. **Search types:** - `name` — Fuzzy name search with relevance scoring - `domain` — Company domain or full URL - `linkedin` — LinkedIn company URL - `crunchbase` — Crunchbase organization URL Examples: - `?linkedin=https://linkedin.com/company/stripe` - `?crunchbase=https://crunchbase.com/organization/notion`
Use this endpoint by default for company sourcing and discovery. It returns company metadata such as name and domain together with the full details of each company's latest funding round. Filters inside `latest_deal` apply only to the company's most recent round. Use `POST /deals` instead when deal criteria must match any round in a company's history. For example, `/companies` is appropriate for "find AI companies in San Francisco whose latest round was Seed"; `/deals` is appropriate for "analyze all Seed rounds announced last year," regardless of whether Seed is now the company's latest round. Filters inside `investors` can match investor participation across all rounds. ## Request Body Structure Send a JSON body with up to 4 filter sections plus pagination/sort at the top level: - `identifiers` - Look up specific companies by UUID, domain, LinkedIn, or Crunchbase - `company` - Filter by company attributes (search, location, industry, size, etc.) - `latest_deal` - Filter by latest funding round attributes (type, size, date, investors) - `investors` - Filter by investors (firms or people) across all rounds
Use this endpoint when the requested result is a list of investor firms. Filters under `company_investments` identify qualifying portfolio companies and deals, then return the firms that participated in those deals. For example, use this route to find San Francisco-based investors that participated in a Seed round during the last year. Use `POST /people` with investor filters instead when the desired result is an individual angel investor or lead partner attached to a firm. Use `POST /deals` when the desired result is the matching funding rounds themselves. ## Request Body Structure Send a JSON body with up to 3 filter sections plus pagination/sort at the top level: - `identifiers` - Look up specific investors by UUID, domain, LinkedIn, or Crunchbase - `investor` - Filter by investor entity attributes (location, employee count) - `company_investments` - Filter by portfolio (industries, deal characteristics, etc.). Supports semantic search via `search_query` + `min_relevance`. When `company_investments` filters are active, `filtered_deal_count` is the number of deals that matched those filters and `filtered_lead_count` is the number of those matched deals the investor led.
Use this endpoint when one investor firm is already identified and its full profile, statistics, and portfolio summary are required. Prefer a domain or LinkedIn URL when available; it can be passed directly without calling `/investor/search` first. Use `/investor/search` for fuzzy firm-name resolution or an uncertain identifier. Use `POST /investors` to discover or batch-retrieve multiple investor firms. Provide ONE of the following query parameters to identify the investor: - `id` - Investor UUID - `domain` - Investor domain or full URL (e.g., "sequoiacap.com" or "https://sequoiacap.com") - `linkedin` - LinkedIn company URL - `crunchbase` - Crunchbase organization URL The response includes the investor's statistics, portfolio summary, and profile links.
Use this endpoint when an investor firm is already identified and its complete deal history is required. Prefer a domain or LinkedIn URL when available; it can be passed directly without calling `/investor/search` first. Use `POST /investors` instead to discover firms from investment criteria, or `POST /deals` when the desired result is a filtered list of funding rounds. Provide ONE of the following query parameters to identify the investor: - `id` - Investor UUID - `domain` - Investor domain or full URL (e.g., "sequoiacap.com" or "https://sequoiacap.com") - `linkedin` - LinkedIn company URL - `crunchbase` - Crunchbase organization URL The response includes the investor's deals with pagination. If the identifier matches multiple investors (e.g., a16z has multiple firms), deals from all matches are returned together.
Use this endpoint primarily to resolve a fuzzy investor-firm name or an uncertain identifier. If a reliable domain or LinkedIn URL is already available, skip this search and pass it directly to `GET /investor` for one full profile or to `POST /investors` for a batch lookup. Exactly one parameter must be provided. **Search types:** - `name` — Fuzzy name search with relevance scoring - `domain` — Investor domain or full URL - `linkedin` — LinkedIn company URL - `crunchbase` — Crunchbase organization URL Identifier lookups (`domain`, `linkedin`, `crunchbase`) return `relevance_score: 1`. Examples: - `?linkedin=https://linkedin.com/company/sequoia-capital` - `?crunchbase=https://crunchbase.com/organization/sequoia-capital`
Use this endpoint when the requested result is a list of people. With `person_type: company`, it returns founders, executives, or employees based on their current employer. Filters under `company.latest_deal` apply only to that employer's latest funding round, like `POST /companies`; funding information is used for filtering but is not included in the returned person record. For example, use this mode to find founders of AI companies in San Francisco whose latest round was Series A. With `person_type: investor`, it applies investment and portfolio filters in the same way that `POST /investors` does, but returns individual angel investors or lead partners attached to their firms rather than firm records. Use `POST /investors` when the desired result is firms, and `POST /deals` when it is funding rounds. ## Request Body Structure Send a JSON body with up to 4 filter sections plus pagination/sort at the top level: - `identifiers` - Look up specific people by UUID, LinkedIn, Crunchbase, or Twitter - `person` - Filter by person attributes (role, contact info, job title, education, prior employers) - `company` - Filter by current employer attributes (industry, location, funding, IPO status, etc.) - `investor` - Filter by investor activity (firm, deal characteristics, portfolio companies)
8 fields
Use this endpoint when one person is already identified and their full profile is required. Prefer a LinkedIn URL when available; it can be passed directly without calling `/person/search` first. Use `/person/search` for fuzzy name resolution or an uncertain identifier. Use `POST /people` to discover or batch-retrieve multiple people. Provide ONE of the following query parameters to identify the person: - `id` - Person UUID - `linkedin` - LinkedIn person URL - `crunchbase` - Crunchbase person URL - `twitter` - Twitter/X URL Returns the same constant unified shape as the list endpoint, with **full** employment and education history (no per-section limit).
Use this endpoint only when a verified email is explicitly required for an identified person. Return a verified email for a person identified by UUID, LinkedIn, Crunchbase, or Twitter/X. Provide one identifier. If multiple identifiers are supplied, the endpoint uses the first non-empty value in this order: `id`, `linkedin`, `crunchbase`, `twitter`. A newly created unlock costs 5 credits. Repeating the request for an email the same user already unlocked costs 0 credits. Unlock ownership persists across API keys belonging to that account. Provider attribution is internal and is not returned. Available on non-trial Pro+, Enterprise, and API plans.
Use this endpoint only when a verified phone number is explicitly required for an identified person. Return a verified phone number for a person identified by UUID, LinkedIn, Crunchbase, or Twitter/X. Provide one identifier. If multiple identifiers are supplied, the endpoint uses the first non-empty value in this order: `id`, `linkedin`, `crunchbase`, `twitter`. A newly created unlock costs 5 credits. Repeating the request for a phone number the same account already unlocked costs 0 credits. Unlock ownership persists across API keys belonging to that account. Provider attribution is internal and is not returned. Available on non-trial Pro+, Enterprise, and API plans.
Use this endpoint when a person is already identified and their investment history is required. It returns deals the person joined as an angel plus lead or firm deals. Prefer a LinkedIn URL when available; it can be passed directly without first calling `/person/search`. Provide ONE of the following query parameters to identify the person: - `id` - Person UUID - `linkedin` - LinkedIn person URL - `crunchbase` - Crunchbase person URL - `twitter` - Twitter/X URL The response includes the person's investment deals with pagination.
Use this endpoint primarily to resolve a fuzzy person name or uncertain identifier. If a reliable LinkedIn URL is already available, skip this search and pass it directly to `GET /person` for one full profile or to `POST /people` for a batch lookup. Exactly one parameter must be provided. **Search types:** - `name` — Fuzzy name search across both investors AND non-investor people (founders, employees). Returns up to 10 results. - `id` — Person UUID lookup (returns 0 or 1) - `linkedin` — LinkedIn person URL or slug - `crunchbase` — Crunchbase person URL or slug - `twitter` — Twitter/X URL or handle `person_type` on each result indicates which pool the row came from (`investor` wins when a person is in both). For full person detail, use `/person`.
Retrieve saved alert data including all deals that matched the alert criteria within the specified date range. Results include a flattened array of deals sorted by date (newest first) with duplicates removed. Available on Pro+ and Enterprise plans. This endpoint does not consume credits. **Multiple Alerts Support:** - Query multiple alerts in a single request (up to 10) - Each alert returns its own flattened deals array - Different alerts can have different frequencies (e.g., one daily, one weekly) - Successful requests report `credits_used: 0`, regardless of deal count **Important Notes:** - All alert_ids must belong to alerts you have access to - Deals are flattened from all time periods and sorted by date DESC (newest first) - Duplicate deals are automatically removed - Each deal includes AI-generated reasoning for why it matched the alert criteria - Deal structure is simplified with flattened company information for easier integration
3 fields
Retrieve all alert configurations for the authenticated user (identified by API key). Returns configuration metadata including filters, frequency, and descriptions. Available on Pro+ and Enterprise plans. This endpoint does not consume credits. **Important Notes:** - This endpoint does NOT consume usage credits (actualUsageCount: 0) - Returns only configuration metadata, not deal data - Does not require any query parameters - user is identified by API key - All configurations for the authenticated user are returned (no pagination) **Authentication:** - User identity is automatically determined from the API key - No email or user_id parameter needed **Use Cases:** - Look up what alerts are configured for the authenticated user - Retrieve alert filter settings for external integrations - Audit alert configurations programmatically
Use this endpoint to resolve a human-readable city, state, country, or region into the exact permalink required by location filters on discovery endpoints. Agents should not guess permalinks. Select the result that matches the user's intended geography, then pass its permalink to the relevant filter. The `name` parameter is required; `type` is optional. **Search types:** - `name` — Fuzzy name search with relevance scoring (required) - `type` — Optional filter by location type: `CITY`, `STATE`, `REGION`, or `COUNTRY` - `location_type` — Alias for `type` Examples: - `?name=san francisco` - `?name=california&type=STATE`
Use this endpoint before semantic search to resolve a human-readable category into an exact `INDUSTRY` or `SUPER_CATEGORY` permalink. Agents should not guess permalinks. If the taxonomy has an appropriate result, use its permalink in the structured industry filter. Use `search_query` only when the requested niche is not represented by the taxonomy. The `name` parameter is required; `type` is optional. **Search types:** - `name` — Fuzzy name search with relevance scoring (required) - `type` — Optional filter by industry type: `INDUSTRY` or `SUPER_CATEGORY` - `industry_type` — Alias for `type` Examples: - `?name=artificial intelligence` - `?name=fintech&type=INDUSTRY`
