Skip to content
Delivr.ai

Resolution API: pure usage-based, no minimums

One API call. Anonymous visitor to named buyer.

Half the visitors you pay to acquire show up as "Unknown." Resolve them to verified people, with 22,000+ intent topics and post-cookie IDs attached, and pay only per successful resolution. No minimums, no setup fees, no annual prepay.

Request API access

Pay per resolution · $0 monthly minimum · Volume rates fall automatically · Read the docs

GET /api/v1/lookup
curl "https://api.delivr.ai/api/v1/lookup?email=jane@acme.com" \
  -H "X-Api-Key: $DELIVR_API_KEY" \
  -H "X-Api-Secret: $DELIVR_API_SECRET"
# Plain text, normalized and hashed server-side.
200 OK
{
  "first_name": "Jane",
  "last_name": "Rivera",
  "job_title": "VP, Growth Marketing",
  "seniority_level": "vp",
  "department": "marketing",
  "company_name": "Acme",
  "company_domain": "acme.com"
}
200 = one metered resolution. 404 = no match, free.
$0
monthly minimum

pay per resolution

50%+
traffic resolved

measured on US web traffic

100%
deterministic

no modeled matches

22K+
intent topics

scored per person

Enter your work email and we'll show you the topics we see you researching. Real data, straight from the API you'd be buying.

Partners

  • UID2
  • LiveRamp
  • The Trade Desk
  • IAB Tech Lab
  • Google Cloud
  • Amazon Web Services

Zero risk by design

The meter is the whole deal

No floor to clear, no setup fee to amortize. Your bill is the resolutions you ran, and your rate falls automatically as volume grows.

$0 minimums

Start with one campaign’s traffic or one landing page. There is no monthly floor and no platform fee. If you resolve nothing, you pay nothing.

No setup fees, no seat licenses

Sign the usage agreement, request API access, and send your first call the same day. The only line item on your invoice is usage.

Volume pricing that reprices everything

When monthly volume reaches a cheaper bracket, every resolution that month bills at the lower rate, not just the marginal ones. Scale is rewarded, never penalized.

For performance teams

Stop paying to advertise to "Unknown"

Every resolved visitor moves budget from spray-and-pray to a person you can name, score, suppress, and activate. All deterministic, no modeled guesswork.

01

Rebuild retargeting on people, not cookies

Browser restrictions on third-party cookies have shrunk remarketing pools. Our first-party pixel cookie resolves to a verified hashed email and a full person record, so the traffic you already paid to acquire stays targetable instead of going dark. 50%+ of US traffic, resolved deterministically.

cookiehemprofile
02

Spend against intent, not impressions

Every resolved person carries 22,000+ scored intent topics. Bid up the in-market segment, suppress existing customers and low-intent traffic, and route high-intent visitors to sales while they are still on the site.

hemprofile
03

Activate where cookies can’t go

Resolved emails generate UID2 tokens deterministically, 4.0B of them, alongside 1.4B mobile ad IDs and 280M CTV device IDs. Push first-party audiences to The Trade Desk and any UID2-enabled DSP without a third-party cookie in the chain.

hemuid2
04

Qualify the B2B click before you pay for the next one

Reverse-IP maps visitor traffic to 103M company records with firmographics and technographics. Build ABM target lists from real site activity, and stop bidding on traffic from accounts you would never sell to.

ipaccount

New on your API key

Off-domain intent and audiences: same endpoint, same key

Resolution tells you who landed. Off-domain intent tells you who is in-market across the open web, scored per person, before they ever hit your site. The same API key now opens our off-domain person-based intent and audience-configuration endpoints, so you can bid on real demand instead of waiting for the visit.

POST/v1/intent

Person-level off-domain intent

Send a resolved person or hashed email and get 22,000+ topics scored 0–100 with an up/down/static trend, measured against that individual’s own baseline, not pooled at the account. Signals are distilled from ~1 trillion daily impressions across publisher co-ops, the bid-stream, and content consumption, then resolved deterministically to the person.

POST/v1/audiences

Audience configuration

Configure an audience in one call: pick intent topics, score thresholds, firmographics, and recency. Every member resolves deterministically and refreshes daily, then activates on The Trade Desk, LiveRamp, DV360, Meta, and Customer.io, no list export, no second platform.

GET/v1/topics

Topic taxonomy

Pull the full 22,000+ topic taxonomy programmatically, or request a custom topic and have it scored and live within 24 hours.

Where this connects

Off-domain intent is person-level and resolved deterministically, no account-level inference, no device fingerprinting. LinkedIn URL as a resolved output is coming soon.

Already paying another vendor?

A/B us against your incumbent, mid-contract

You already split-test creative, landing pages, and bid strategies. Test identity the same way. Delivr.ai is pure usage-based with no minimum, so you can run it beside your current identity or intent vendor on the same traffic and let the match rates argue.

  • Side-by-side on your own traffic, not a vendor benchmark deck
  • Person-level resolution, not account-level guesses
  • The test costs exactly what you resolve, nothing more
Start the comparison

Why deterministic

"A model said so" is not an answer

When the budget review asks why spend moved to this audience, "the vendor’s model scored it highly" doesn’t survive the meeting. A verified email match does.

The probabilistic status quo

  • Modeled audiences with confidence scores nobody can audit
  • Match rates inflated by counting low-confidence guesses
  • Accuracy decays every time device signals churn or panels go stale
  • Wasted impressions you can’t trace back to a real person

Deterministic by design

  • Every match anchored to a verified hashed email, or no match at all
  • 100% deterministic: the same visitor resolves to the same person every time
  • No device fingerprinting and no modeled inference, ever
  • An audience you can defend in any budget review: "verified email match"

How it works

Three steps to your first resolved profile

No SDK lock-in, no heavy onboarding. Authenticate, send an identifier, get a verified profile back.

  1. 01

    Request API access

    Sign up, e-sign the usage-based API agreement, and receive your credentials within one business day. No minimums, no annual prepay.

  2. 02

    Send an identifier

    GET a plain-text email or a SHA-256 or MD5 hash through the lookup endpoint. One call, JSON out.

  3. 03

    Get a resolved profile

    We return the verified person, company, or household, deterministically, with contact, firmographic, and 22K+ scored intent topics.

Average implementation

From signup to production in two weeks

A typical rollout. Most teams resolve their first profile on day one. The rest is validating against your own traffic before you flip to production.

  1. Day 1No minimums

    Sign up & request API access

    Create your account, e-sign the usage-based API agreement, and make your first lookup call. No minimums, no setup fees.

  2. Days 2–3

    First integration

    Wire the resolve endpoint into your pixel, CRM, or warehouse. One endpoint, predictable JSON.

  3. Days 4–6

    Map the response

    Plumb the resolved profile and intent topics into your destinations and workflows.

  4. Days 7–9

    Validate on your traffic

    Run a sample of your real anonymous traffic through the API and confirm match rate and data quality. You pay only for the resolutions you run.

  5. Days 10–12

    Review & plan rollout

    Review results with our team and size your production volume. Per-resolution pricing drops as you scale.

  6. Day 14Usage-based

    Go live

    Ramp to full production volume. Your bill is your usage, nothing more.

Two weeks is the average. Lighter integrations go live faster.

Documentation

Everything is documented

Auth, endpoints, identifier types, response schemas, rate limits, and webhooks, with copy-paste examples. Your engineers have what they need before the first call.

  • Authentication & API keys
  • The /resolve endpoint & identifier types
  • Response schema & intent topics
  • Webhooks, rate limits & SLAs

Questions performance teams ask

Before you take this to your CMO

Whatever you resolve, nothing else. There is no monthly minimum, no setup fee, and no seat license. Run a sample of one campaign’s traffic through the API, pay for those resolutions, and judge the match rate on your own numbers instead of a vendor benchmark.

Delivr.ai resolves 50%+ of US web traffic to verified people. Because pricing is usage-based with no minimum, validating that number on your own traffic costs exactly the resolutions you run during the test.

Pure usage: you pay per resolution, with bracket rates that fall as monthly volume grows. When you reach a cheaper bracket, all of that month’s usage bills at the lower rate, not just the units above the threshold. No floor, no annual prepay.

No. Delivr.ai never uses device, browser, or canvas fingerprinting and never models matches probabilistically. Every resolution is a deterministic match against a verified hashed email (HEM). If there is no deterministic match, the API says so.

Send a plain-text email and we normalize and hash it server-side, or send a SHA-256 or MD5 hash. The public lookup endpoint accepts email and HEM inputs and returns deterministic person and company fields when there is a match.

Resolution operates on hashed identifiers, and matching is deterministic against verified data, no fingerprinting, no inference. Delivr.ai supports data subject requests (access and deletion) and honors opt-outs across the graph.

Prove it on one campaign

Get a key, point a slice of traffic at the endpoint, and see your own match rate. You pay only for what you resolve. No minimums, no setup fees, no annual prepay.

How will you use the data? *

Select all that apply.

You'll receive your API Service Agreement via email for electronic signature.

Read the docs