canonical: https://jentic.com/apis/crustdata.com/crustdata

# Crustdata API

Jentic publishes the only available OpenAPI specification for Crustdata API, keeping it validated and agent-ready. Crustdata provides company and people data enrichment and search through six POST endpoints: search and enrich for companies, headcount lookup, search and enrich for people, and a combined screener for filtering companies by criteria. Authentication uses a bearer token issued by Crustdata.

## For AI agents

Search and enrich company and people records, plus pull company headcount and screening data, through Crustdata's six-endpoint API.

## Scope

Does not handle CRM record creation, outbound messaging, or financial transaction execution - use for company and people search and enrichment only.

## Capabilities

- Search companies with structured filters via POST `/screener/company/search`
- Enrich a company record with firmographics, funding, and headcount data
- Pull historical and current headcount snapshots for a target company
- Search people with filters such as title, seniority, and company
- Enrich a person record with contact and professional details
- Run combined company screening that returns ranked results matching multiple criteria

## Use cases

### ICP-Driven Account Discovery

Discover net-new accounts that match a defined ideal customer profile by POSTing filter criteria to `/screener/screen` and `/screener/company/search`, then enriching each result with firmographics and headcount before handing the list to outbound sales.

Example prompt: POST `/screener/screen` with industry=SaaS, employee_count_min=50, employee_count_max=200, region=US, then POST `/screener/company/enrich` for each result to attach firmographics.

### Headcount Trend Monitoring

Watch hiring or attrition trends at target accounts by polling `/screener/company/headcount` on a cadence and surfacing month-over-month deltas. Useful for sales triggers ('they're hiring fast') and competitive intelligence.

Example prompt: POST `/screener/company/headcount` weekly for each target account and alert when month-over-month change exceeds 5%.

### Lead Enrichment for Outbound

Take a list of leads (names plus company or LinkedIn URLs) and run them through `/screener/people/enrich` to attach title, seniority, and contact data. Combine with company enrichment for full account context before personalising outreach.

Example prompt: POST `/screener/people/enrich` with each lead's identifier, then POST `/screener/company/enrich` for the linked company to assemble a full enriched lead record.

### Recruiter Talent Search

Search for candidates by title, seniority, and company filters via `/screener/people/search` to surface a passive talent pipeline, then enrich the best matches with `/screener/people/enrich` before reaching out.

Example prompt: POST `/screener/people/search` filtered by title='VP of Engineering' and company_employee_count_min=200, then enrich the top 25 results.

### Agent-Driven Account Research

Allow an AI sales-research agent to answer questions like 'find ten Series B fintechs in EMEA hiring engineers' by chaining screen, search, and enrich calls through Jentic so the bearer token stays in the vault.

Example prompt: Search Jentic for 'find companies matching my ICP', load the screener-screen operation, and execute it with the configured filter body.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/screener/company/search` | Search companies by filters |
| POST | `/screener/company/enrich` | Enrich a company record |
| POST | `/screener/company/headcount` | Get company headcount data |
| POST | `/screener/people/search` | Search people by filters |
| POST | `/screener/people/enrich` | Enrich a person record |
| POST | `/screener/screen` | Run multi-criteria company screening |

## Key resources

- **Company** — Search, enrich, and pull headcount data for company records.
- **People** — Search and enrich person records by filters or identifiers.
- **Screening** — Combined screening endpoint that returns ranked company matches against multi-criteria filters.

## Why Jentic

- **Setup:** Wiring the Crustdata API by hand means setting its bearer auth and building the POST bodies for company and people search, enrichment, and headcount yourself. Through Jentic you install once, import the Crustdata API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Crustdata passes its screener targets in the request body rather than the URL path, so limit the agent to the operations it needs, such as company enrichment or people search. You choose the operations it may call, so headcount or broad screener queries are not included unless you add them.
- **Credential handling:** Your Crustdata bearer token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'enrich a company with firmographics' or 'search for people', and Jentic returns the matching Crustdata operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Crunchbase Enterprise API** — Larger Enterprise dataset covering organisations, IPOs, layoffs, and ownership relationships.
- **Crunchbase API** — Smaller Crunchbase v4 surface focused on entity lookup and search.
- **Cruise Control API** — Outbound review-request automation that benefits from enriched contact data.

## FAQ

### Why is there no official OpenAPI spec for Crustdata API?

Crustdata does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Crustdata API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Crustdata API use?

The API uses HTTP bearer authentication. The token is issued from your Crustdata account. Through Jentic the token is held in the encrypted vault so the agent never receives its raw value.

### Can I screen companies against an ICP with the Crustdata API?

Yes. POST `/screener/screen` accepts a multi-criteria filter body and returns ranked matching companies. Combine with POST `/screener/company/enrich` to attach firmographics to each result.

### How do I track company headcount over time through the Crustdata API?

POST `/screener/company/headcount` with the company identifier returns headcount snapshots. Polling on a weekly cadence and diffing the values yields a hiring-trend signal for outbound or competitive analysis.

### What are the rate limits for the Crustdata API?

The OpenAPI specification does not document numeric rate limits. Watch for HTTP 429 responses and confirm your contract limits with Crustdata support before running large enrichment batches.

### How do I enrich a company through Jentic?

Run pip install jentic, search 'enrich a company with firmographics', load the company-enrich operation, and execute it with the company domain or identifier. Jentic injects the bearer token automatically.

### Can I limit what my agent is allowed to do with the Crustdata API?

Yes. Because you run Jentic One yourself, you decide which Crustdata operations the agent may call, so you can grant it just company enrichment or people search while withholding the headcount and broad screener endpoints. Since Crustdata passes its screener targets in the request body rather than the URL path, scoping is done at the operation level: an operation the agent has not been given is simply unavailable to it. Your bearer token is held by your own instance and injected at execution time, so the agent can only reach the endpoints your rules permit.