Plan, then run
POST /v1/runs?dry_run=true returns the estimate and stores nothing. The same call without the flag spends only after you accept the cost.
REST API
The same recruitment calls over HTTP.
JSON in, JSON out. A bearer API key. A dry run spends nothing. A confirmed call spends for a result that comes back.
What the API does
Profiles and contacts
Fetch a full profile or contact details for someone a search already returned. A miss is free. The contact price is in the estimate before it runs.
Outreach accounts
Connect an account, save a sequence, and enroll people. Sends wait for confirm. The monthly price is per connected account.
Keys, confirm, replay
- Bearer keys
- Keys start with rmcp_live_. Older rapi_live_ keys still work. The secret is shown once and stored as a SHA-256 hash. Scopes limit read, spend, and send.
- Confirm
- A dry run and a preview need the read scope. Spending or sending needs the matching scope and an explicit confirm.
- Idempotency-Key
- The same key and body replay for 24 hours. A different body with that key returns 409.
A free preview
This is the homepage dry run: Senior backend engineer in Ghent, Belgium. Go, 5+ years. Target 40. The estimate is 1–120 credits and the cost is 0.
POST /v1/runs?dry_run=true
curl -sS -X POST https://api.recruitmcp.com/v1/runs?dry_run=true \
-H "authorization: Bearer $KEY" \
-d '{"job_description":"Senior backend engineer in Ghent, Belgium. Go, 5+ years.","target":40}'