Test safely
Every free workspace can create deterministic pd_test_ keys. Sandbox calls never reach Reoon and never use credits.
PeopleDat developer platform
One verification contract. Every integration path.
Use versioned REST endpoints, signed webhooks, a domain-bound browser widget, or MCP. Every path uses the same verification orchestration, credit controls, exclusions, and workspace boundary; the widget deliberately returns a coarser browser-safe result.
quickstart.sh
curl https://peopledat.com/api/v1/verifications \
-H "Authorization: Bearer pd_test_…" \
-H "Idempotency-Key: example-001" \
-H "Content-Type: application/json" \
-d '{"email":"[email protected]","mode":"power"}'Choose your integration
Four paths. One workspace boundary.
Start with the interface that fits the workflow. You can combine them without creating a second billing, result, or authorization model.
REST API
Synchronous single checks, durable 50,000-record jobs, exports, credits, usage, and a checked-in OpenAPI 3.1 contract.
Read the API referenceSigned webhooks
Receive terminal job and export events plus low-credit alerts through exact-body HMAC signatures and durable retries.
Build a receiverBrowser widget
Add origin-bound Quick verification to a form with hard caps, coarse reasons, and outage-safe fail-open behavior.
Install the widgetHosted MCP
Connect an MCP-compatible assistant to balances, jobs, estimates, results, and explicitly bounded verification tools.
Connect an MCP clientProduction-minded by default
The safeguards are part of the product.
Single and bulk verification
Run a synchronous check or submit up to 50,000 records in a durable asynchronous job. Power mode is the default.
Signed events
Receive terminal job, export, and low-credit events through registered HTTPS endpoints with raw-body HMAC signatures.
Designed for retries
Chargeable POST requests require idempotency keys. Replays return the original resource; changed payloads return a conflict.
Visible limits
Responses include request and rate-limit headers. Usage logs keep counts and billed units without retaining request bodies or raw addresses.
MCP on the same controls
The hosted Streamable HTTP endpoint uses the same key scopes, rate limits, idempotency, billing, and audit path as the REST API.
Start in the sandbox. Promote when billing is ready.
An active subscription or any settled PayGo purchase unlocks live keys, webhooks, widgets, and hosted MCP without a separate developer plan.