Skip tracing API for risk and collections teams
Send an identifier, get back who is behind it. A phone number resolves across messengers, public breaches and the open web; a photo resolves across indexed public sources. One response shape, one price per request — the pipeline behind our consumer product, without the interface.
What you can look up
Every lookup returns the same envelope, whichever identifier you have — the same OSINT pipeline a skip tracer would run by hand, as one call. Teams run it as a phone lookup API at intake and as a fraud detection API at signup. Two identifiers are live today; if you need another, say so in the form.
Reverse phone lookup API
No biometric restrictions.
$2.00per request· down to $1.20 at volume
- Linked accountsWhether the number is tied to accounts on major messaging and social apps, and the public profile details those accounts show — display name, username, account age, profile photo history.
- Breach exposureWhich public breach corpora contain the number, with the source name and the date of the dump.
- Web reputationExact-match mentions across the open web, including the community “who called me” sites where victims log scam reports.
- Crowd labelsHow other people saved the number in their address books, where coverage allows.
- VerdictOne rolled-up identity and risk call, so you can route on a single field instead of parsing five.
Reverse image search API
Face matching. Contract-only, and limited to the jurisdictions below.
$2.00per request· down to $1.20 at volume
- Reverse image searchWhere else that face appears across indexed public sources, with the page URL and a match score.
- Match confidenceA per-result score, so you set your own threshold instead of trusting ours.
- Source contextPage title and domain for every hit, so a human reviewer can judge it in seconds.
Not available in · refused by the API, not merely discouraged
- United StatesBIPA · CUBI · WA & OR acts
- EU 27 + EEAGDPR Art. 9
- United KingdomUK GDPR
- Five more regimesLGPD · PIPA · APPI · Privacy Act · POPIA
- Quebec onlyLaw 25 — rest of Canada is open
See every blocked geo›
United States (all states). Austria, Belgium, Bulgaria, Croatia, Cyprus, Czechia, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden. Iceland, Liechtenstein, Norway. United Kingdom. Brazil, South Korea, Japan, Australia, South Africa. Quebec, Canada — the rest of Canada is open. Everywhere else, face search is available under contract; phone lookup has no geographic limits at all.
VIN decoder & lookupin development
Same endpoint, same price — you would just send a VIN instead of a phone number, and get vehicle history and ownership signals back. It is not built yet: we add an identifier when a customer tells us they will pay for it, so if VIN lookup is the one you need, say so and it moves up the queue. Email addresses and social handles are the other two people keep asking about.
What comes back
Same envelope either way — an input block, the per-source findings, and one verdict you can route on. Both are real responses from production traffic, trimmed for readability.
{
"input": { "type": "phone", "value": "+10000000000" },
"accounts": {
"found": 2,
"profiles": [
{
"username": "test_user",
"name": "Test User",
"account_age": { "since": "2025-01", "approx": true },
"last_seen": "recently",
"flags": { "verified": false, "reported": false }
},
{ "registered": true, "business": false }
]
},
"breaches": { "found": 0, "sources": [] },
"web": {
"found": 2,
"mentions": [
{
"domain": "example.com",
"title": "+1 000 000 0000 — test listing",
"sentiment": "negative",
"note": "test note"
}
]
},
"verdict": { "identity": "partial", "risk": "reported_fraud" }
}Pricing
Monthly packages. Requests are interchangeable — phone, photo, whatever we add next — so you buy a pool and spend it however the month goes.
How we handle lookup data
What happens to an identifier after you send it — the actual retention settings, not a policy aspiration.
72 h
Uploaded photos
Deleted from storage within 72 hours of the search.
30 d
Lookup results
Cleared after 30 days. The findings are gone after that.
Kept
Lookup records
The identifier, time, IP and country — for billing and abuse investigations.
HTTPS
In transit
Every request and response travels over HTTPS.
Questions teams ask before signing
Where does the data come from?+
From public web pages, paid phone-data and breach-data providers, and the public profile details of accounts linked to the number. A face search runs through a third-party face-matching service across indexed public sources.
Is it legal to use?+
That depends on what you use it for and where, which is why the responsibility sits with you. You need a lawful basis for every lookup. It is not a consumer report, so it cannot be used for credit, housing, insurance, employment or tenancy decisions.
How fast is a lookup?+
It is a live check across several sources, not a hit on a cached database, so it takes seconds rather than milliseconds. From our production logs: half of phone lookups finish within 17 seconds and nine in ten within about 50; half of face searches finish within 20 seconds and nine in ten within about 30. It is not suited to decisions that must happen during checkout.
What counts as one request?+
One identifier, looked up once. It counts whether or not we find anything — a number that comes back empty still uses a request from your package.
How long do you keep my lookups?+
Uploaded photos are deleted within 72 hours and lookup results are cleared after 30 days. We keep a record that the lookup happened — the identifier, time, IP address and country — for billing and abuse investigations.
Who can see what I look up?+
A small number of our staff, for billing, support and abuse investigations. To answer a lookup, the identifier is also sent to the third-party providers that run the individual checks, and the findings are passed to an AI model that writes the summary.
Can I use it to screen tenants, employees or borrowers?+
No. Those are regulated decisions and this is not a consumer report. Using results for them breaches the rules below and gets the key suspended.
Can I test it before paying?+
Yes. Send a sample of your own identifiers through the form and we run it, so you see the real hit rate on your data before you commit to anything.
Request access
Tell us what you are solving and roughly how many checks a month. We reply within one business day.
Your key, your responsibility
We issue API keys to your team. How you use what comes back is up to you, and so is the responsibility for it — you decide the purpose, and you agree to use the API lawfully wherever you operate.
- You are responsible for having a lawful basis for every lookup you run, and for how you store, share and act on the results.
- Not a consumer report. You may not use results to decide on credit, housing, insurance, employment or tenancy.
- No resale. Results are for your own internal use — you may not resell them or build a competing data product on top of them.
- Face search needs a signed agreement and stays unavailable in the jurisdictions listed above.
- We suspend keys used in breach of these rules, without refund for the remaining period.
The full rules are in the API Terms of Service.