Crustdata for AI agents

Crustdata provides real-time company and people data for B2B sales and investing, giving teams live signals instead of static, stale contact lists. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

CRMAPI keyMCP + RESTcrustdata.com
AUDIT LOG · CRUSTDATAPOLICY: acme-support
09:41:07 · claude · u_8f2read
crustdata.search_companies_with_filters
Search companies with filters✓ allowed · 212ms
09:41:08 · claude · u_8f2read
crustdata.validate_credential
Validate API Credentials✓ allowed · 164ms
09:41:09 · claude · u_8f2write
crustdata.post_web_traffic_data
Post web traffic data✓ approved · approved by user
EVERY CRUSTDATA CALL, ON THE RECORD
01 · USE CASES

What agents do in Crustdata.

01

Search companies by criteria

Search companies matching criteria like headcount growth before building a target list.

02

Check a company's headcount trend

Fetch a company's headcount timeseries to spot hiring trends before a sales call.

03

Find decision makers at a company

Filter decision makers at a target company before starting a new outreach sequence.

02 · ACTIONS

15 Crustdata actions, graded by risk.

Every Crustdata action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

7

Look things up. Allowed by default.

  • crustdata.search_companies_with_filters
    Search companies with filters
  • crustdata.search_for_job_id_in_screener
    Search for job id in screener
  • crustdata.search_linked_in_posts_by_keyword
    Search linkedin posts by keyword
  • crustdata.validate_credential
    Validate API Credentials
  • crustdata.retrieve_linked_in_posts
    Retrieve linkedin posts
  • crustdata.fetch_investor_portfolio_data
    Find companies by investor
  • crustdata.fetch_headcount_by_facet_timeseries
    Fetch headcount by facet timeseries

write

8

Create and change things. Allow, or ask the user first.

  • crustdata.post_web_traffic_data
    Post web traffic data
  • crustdata.post_job_listings_table_data
    Search indexed job listings
  • crustdata.post_headcount_timeseries_data
    Post headcount timeseries data
  • crustdata.post_funding_milestone_time_series_data
    Post funding milestone timeseries data
  • crustdata.enrich_person_screener
    Enrich person screener
  • crustdata.filter_decision_makers_data
    Filter decision makers data
  • crustdata.screener_company_information
    Screener company information
  • crustdata.screen_metrics_and_filter_conditions
    Screen metrics and filter conditions

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

Crustdata in three steps.

  1. 01Your users connect CrustdataThey add their Crustdata api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “post web traffic data” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Crustdata through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('crustdata', {
  read: 'allow',
  write: 'ask',        // post_web_traffic_data
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Crustdata connects.

Users add their Crustdata api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Crustdata connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Crustdata from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Crustdata and Arc0, answered.

Q01

Can I use Crustdata with Claude, ChatGPT or Cursor?

Yes. Connect Crustdata to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Crustdata actions you allow.

Q02

How do users connect Crustdata?

Users add their Crustdata api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Crustdata actions can my agent take?

15 in total: 7 read, 8 write and 0 destructive, such as “post web traffic data”. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Crustdata?

Yes. Allow read actions and deny writes in the Crustdata policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Crustdata too?

Yes. The same Crustdata connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Crustdata into your agent.

Your users connect Crustdata once, under your brand. Your agent gets 15 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan