Revcenter API - Revcenter API

The Revcenter API finds people and companies, enriches them, and pushes them into outbound sequences. Everything the product does is available over HTTP.

curl https://api.revcenter.ai/v1/data/search/web \
  -H "Authorization: Bearer $REVCENTER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "query": "site:linkedin.com/in wealth advisor San Jose CFP", "num": 10 }'

Two surfaces, one host

Everything lives on https://api.revcenter.ai. Which prefix you call determines how you authenticate.

/v1 — API keys

Bearer-token endpoints for your own software, agents, and MCP tools. Scoped keys, per-key rate limits, metered per request. No cookies, no browser.

/api — workspace session

The endpoints the Revcenter app itself runs on. Authenticated by a signed-in workspace session, scoped to that session’s active workspace.

Both are documented here, and every endpoint page states which one it uses. The practical split: /v1 is raw data acquisition, /api is the product — running searches, scoring results, and launching campaigns.

Campaigns are currently /api only. There are no bearer-token campaign endpoints yet.

What you can do

Search

Query the web directly, or run a full Revcenter search: a brief in, scored and ranked people out, exportable and shareable.

People

Search people, enrich a profile to its full record, and browse the deduplicated contact pool your searches have built up.

Companies

Search companies, enrich one to its full record, and read the org chart Revcenter has assembled for it.

Campaigns

Turn a shortlist into an outbound sequence on Smartlead or HeyReach — planned, reviewed, published, then explicitly launched.

Response shape

Every /v1 endpoint returns the same envelope. Data goes in data, everything else in meta.

{
  "data": {},
  "meta": {
    "request_id": "6f1c2b7e-9a3d-4c5f-8e21-0b7d4a9c1e33",
    "usage": {
      "operation": "data.people.profile",
      "acquisition_units": 10000,
      "billable_units": 10000,
      "funding_source": "platform"
    }
  }
}

meta.usage is present on billed endpoints, so you always know what a call cost at the moment it returns. See Metering. The /api endpoints return their payload directly, without an envelope — they were built for the app’s own UI. Their error shape is flatter too; both are documented in Errors.

Long-running work

Searches and campaigns do not block. POST /api/scans, POST /api/bulk, and the campaign publish endpoints all return an ID immediately and keep working in the background. Poll the corresponding GET endpoint for status. A search that produced results finishes complete even if a later stage errored — partial results are never discarded.

Agents and MCP

The /v1 API is built to be wrapped as tools: bearer auth, scoped keys, JSON bodies, deterministic paths, structured responses, a request ID on everything, and usage reported inline. It is not itself an MCP server — wrap these endpoints as tools like web_search, people_search, person_enrich, and company_enrich.

Get authenticated

Provision a key, pick scopes, and understand rate limits.

​Two surfaces, one host

/v1 — API keys

/api — workspace session

​What you can do

Search

People

Companies

Campaigns

​Response shape

​Long-running work

​Agents and MCP

Get authenticated

Two surfaces, one host

What you can do

Response shape

Long-running work

Agents and MCP