How can we help you?

IRBIS is ESPY's cloud-native identity intelligence and OSINT platform. It takes a minimal identifier — a phone number, email address, name, social media profile, or face image — and enriches it into a multi-signal identity profile in real time.

IRBIS is used by fraud and risk teams, compliance departments, trust & safety teams, professional investigators, journalists, insurers, and HR professionals to verify identities, detect suspicious patterns, and reduce risk across onboarding and operational workflows.

IRBIS is available as a web portal (irbis.espysys.com) for interactive lookups and as a developer API for automated, high-volume integrations.

To create an account: 1. Visit irbis.espysys.com and click Sign Up. 2. Enter your email address and create a password. 3. Verify your email by clicking the confirmation link. 4. Log in and you'll receive a trial credit package to explore the platform.

No credit card is required to create an account or to use trial credits.

After logging in to the IRBIS web portal:

• Select the lookup type from the left menu (Phone, Email, Name, Social, etc.).
• Enter your input in the search field — for example, a phone number in E.164 format (+14155552671) or an email address.
• Click Search or press Enter.
• IRBIS returns an enriched profile, typically in under 5 seconds.
• You can download the report as a PDF or export raw JSON.

Each lookup deducts credits from your balance according to the query type and your plan rate.

Yes. When you register on the IRBIS portal, your account receives an initial trial credit package so you can test lookups before purchasing. You can also use the free instant search tools on espysys.com (phone and email) without creating an account.

For API testing, trial credits work identically to paid credits — all endpoints are accessible.

The IRBIS web portal includes:

• Search modules — Phone, Email, Name, Social, Face, Breach, IP, and more (availability depends on plan).
• Result reports — structured identity profiles with confidence scores, downloadable as PDF or JSON.
• History — a log of all previous lookups for your account.
• API key management — generate, rotate, and revoke API keys.
• Credit balance — real-time credit usage and remaining balance display.
• Billing & plan management — view invoices, upgrade plans, and manage subscriptions.

IRBIS covers 200+ countries. Phone lookups work globally using E.164-format numbers. Email and name lookups aggregate signals from global sources. Social media and digital footprint lookups are not limited by geography.

Certain compliance-specific modules (e.g., SSN Trace, National Criminal Screening) are currently limited to the United States. Watchlist and PEP screening cover international entities.

Yes. From the portal, every lookup result can be exported as a PDF report or as raw JSON data. Use the download icon on any result card.

Via the API, all responses are returned in JSON format, making it straightforward to pipe results into your own database, CRM, or reporting tools.

You can reach our team at info@espysys.com. We typically respond within 24 hours on business days.

For API-specific technical questions, billing inquiries, or enterprise pricing, please include your account email in your message so we can assist you faster.

Your API key is generated inside the IRBIS web portal: 1. Log in to irbis.espysys.com. 2. Navigate to Settings → API Keys. 3. Click Generate new key. 4. Copy and store the key securely — it is only shown once.

You can generate multiple keys (e.g., separate keys per application) and revoke them at any time from the same settings panel.

All IRBIS API requests must include your API key in the Authorization header using the Bearer scheme:

Authorization: Bearer YOUR_API_KEY

Example request (phone lookup):

curl -X POST https://api.espysys.com/lookup/phone \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"phone": "+14155552671"}'

Never include your API key in a URL query parameter or embed it client-side in a public app.

The IRBIS API base URL is:

https://api.espysys.com/

All endpoints are HTTPS only. Full API documentation including all available endpoints and request schemas is at api-docs.espysys.com.

All responses are returned as JSON. A typical successful response contains:

{
  "status": "success",
  "credits_used": 10,
  "credits_remaining": 970,
  "confidence": 0.87,
  "data": {
    "name": "John D.",
    "phones": [...],
    "emails": [...],
    "social_profiles": [...],
    "risk_signals": {...}
  }
}

The data object structure varies by lookup type. Confidence scores (0–1) indicate match quality. Refer to the API docs for full field-level schemas per endpoint.

Yes. Rate limits apply per API key and depend on your plan. If you exceed the rate limit, the API returns HTTP 429 Too Many Requests. The response includes a Retry-After header indicating how many seconds to wait before retrying.

For high-volume or real-time integration use cases that require elevated rate limits, contact info@espysys.com to discuss an enterprise arrangement.

• 200 OK — Request succeeded. Results in data field.
• 204 No Content — Request succeeded but no enrichment data was found for the input.
• 400 Bad Request — Invalid or malformed request body (e.g., missing required field, wrong phone format).
• 401 Unauthorized — Missing or invalid API key.
• 402 Payment Required — Insufficient credits to complete the lookup.
• 403 Forbidden — Your plan does not include access to this endpoint.
• 429 Too Many Requests — Rate limit exceeded. Check Retry-After header.
• 500 Internal Server Error — Server-side error. Retry after a short delay; if persistent, contact support.

In the IRBIS portal go to Settings → API Keys. Click the revoke (trash) icon next to any key to immediately invalidate it. Then generate a new key and update your application.

If you suspect a key has been compromised, revoke it immediately. Revoked keys stop working instantly — no grace period.

Most IRBIS lookup endpoints are synchronous — the result is returned in the same HTTP response, typically within 5 seconds. Asynchronous / webhook patterns are available for certain batch or bulk use cases.

For bulk processing requirements (e.g., submitting thousands of phone numbers), contact info@espysys.com to discuss the Mass Profiler workflow, which uses a queue-based asynchronous model.

IRBIS is a standard REST API, so any HTTP client library in any language works out of the box. Common examples:

• Python: requests library — requests.post(url, headers=headers, json=payload)
• Node.js: axios or native fetch
• PHP: curl or Guzzle

Dedicated SDK packages are in development. For the latest status, contact info@espysys.com.

A Phone Lookup takes a phone number in E.164 format (e.g., +14155552671) and returns enriched identity signals including:

• Carrier name and line type (mobile, landline, VoIP)
• Country and region information
• Associated names and aliases (where available)
• Linked email addresses and social profiles
• Activity signals and reputation indicators
• Spam / fraud risk score

Phone lookups work globally across 200+ countries. Results include a confidence score reflecting data availability for that number.

An Email Lookup accepts any email address and returns:

• Domain reputation and MX validity check
• Linked name(s) and identity signals
• Associated social media accounts and usernames
• Breach exposure — whether the email appears in known data leaks
• Deliverability status (valid, risky, disposable, etc.)
• Risk score and fraud indicators

Combine Email Lookup with Phone Lookup to cross-validate identities.

Name Search accepts a full name (and optionally a city or company) and returns a ranked list of candidate profiles. Each profile includes:

• Matched name and known aliases
• Associated contact identifiers (phones/emails where found)
• Linked social media profiles and usernames
• Confidence score per result (higher = stronger match)

Including additional context (location, employer) significantly improves accuracy. Name Search covers global records, not just US databases.

Social Profile Lookup takes a username, social media profile URL, or platform user ID and maps it to a broader identity profile. It can reveal:

• Profile details (display name, bio, joined date, public data)
• Accounts on other platforms sharing the same username or linked signals
• Associated phone numbers or emails (where data is available)
• Activity patterns and platform presence

Supported platforms vary; see the API docs for the current list of supported networks.

Face WebScan lets you upload an image of a face and search for publicly available matching profiles across the web. It returns:

• Matching public profiles ranked by facial similarity score
• Profile URLs, names, and associated platforms
• Confidence score per match

This feature is available on the Ultimo plan and higher. It is intended for professional investigative use within legal and ethical boundaries. Usage is logged and governed by ESPY's Terms of Use.

BreachScan checks whether an email address or phone number appears in known data breach databases. It returns:

• Number of breaches the identifier appears in
• Breach names and approximate dates
• Types of data exposed (password hashes, addresses, etc.) without exposing the raw leaked data

Use BreachScan as a risk signal during account onboarding — a heavily breached email is a strong indicator of increased fraud risk.

IP Lookup takes an IPv4 or IPv6 address and returns:

• Country, region, city, and approximate coordinates
• ISP name and ASN (Autonomous System Number)
• Connection type (residential, datacenter, VPN, proxy, Tor)
• Abuse / spam score for the IP

Use IP Lookup to validate that a user's claimed location matches their connecting IP, flag VPN/proxy use during onboarding, or detect suspicious login patterns.

IRBIS KYC & Watchlist Screening checks an individual's name (and optionally date of birth, country) against international watchlists and PEP (Politically Exposed Person) databases. Results include:

• PEP status and role description
• Sanctions list matches (OFAC, UN, EU, and others)
• Adverse media signals
• Match confidence score

This feature is available on the Ultimo plan. It is intended to support AML and compliance screening workflows, not to serve as a sole compliance decision tool. Always consult your compliance team.

The AI Psychological Portrait is a behavioral summary generated from publicly available signals such as social media posts, writing style, and activity patterns. It produces a structured report covering inferred personality traits, communication style, and behavioral tendencies.

This feature is intended for professional investigative and HR use cases within applicable laws. It is not a psychiatric assessment and should be treated as an investigative signal, not a definitive characterization of any individual.

The confidence score (0.0 – 1.0) reflects how certain IRBIS is that the returned data corresponds to your input. It is calculated based on:

• Number of independent corroborating data sources
• Consistency of data across sources
• Recency of the underlying data signals

A score above 0.75 is generally considered high confidence. Below 0.4 indicates limited data availability — results should be treated as unverified signals rather than confirmed facts.

IRBIS offers three plans:

• Combo — €98/month · 980 credits/month · ~10 credits/query. Core lookups: phone, email, name, social, and more.
• Ultimo — €450/month · 4,500 credits/month · ~8 credits/query. Everything in Combo plus face recognition, KYC/watchlist screening, criminal records, and advanced modules.
• Pay As You Go — €500 one-time · 5,000 credits · valid for 12 months. No recurring charge. Use at your own pace.

Annual subscriptions receive a 10% discount (Combo Annual: €1,056 · Ultimo Annual: €4,860). See the full plan comparison at espysys.com/pricing.

Credits are the consumption unit for IRBIS lookups. One lookup deducts a fixed number of credits based on the lookup type and your plan:

• Combo plan: approximately 10 credits per standard query.
• Ultimo plan: approximately 8 credits per standard query (better rate per query).
• Certain advanced lookups (face recognition, KYC screening) may cost more credits. Check the pricing comparison page for exact costs per module.

Credits are deducted only on a successfully processed request. Requests that return 400 or 401 errors do not consume credits.

Monthly plans (Combo / Ultimo): Credits are refreshed at each billing cycle. Unused credits from the previous month generally do not roll over — check your plan's specific terms in the IRBIS portal under Billing.

Pay As You Go: Credits are valid for 12 months from the date of purchase. Use them at any rate within that window.

To confirm exact rollover rules for your account, visit Billing in the portal or review the Terms of Use.

Yes. You can upgrade from Combo to Ultimo at any time from the Billing section of the IRBIS portal. The change takes effect immediately and the new credit balance reflects the upgraded plan.

To discuss downgrading or switching to Pay As You Go mid-cycle, contact info@espysys.com.

Your credit balance is displayed in the top-right corner of the IRBIS portal at all times. You can also check it programmatically via the API:

GET https://api.espysys.com/account/balance
Authorization: Bearer YOUR_API_KEY

The response includes credits_remaining and credits_used_this_cycle. Every API response also includes a credits_remaining field after each lookup.

Per the ESPY Terms of Use, all purchases are generally non-refundable once credits have been used. If you believe you have been charged in error or have a billing dispute, contact info@espysys.com within 14 days of the charge and we will review your case.

Yes. Annual plan subscribers receive a 10% discount compared to monthly pricing. Promo codes are occasionally issued through the affiliate program and marketing campaigns — enter them at checkout to apply the discount.

ESPY also operates an affiliate program offering a 10% commission on referral sales. Learn more at espysys.com/become-an-affiliate.

Yes. For high-volume API usage, custom integration requirements, dedicated infrastructure, or government/enterprise deployments (including the OSINT Center and Mass Profiler), ESPY offers custom pricing on a quote basis.

Contact info@espysys.com with an overview of your use case and expected monthly lookup volume and we will prepare a custom proposal.

ESPY has a native Zapier integration. To set it up: 1. Search for IRBIS in the Zapier app directory. 2. Connect using your IRBIS API key. 3. Choose a trigger (e.g., new row in a Google Sheet) and an action (e.g., Phone Lookup or Email Lookup). 4. Map the result fields to your destination (CRM, spreadsheet, database).

Available Zapier actions include phone lookup, email lookup, name validation, and balance check. Each Zap run consumes credits from your IRBIS account.

ESPY has a native Make.com app. Available modules include:

• Phone Lookup
• Email Lookup
• Name Validation
• Get Lookup Data (retrieve a previous result by ID)
• User Balance check
• Generic API Call (for advanced scenarios)

In Make.com, search for IRBIS in the app list, authenticate with your IRBIS API key, and add the desired module to your scenario.

Yes. Using Zapier or Make.com, you can trigger an IRBIS lookup whenever a new contact is added to your CRM (Salesforce, HubSpot, Pipedrive, etc.) and write the enriched data back to the contact record.

For deeper, real-time CRM enrichment at scale, use the IRBIS REST API directly from your backend — pass a contact's phone or email to IRBIS and update the CRM record with the returned identity signals.

Yes. A common workflow via Zapier: use a New or Updated Spreadsheet Row trigger in Google Sheets → IRBIS Phone/Email Lookup action → Update Row to write results back. This processes each row as it's added.

For bulk batch processing of existing lists (hundreds or thousands of rows), use the IRBIS API directly with a script (Python, Node.js, etc.) that iterates through your list, submits each lookup, and collects the results. This is more efficient and avoids Zapier task limits.

Direct integration is straightforward via the REST API:

• Generate an API key in the IRBIS portal.
• From your backend, make a POST request to the relevant endpoint with the identifier.
• Parse the JSON response and use the data in your application logic.

Always call the API from your server side — never expose your API key in client-side JavaScript, mobile apps, or public repositories. Full API docs at api-docs.espysys.com.

Yes. ESPY operates an affiliate program offering a 10% commission on sales referred through your unique affiliate link. You also receive discount codes to share with your audience. Sign up at espysys.com/become-an-affiliate.

An empty result (HTTP 204 No Content) means IRBIS processed your query successfully but found no matching data for that identifier. Common reasons:

• The phone number or email is very new, unpublished, or not present in any indexed sources.
• The input format is incorrect — ensure phone numbers use E.164 format (+countrycode number).
• The identifier belongs to a region with limited data coverage.

Credits are not deducted for 204 responses. If you consistently get empty results for valid numbers in well-covered regions, contact support with example inputs.

A 401 Unauthorized means the API key is missing or invalid. Check the following:

• The Authorization header is present in the request and formatted as Bearer YOUR_API_KEY (note the space after "Bearer").
• You are using the correct key — copy it fresh from the IRBIS portal under Settings → API Keys.
• The key has not been revoked. If it was revoked, generate a new one.
• There are no leading/trailing spaces or line breaks in the key value.

HTTP 402 Payment Required means your account does not have enough credits to complete the requested lookup. To resolve this:

• Check your credit balance in the portal or via GET /account/balance.
• Purchase additional credits or upgrade to a plan with more credits.
• If you are on a monthly plan, credits refresh on your next billing date.

403 Forbidden means your current plan does not include access to the endpoint you requested. For example, Face Recognition and KYC Screening are only available on the Ultimo plan. Upgrade your plan in the Billing section to unlock these features.

400 Bad Request indicates the request body is invalid. The error response will include a message describing what's wrong. Common causes:

• Phone number not in E.164 format — use +14155552671, not 4155552671 or +1-415-555-2671.
• Missing required field — check the endpoint's schema in the API docs.
• Invalid JSON — ensure the Content-Type: application/json header is set and the body is valid JSON.

Most IRBIS lookups respond within 2–5 seconds. If requests are slow or timing out:

• Set your HTTP client timeout to at least 30 seconds to account for complex enrichment queries.
• Retry with exponential backoff on 500 errors (server-side transient issues).
• Avoid sending many concurrent requests from a single API key — this may trigger rate limiting.
• For high-concurrency batch workflows, contact support to discuss the asynchronous Mass Profiler API.

If you experience persistent latency issues, email info@espysys.com with your account email and approximate timestamps.

IRBIS aggregates data from multiple sources that are updated continuously, but some underlying sources may have a lag. If you believe a result is significantly incorrect:

• Check the confidence score — a low score indicates limited data and higher uncertainty.
• Cross-reference with a second lookup type (e.g., email lookup to corroborate a phone result).
• Report the issue to info@espysys.com with the query type, the input (anonymised if needed), and what specifically appears incorrect. This helps improve data quality.

A lookup is a single search request you send to IRBIS. You give it one piece of information — a phone number, email, name, or image — and it searches its data sources and comes back with everything it can find about that identifier.

Think of it like a Google search, but instead of web pages you get a structured identity profile. Each lookup deducts credits from your account balance.

A credit is the unit of currency inside IRBIS. Every plan comes with a bundle of credits. Each time you run a lookup, a small number of credits are subtracted from your balance.

Example: on the Combo plan you get 980 credits per month, and a standard lookup costs about 10 credits — so you can run roughly 98 standard lookups per month. More advanced lookups (like face recognition) may cost more credits.

Enrichment means taking a small piece of information you already have — like a phone number or an email address — and expanding it into a much fuller picture.

For example: you start with just a phone number. After enrichment, you might have the person's name, linked email addresses, social media profiles, and a risk score. You "enriched" one data point into many.

OSINT stands for Open Source Intelligence. It means gathering information from publicly available sources — social media, websites, public databases, news articles — and turning it into useful intelligence.

IRBIS is an OSINT platform: it automates the process of collecting, cross-referencing, and structuring public data so you get an organized result instead of having to manually search dozens of sources yourself.

An API (Application Programming Interface) is a way for two software systems to talk to each other. Think of it like a waiter at a restaurant: you (your app) place an order (a request), the waiter (the API) takes it to the kitchen (IRBIS), and brings back your food (the result).

The IRBIS API lets your own website, app, or script send a phone number or email to IRBIS and get back an identity profile — all automatically, without anyone clicking anything manually.

A confidence score is a number between 0 and 1 that tells you how sure IRBIS is about the result it returned. Think of it as a percentage: 0.9 means "90% confident this is correct," 0.3 means "only 30% confident — treat this as a weak signal."

A high score means multiple independent sources confirmed the same data. A low score means the data was found in few places or the sources disagreed. Always weigh low-confidence results carefully.

KYC (Know Your Customer) is the process businesses use to verify who their customers actually are before doing business with them — used widely in banking, fintech, crypto, and insurance.

AML (Anti-Money Laundering) refers to checks and controls that prevent financial crime — confirming a customer isn't on sanctions lists, isn't a politically exposed person (PEP), and doesn't have adverse criminal history.

IRBIS supports both workflows: phone/email/name lookups help verify identity, while the Watchlist & PEP screening module provides AML-relevant signals.

E.164 is the international standard format for phone numbers. It starts with a +, followed by the country code, then the local number — with no spaces, dashes, or brackets.

Examples:

• US: +14155552671
• UK: +447700900123
• Germany: +4915123456789

IRBIS requires phone numbers in E.164 format. If you send 415-555-2671 or (415) 555-2671 you'll get a 400 Bad Request error — always include the country code and the leading +.

Yes — this is exactly what the IRBIS API is designed for. You can use IRBIS as the intelligence engine behind your own branded product: a fraud-screening tool, a KYC widget, a lead-enrichment service, a risk dashboard, or any other identity-data application.

Your end users interact with your product. Your product calls the IRBIS API on the backend and presents the results in whatever format suits your use case. ESPY remains invisible to your end users if that's what you need.

Chain your API calls on the backend and merge the results before presenting them to your user. A common cascade pattern:

1. POST /lookup/phone   → get name + linked emails
2. POST /lookup/email   → enrich each linked email
3. POST /lookup/name    → expand name matches
4. Merge all JSON results into one unified profile object
5. Render that object in your UI

Because lookups are fast (typically under 5 seconds each), you can run steps 1–3 in parallel using Promise.all() (Node.js) or asyncio.gather() (Python) to keep total response time low. Show a loading indicator in your UI while the parallel calls complete, then render the merged result.

The recommended approach for a publicly visible website:

• Frontend: Build a simple HTML form (phone / email / name input field + Submit button).
• Your backend: On form submission, your server receives the input, calls the IRBIS API with your API key (server-side only — never expose the key in JavaScript), and returns the formatted result to your frontend.
• Frontend rendering: Display the result in a styled card or modal on your page.

Never call the IRBIS API directly from the browser — your API key would be visible in network requests. Always proxy through your own backend endpoint.

After merging results from multiple lookups on your backend, deduplicate and structure the data before sending it to your frontend. A practical merging strategy:

• Identity fields (name, aliases): union all unique values, rank by frequency across sources.
• Contact fields (phones, emails): deduplicate by normalized value.
• Social profiles: collect all unique platform URLs.
• Risk signals: take the highest risk score across all lookups as the overall risk level.
• Confidence: average confidence scores, weighted by number of data sources per lookup.

Present the merged result as sections in a single profile card: Identity → Contact Details → Online Presence → Risk Signals. This gives users a clean "one search, one result" experience.

IRBIS works with any backend. Choose what your team knows best:

• Node.js / Express — great for high-concurrency API proxying; use axios or native fetch.
• Python / FastAPI or Flask — clean async support with httpx or aiohttp for parallel lookups.
• PHP / Laravel — use Guzzle for HTTP requests; easy to integrate into existing CMS or WordPress stacks.

Minimal viable backend: one route that accepts user input, validates it, calls IRBIS, and returns a sanitized JSON response to your frontend. Add caching (Redis or in-memory) to avoid re-calling IRBIS for the same input within a short time window — this saves credits and cuts response time.

Yes — caching is strongly recommended if your product may receive repeat lookups for the same identifiers. Benefits: saves credits, reduces latency for returning users, and reduces load on the API.

A practical approach:

• Use Redis (or a simple database) as a cache layer keyed on lookupType:normalizedInput.
• Set a TTL (time-to-live) of 24–72 hours — IRBIS data is continuously updated, so don't cache indefinitely.
• On each request: check the cache first. Cache hit → return immediately (no credit used). Cache miss → call IRBIS, store result, return to user.

For compliance-sensitive use cases (KYC), always fetch fresh results rather than serving cached ones — a cached profile may be outdated for sanction screening.

Always validate and normalize input on your backend before sending it to IRBIS. This avoids wasted 400 Bad Request calls and protects against bad data:

• Phone numbers: strip all spaces, dashes, and brackets; ensure it starts with + and a valid country code. Libraries like libphonenumber (available for Python, JS, PHP) do this reliably.
• Emails: use a regex or a library to confirm it's a syntactically valid email before sending.
• Names: strip leading/trailing whitespace; ensure at least two characters are present.
• Face images: check file type (JPEG/PNG), file size limit, and minimum pixel dimensions before uploading.

Reject invalid input at your backend layer and return a clear error message to the user — don't let bad data reach the IRBIS API and consume credits.

There are two main paths to generating revenue with IRBIS:

• Active (product) monetization: build your own product or service that uses IRBIS as the data engine. Sell access to your product at a markup. Examples: KYC verification tools, AML screening services, lead enrichment platforms, reverse phone lookup directories, or HR screening tools.
• Passive (affiliate) monetization: promote IRBIS directly and earn a 10% commission on every sale you refer — via your website, content on TikTok, Instagram, YouTube, newsletters, marketplaces, or any platform where your audience is.

Both can be combined: build a product (active) and also promote IRBIS to those who'd rather use it directly (passive).

A KYC (Know Your Customer) verification product built on IRBIS typically works like this:

• Input: your customer submits their phone number, email, or name during sign-up.
• Backend: you call IRBIS Phone + Email + Watchlist lookups in parallel.
• Decision logic: apply your own scoring rules (e.g., high-risk carrier + breach exposure + PEP hit = reject).
• Output: return a pass/fail/review decision to your client's onboarding flow.

Revenue model: charge your clients per verification check (e.g., $0.50–$2 per check) or on a monthly SaaS subscription. Your cost per check via IRBIS is predictable (credits), so your margin is the difference between what you charge and what you pay.

Target markets: fintech startups, neobanks, crypto exchanges, lending platforms, marketplaces — any business that needs to verify users at onboarding.

An AML screening service uses IRBIS's Watchlist & PEP lookup (available on the Ultimo plan) as its core intelligence layer:

• Accept a customer's full name + date of birth + country from your client's compliance system.
• Submit to IRBIS Watchlist/PEP endpoint and receive sanctions matches, PEP flags, and adverse media signals.
• Return a structured match report with risk classification (clear / possible match / confirmed match).
• Store results with timestamps to satisfy your clients' audit trail requirements.

Revenue model: per-screening fee or monthly API subscription. Target markets include law firms, accountancies, real estate agencies, insurance brokers, and any regulated business with AML obligations. The global AML compliance software market runs into the billions — there is substantial demand for affordable, API-first alternatives to legacy providers.

A lead enrichment product sits on top of IRBIS Name + Email + Social lookups and lets sales teams get deeper profiles on their prospects instantly:

• User inputs a name or email from their CRM or a spreadsheet.
• Your product calls IRBIS, merges results, and returns enriched data: phone number, social profiles, employer signals, digital footprint.
• Results write back to the CRM record automatically via Zapier/Make.com or a direct integration.

Revenue model: per-lookup credit packs, monthly SaaS tiers by lookup volume, or a per-seat model for sales teams. Target customers: B2B sales teams, recruiters, real estate agents, marketing agencies, and insurance agents who need to verify or expand contact lists.

Yes. A reverse phone lookup site is one of the most proven models for monetizing identity data APIs. The structure is simple:

• SEO-optimized landing pages targeting searches like "who called me from [number]" or "reverse phone lookup."
• A free partial result (carrier, country, line type) shown to drive traffic, with a paywall for the full enriched profile.
• Monetization via pay-per-report, subscription access, or ad revenue on free results.

IRBIS handles all the data retrieval — you own the brand, the design, and the user experience. This model scales well: traffic from search engines generates revenue without proportional increases in your effort.

The ESPY affiliate program pays a 10% commission on every sale made through your unique referral link. You also receive a discount code to share with your audience, which gives them an incentive to buy while you earn on the conversion.

• Sign up at espysys.com/become-an-affiliate.
• Get your unique referral link and discount code.
• Share it anywhere your audience is — website, bio links, video descriptions, social posts.
• Earn 10% commission on each purchase made via your link, tracked via PayPro Global.

There is no cap on earnings. The more qualified traffic you send, the more you earn — entirely passively once your content is live.

Content that performs well for identity and OSINT tools on social platforms:

• TikTok & Instagram Reels: short demos — "I searched my own phone number and found THIS." Screen recordings of a live IRBIS lookup work extremely well because the result is visually striking and the audience immediately understands the value. Include your affiliate link in your bio.
• YouTube: tutorials — "How to check who owns any phone number," "How I verify leads before calling them," "Best tools for OSINT research." Longer-form content builds trust; put your affiliate link in the description with a discount code for viewers.
• Instagram: carousel posts showing "5 things you can find out from a phone number" with screenshots. Story links direct to your affiliate URL.
• Newsletters & blogs: reviews and comparison articles ("IRBIS vs. Spokeo vs. PIPL") capture high-intent search traffic and convert well.

The most effective content answers a question the audience already has — "Who called me?", "Is this lead real?", "How do recruiters verify candidates?" — and positions IRBIS as the solution.

Yes. Products built on IRBIS can be distributed across a wide range of channels:

• API marketplaces: list your enrichment API on RapidAPI, APILayer, or similar hubs where developers search for data services. This brings inbound developer customers without marketing spend.
• Zapier / Make.com marketplace: publish your integration as a public app so users can find it in the automation ecosystem.
• Chrome extensions: a browser extension that lets users look up phone numbers or emails directly from LinkedIn, Gmail, or any webpage is highly viral in B2B sales communities.
• WordPress / Shopify plugins: a fraud-screening plugin for e-commerce stores or a verification widget for WordPress membership sites can be sold on plugin marketplaces.
• Freelance platforms: offer IRBIS-powered "identity investigation" as a service on Fiverr or Upwork — using IRBIS to deliver the report, charging per project.

Yes. Monthly and annual subscription plans (Combo and Ultimo) auto-renew at the end of each billing cycle. You will receive an email reminder before renewal. To disable auto-renewal or cancel before the next cycle, visit Billing → Subscription in the portal or contact info@espysys.com.

To cancel your subscription, go to Billing → Subscription in the IRBIS portal and click Cancel Plan. Your plan remains active until the end of the current billing period. Alternatively, email info@espysys.com with your cancellation request at least 48 hours before your renewal date.

All invoices are available in the IRBIS portal under Billing → Invoices. Each invoice can be downloaded as a PDF. Invoices are also emailed to the registered account address after each payment.

If you need a VAT invoice, a specific billing format, or have a billing inquiry, contact info@espysys.com.

Go to Settings → Profile in the IRBIS portal to update your display name, email address, or password. If you are locked out of your account, use the Forgot Password link on the login page at irbis.espysys.com. For email changes that involve billing records, contact support for assistance.

For teams, the recommended approach is to use the API with separate API keys per team member or per application. Each key shares the credit pool of the account but provides individual audit trails.

For enterprise deployments with multi-user portal access, role-based access control, and dedicated infrastructure, contact info@espysys.com to discuss the OSINT Center or enterprise IRBIS arrangement.

ESPY accepts major credit and debit cards (Visa, Mastercard, American Express) processed securely via PayPro Global. For enterprise invoiced billing or alternative payment arrangements, contact info@espysys.com.