Quickstart

Agents: the full documentation index is at /llms.txt.

The revcenter CLI and MCP server are coming soon. Until they are published, use the API as shown here; everything they do, the API does.

Get a key

In Revcenter, open Settings → Usage → API and choose Create key. Name it and pick an expiry (30, 90 or 365 days). Copy the key when it is shown; it is shown once. Only workspace admins can create keys, and only in a workspace with API access and an active plan.

export REVCENTER_API_KEY="<your key>"

Check it

curl -s https://api.revcenter.ai/v1/projects -H "Authorization: Bearer $REVCENTER_API_KEY"

You get {"data": [...]} with your workspace’s projects. A 401 means the key is wrong or expired; see errors.

Make a project

curl -s -X POST https://api.revcenter.ai/v1/projects \
  -H "Authorization: Bearer $REVCENTER_API_KEY" -H "Content-Type: application/json" \
  -d '{"name": "Plant Maintenance Manager, Lancaster PA"}'

{
  "data": { "id": "6a1e0c52-…", "name": "Plant Maintenance Manager, Lancaster PA", "created_at": "2026-10-16T14:02:11.000Z", "archived": false, "searches": 0, "shortlisted": 0 },
  "meta": { "request_id": "…" }
}

Launch a search

curl -s -X POST https://api.revcenter.ai/v1/projects/<project_id>/searches \
  -H "Authorization: Bearer $REVCENTER_API_KEY" -H "Content-Type: application/json" \
  -H "Idempotency-Key: lancaster-maint-0001" \
  -d '{"criteria": {"title_variants": ["Plant Maintenance Manager", "Maintenance Manager"], "metro": "Lancaster, PA"}}'

This uses one shortlist credit and answers 202 with a search_id. Sending the same request with the same Idempotency-Key again returns the same search and uses nothing more; see idempotency keys.

Wait for it

curl -s https://api.revcenter.ai/v1/searches/<search_id> -H "Authorization: Bearer $REVCENTER_API_KEY"

Repeat every 10 to 30 seconds until status is no longer queued or running; a typical search takes a few minutes. A finished search has an outcome: Shortlist ready, Poor yield or No results. See async jobs.

Read the results

curl -s "https://api.revcenter.ai/v1/searches/<search_id>/people?min_score=80" -H "Authorization: Bearer $REVCENTER_API_KEY"
curl -s https://api.revcenter.ai/v1/projects/<project_id>/shortlist.csv -H "Authorization: Bearer $REVCENTER_API_KEY" -o shortlist.csv

Neither uses credits. Each person comes with their score, how they fit each criterion, and their full profile. Long lists page with limit and offset; see pagination.

The backend job recipe does all of this from a script, safely retried.
Criteria explains which fields filter LinkedIn and which only score.
Every endpoint is in the API reference.

Get started

Concepts

Tools

Guides

Recipes

Use cases

API reference

Next

​Next

Next