People Search - Crustdata v3 (legacy)

Find up to 100 professional profiles by company domain and title keywords. Supply a company domain and a title keywords and optionally set a country. Use it for account research or company due diligence. The POST request schema also lists fields, max_items, summary. Use the results to organize a research workflow and cross-check the relevant source records.

Selected price
$0.144 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
body*object

body

Find up to 100 professional profiles by company domain and title keywords.
Optional parameters (6)
Optional. Comma-separated keys (dotted paths like `author.name` descend into nested objects) to keep on each result item: each row of the API's result list, or the `data` object itself for an API that returns one record. Keys are matched relative to that item, not against the top-level response envelope, so use `jq` to reshape the whole envelope. Shrinks the response without changing cost.
Optional. Cap the number of result rows returned; a `_truncated` note reports how many were withheld so you can page via the API's own `limit`. An API that returns one record is not trimmed. Does not change cost.
Optional. Return only a structural outline (top-level keys, item counts, and per-field byte sizes) instead of the full data. Does not change cost.
Optional. A jq expression applied to the result envelope; its output replaces `output` (multiple outputs collect into an array). Reshape freely, e.g. `jq=.data | {title, description, md: .markdown[:3500]}`. Runs sandboxed with a 250ms / 2MB budget; on failure the full result is returned with a `jqError`. Does not change cost.
Optional. The most you are willing to pay for this one request, in US dollars (for example 0.05). Any route that would charge more than this is not used, so a request only ever runs on something you can afford. If nothing is available at or below your amount, the request is refused before it runs, nothing is charged, and the message tells you the cheapest price per request so you can raise it. Leave it out to accept the normal price.
Optional wallet idempotency key, scoped to this customer for 24 hours. When the gateway honors the key, this synchronous in-process execution can continue after the caller disconnects, bounded by its execution deadline. A completed replayable result charges normally exactly once and can be replayed without another provider run or charge. A pending duplicate returns 409 idempotency_in_progress; reuse with different request semantics returns 409 idempotency_conflict.

Sample response

{
  "output": {
    "data": {
      "hasMore": true,
      "profiles": [
        {
          "certifications": [
            {
              "issuedUtc": 1609459200,
              "issuer": "Amazon Web Services",
              "name": "AWS Certified Solutions Architect"
            }
          ],
          "city": "San Francisco",
          "connectionCount": 2340,
          "continent": "North America",
          "country": "United States",
          "currentEmployers": [
            {
              "businessEmailVerified": true,
              "companyDomain": "notion.so",
              "companyHeadcount": 700,
              "companyHeadcountRange": "501-1000",
              "companyHeadquartersCountry": "United States",
              "companyHqLocation": "San Francisco, California, United States",
              "companyId": "crd3_co_5510",
              "companyIndustry": "Software Development",
              "companyLinkedinUrl": "https://www.linkedin.com/company/notionhq",
              "companyName": "Notion",
              "companyWebsite": "https://notion.so",
              "description": "Own the sync and offline conflict-resolution layer.",
              "employmentType": "Full-time",
              "functionCategory": "Engineering",
              "location": "San Francisco, CA",
              "primaryEmployer": true,
              "seniority": "Senior",
              "startUtc": 1625097600,
              "title": "Senior Software Engineer, Infrastructure",
              "yearsAtCompany": 4,
              "yearsAtCompanyRange": "3 to 5 years"
            }
          ],
          "emails": [
            "[email protected]"
          ],
          "firstName": "Jonah",
          "flagshipProfileUrl": "https://www.linkedin.com/in/jonahwhitfield/",
          "followerCount": 2890,
          "headline": "Senior Software Engineer, Infrastructure at Notion",
          "image": "https://media.licdn.com/dms/image/crd3_pr_774102.jpg",
          "indexedUtc": 1758758460,
          "languages": [
            "English"
          ],
          "lastName": "Whitfield",
          "linkedinUrl": "https://www.linkedin.com/in/jonahwhitfield/",
          "name": "Jonah Whitfield",
          "pastEmployers": [
            {
              "companyDomain": "segment.com",
              "companyId": "crd3_co_1180",
              "companyName": "Segment",
              "endUtc": 1624406400,
              "functionCategory": "Engineering",
              "location": "San Francisco, CA",
              "seniority": "Mid-Senior",
              "startUtc": 1483228800,
              "title": "Software Engineer"
            }
          ],
          "personId": "crd3_pr_774102",
          "profileLanguage": "en",
          "profilePictureUrl": "https://media.licdn.com/dms/image/jonah-full.jpg?e=1759449600",
          "recentlyChangedJobs": false,
          "recordUpdatedUtc": 1758758400,
          "region": "San Francisco Bay Area",
          "skills": [
            "Distributed Systems",
            "Go",
            "PostgreSQL",
            "System Design"
          ],
          "state": "California",
          "summary": "Building the sync engine that keeps Notion's blocks consistent across clients. Previously at Segment.",
          "twitterHandle": "jonahbuilds",
          "updatedUtc": 1758758400,
          "yearsOfExperience": 9,
          "yearsOfExperienceRange": "More than 8 years"
        },
        {
          "city": "New York",
          "continent": "North America",
          "country": "United States",
          "currentEmployers": [
            {
              "companyDomain": "notion.so",
              "companyId": "crd3_co_5510",
              "companyName": "Notion",
              "location": "New York, NY",
              "primaryEmployer": true,
              "seniority": "Senior",
              "startUtc": 1640995200,
              "title": "Senior Software Engineer, Editor"
            }
          ],
          "firstName": "Sara",
          "headline": "Senior Software Engineer, Editor at Notion",
          "lastName": "Lindqvist",
          "linkedinUrl": "https://www.linkedin.com/in/saralindqvist/",
          "name": "Sara Lindqvist",
          "personId": "crd3_pr_662310",
          "recordUpdatedUtc": 1758672000,
          "region": "New York City Metropolitan Area",
          "skills": [
            "TypeScript",
            "React",
            "Rich Text Editing"
          ],
          "state": "New York",
          "yearsOfExperience": 7,
          "yearsOfExperienceRange": "5 to 8 years"
        },
        {
          "city": "Seattle",
          "continent": "North America",
          "country": "United States",
          "currentEmployers": [
            {
              "companyDomain": "notion.so",
              "companyId": "crd3_co_5510",
              "companyName": "Notion",
              "location": "Seattle, WA",
              "primaryEmployer": true,
              "seniority": "Senior",
              "startUtc": 1651363200,
              "title": "Senior Software Engineer, Growth"
            }
          ],
          "firstName": "Tobias",
          "headline": "Senior Software Engineer, Growth at Notion",
          "lastName": "Reyes",
          "linkedinUrl": "https://www.linkedin.com/in/tobiasreyes/",
          "name": "Tobias Reyes",
          "personId": "crd3_pr_990237",
          "recordUpdatedUtc": 1758585600,
          "region": "Seattle Metropolitan Area",
          "skills": [
            "Python",
            "Experimentation",
            "SQL"
          ],
          "state": "Washington",
          "yearsOfExperience": 6
        }
      ],
      "totalCount": 22
    },
    "found": true
  }
}

Response result

Response structure

Inferred from examples
  • outputobject
    • dataobject
      • hasMoreboolean
      • profilesobject[]
        • certificationsobject[]
          • issuedUtcinteger
          • issuerstring
          • namestring
        • citystring
        • connectionCountinteger
        • continentstring
        • countrystring
        • currentEmployersobject[]
          • businessEmailVerifiedboolean
          • companyDomainstring
          • companyHeadcountinteger
          • companyHeadcountRangestring
          • companyHeadquartersCountrystring
          • companyHqLocationstring
          • companyIdstring
          • companyIndustrystring
          • companyLinkedinUrlstring
          • companyNamestring
          • companyWebsitestring
          • descriptionstring
          • employmentTypestring
          • functionCategorystring
          • locationstring
          • primaryEmployerboolean
          • senioritystring
          • startUtcinteger
          • titlestring
          • yearsAtCompanyinteger
          • yearsAtCompanyRangestring
        • emailsstring[]
        • firstNamestring
        • flagshipProfileUrlstring
        • followerCountinteger
        • headlinestring
        • imagestring
        • indexedUtcinteger
        • languagesstring[]
        • lastNamestring
        • linkedinUrlstring
        • namestring
        • pastEmployersobject[]
          • companyDomainstring
          • companyIdstring
          • companyNamestring
          • endUtcinteger
          • functionCategorystring
          • locationstring
          • senioritystring
          • startUtcinteger
          • titlestring
        • personIdstring
        • profileLanguagestring
        • profilePictureUrlstring
        • recentlyChangedJobsboolean
        • recordUpdatedUtcinteger
        • regionstring
        • skillsstring[]
        • statestring
        • summarystring
        • twitterHandlestring
        • updatedUtcinteger
        • yearsOfExperienceinteger
        • yearsOfExperienceRangestring
      • totalCountinteger
    • foundboolean

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use People Search - Crustdata v3 (legacy) with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.