IRBIS gives you phone intelligence, email enrichment, face search, social footprint, IP signals, and breach data — all under one API key. Feed richer identity signals into your verification engine without managing four separate data vendors.
There's a difference between a KYC workflow tool and an identity data infrastructure provider. IRBIS is the second one — and that matters for how you use it.
Most data providers cover one or two signal types well. IRBIS covers all of them — which means you stop paying for four separate vendor contracts.
IRBIS is an enrichment layer — it goes between your data collection and your risk decision. Here's how most teams wire it in.
Not end users. Engineers and product teams who are building something and need identity data infrastructure underneath it.
The market splits into four types of providers. IRBIS is the only one that crosses all four categories — which is the whole point.
| Signal / capability | IRBIS | Pipl | Telesign | Ekata | MaxMind | PDL | Sift | LexisNexis |
|---|---|---|---|---|---|---|---|---|
| Phone number intelligence | ✓ | Partial | ✓ Core | ✓ | ✗ | ✗ | Partial | ✓ |
| Phone line type (VoIP / mobile) | ✓ | ✗ | ✓ | ✓ | ✗ | ✗ | ✗ | Partial |
| Email identity enrichment | ✓ | ✓ | Partial | ✓ | ✗ | ✓ | Partial | ✓ |
| Reverse face / image search | ✓ Unique | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| Social footprint / identity graph | ✓ | ✓ | ✗ | Partial | ✗ | ✓ | Network signals | Partial |
| IP geolocation + VPN detection | ✓ | ✗ | Partial | ✓ | ✓ Core | ✗ | Device signals | ✗ |
| Breach / dark web exposure | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | Partial |
| Real-time API (not static dataset) | ✓ | ✓ | ✓ | ✓ | ✓ | Batch / static | ✓ | Mostly static |
| Investigative depth (not just scoring) | ✓ | Partial | ✗ | ✗ | ✗ | ✗ | Score only | Partial |
| All signals under one API key | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| Flexible / pay-per-lookup pricing | ✓ | Enterprise | Volume commit | Enterprise | ✓ | Subscription | Enterprise | Enterprise |
Standard REST API, Bearer token auth, JSON responses. If your stack already calls any enrichment API, you already know how to integrate IRBIS.
# 1. Submit enrichment request curl -X POST \ https://irbis.espysys.com/api/developer/post \ -H "Authorization: Bearer YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "searches": [ { "id": "phone", "term": "+14155552671" }, { "id": "real_phone", "term": "+14155552671" } ] }' # Returns lookupId immediately { "lookupId": "lk_9e2c83a1f" } # 2. Retrieve enriched results curl \ https://irbis.espysys.com/api/developer/results/lk_9e2c83a1f \ -H "Authorization: Bearer YOUR_KEY"
lookupId immediately. Your system stores it and GETs the result when ready. No blocking, no timeout risk on your application layer. Most results land in 10–30 seconds.searches array accepts multiple signal types in a single POST request. One round trip to get phone + email + IP enrichment simultaneously./credits endpoint.