Crustdata API

Name: Crustdata API API
Brand: Crustdata API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany Databearer6 EndpointsREST

For Agents

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

Quickstart

Get started with Crustdata API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"enrich a company with firmographics"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Crustdata API API.

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

GET STARTED

Start building with Crustdata API API

Explore with Jentic

View OpenAPI Document

Use for: Find companies in fintech with 50-200 employees in the US, Enrich the company stripe.com with funding and headcount data, Get the headcount history for OpenAI, Search for VPs of Engineering at Series B SaaS companies

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

Jentic publishes the only available OpenAPI document for Crustdata API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Crustdata API API for, with concrete tasks.

★ 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.

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.

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.

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.

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.

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

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for crustdata api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Crustdata bearer tokens are stored encrypted in the Jentic vault. Agents never see the raw token — Jentic injects it into the Authorization header at execution time.

Intent-based discovery

Agents search Jentic by intent (e.g. 'enrich a company with firmographics') and Jentic returns the matching company-enrich or screener operation along with its parameter schema.

Time to first call

Direct integration: 4-8 hours to wire bearer auth, query body construction, and pagination. Through Jentic: minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Crunchbase Enterprise API

Larger Enterprise dataset covering organisations, IPOs, layoffs, and ownership relationships.

Pick Crunchbase Enterprise when the agent needs deeper relationship coverage (IPOs, ownership, key employee changes); choose Crustdata when the workflow is enrichment-first.

Alternative

Crunchbase API

Smaller Crunchbase v4 surface focused on entity lookup and search.

Pick the Crunchbase v4 surface when a simpler entity-lookup model is preferable to Crustdata's enrichment-oriented endpoints.

Complementary

Cruise Control API

Outbound review-request automation that benefits from enriched contact data.

Pair after Crustdata enrichment when the workflow ends in outbound messaging.

FAQs

Specific to using Crustdata API API through Jentic.

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 at https://app.jentic.com/sign-up.

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.