Fusion developer access

Trace data in your workflow.

Send an identifying field, receive a job ID, then retrieve your result with its source verdicts. This console calls the deployed API. It uses your Quarry API key and existing Quarry credits and does not simulate a successful lookup.

From the demo to your first real trace

Sign in to Quarry using the organization that will own your lists, jobs and credits.
Check your available credits. If you need more, choose a one-time pack: 100 for $49, 500 for $199, or 2,000 for $699. Wait for the purchase to appear in your balance before continuing.
Read and accept the use policy in Settings. This is required before a real trace can start.
Create and copy your Quarry API key, then return here and paste it into the workspace. New keys need paid access and available credits.

An existing key and balance can be reused. No separate Trace purchase is required. The guest demo uses fictional records; those records do not become a paid research list. A running trace reserves a credit, and a successful contact match consumes it. An unresolved request can retain its reservation until reconciled.

Need help with a saved job or interrupted upload? Include the job or list ID and what happened, without your API key.

Live request console

Your Quarry API key (uses your existing Quarry credits)

City (recommended)State (recommended)

Add location to distinguish people with the same name. A returned candidate is not proof of identity; inspect its evidence before use.

I am authorized to research this target. This runs a real metered API request.

Recover an existing Quarry job

The job reference stays in this page link after a successful request. Save the link, then re-enter your key to retrieve the owned result after reopening. Keys and research inputs are never saved.

Connect your application

POST /api/quarry/trace
Authorization: Bearer YOUR_QUARRY_API_KEY
Content-Type: application/json

{"company":"Your authorized research target"}

A successful request returns HTTP 202 with a jobId. Check its status through GET /api/quarry/trace?job=JOB_ID using the same key. Results and credit charges belong to your Quarry organization.

HTTP 401 means access is missing; 429 includes retry-after; 503 means a dependency or provisioning is unavailable. Source verdicts are research evidence, not a guarantee that a person or contact is correct.

Buy a Quarry credit pack and accept its acceptable-use policy, then create a scoped key in your account. Packs contain 100 trace credits for $49, 500 for $199, or 2,000 for $699. This console uses the same Quarry balance; no separate Trace purchase is required. HTTP 403 aup_required means the policy must be accepted in Quarry first.

Each organization can hold up to five active API keys. Property and list calls use request limits rather than trace credits: 120 requests per minute and 10,000 per UTC day across its keys. A successful trace hit uses one credit. You can retrieve your owned past results after the trace balance reaches zero. API keys cannot manage billing, other keys or outbound messages.

Create your scoped API key