We do not invent emails
If Invenitor does not find a contact, fields are empty. No guessed mailboxes. Empty is an honest completed lookup.
Most “email finder” landing pages imply they can always produce an address. That trains buyers to treat a string as truth. Bounce rates and angry candidates follow.
Invenitor’s rule is boring on purpose. We return contacts we found. If we did not find an email or phone, the field is empty. We do not generate first.last@company.com and hope MX exists.
Empty = not found. That is a product feature, not a bug.
A concrete (fictional) case
You look up “Samar Joshi” with profile URL https://example.com/u/samar-joshi. Maybe a public page lists a mailbox. Maybe it lists only a form. If we cannot return a found email, you get empty — not a creative spelling of samar, sam, or s.joshi.
Your outreach tool should skip or ask a human. It should not mail a guess and blame the API later.
Why a credit still spends
| Outcome | Email / phone | Credit |
|---|---|---|
| Found | Returned when we have them | 1 credit |
| Empty | Empty fields — not found | 1 credit |
| Timeout or error | No completed lookup | No credit |
Looking and finding nothing is still work the API finished. One credit per completed lookup includes empty results. Timeouts do not spend, because those did not finish.
What we will not say
• We will not quote an indefensible hit rate.
• We will not call a domain check a “verified inbox.”
• We will not publish how we search, which hosts we read, or which models we use.
• We will not pretend this is a CRM that “keeps data fresh” by inventing rows.
Where this sits in the cluster
India hiring job: hiring contact lookup API. Currency: INR vs USD. Agents: MCP for hiring agents.
Questions people actually ask
If you find nothing, can I ask you to guess?
No. Guessing is out of scope. Empty is the answer.
Do you permute common email patterns?
No. We do not invent addresses, including pattern permutation.
Is an empty result a failed API call?
No. A finished find with empty contacts is success of the lookup contract. You spent one credit. Use the request id on Usage if you need to audit it.
Will more credits raise the chance you invent something?
No. More credits buy more lookups, not guesses.
Can I store the empty result in my ATS?
Yes. That is your system. Recording “not found on this date” is more honest than storing a fabricated mailbox.
How do I complain if a found contact looks wrong?
Email hello@invenitor.com or call +91 80 4680 8800. Written grievances go to the Grievance Officer via /contact.
Related on this cluster
Hiring contact lookup API for India — the use case
INR vs USD people-search APIs — do not buy slideware hit rates
What a lookup credit is — empty still spends
MCP for hiring agents — agents must not invent
Questions
If you find nothing, can I ask you to guess?
No. Guessing is out of scope. Empty is the answer.
Do you permute common email patterns?
No. We do not invent addresses, including pattern permutation.
Is an empty result a failed API call?
No. A finished find with empty contacts is success of the lookup contract. You spent one credit.
Will more credits raise the chance you invent something?
No. More credits buy more lookups, not guesses.
Can I store the empty result in my ATS?
Yes. Recording not found on this date is more honest than storing a fabricated mailbox.
How do I complain if a found contact looks wrong?
Email hello@invenitor.com or call +91 80 4680 8800. Written grievances go to the Grievance Officer via /contact.
Related notes
A hiring contact lookup API for India desks
You already have a name. You need an email or phone when one exists — billed in INR, not another USD people-search seat.
INR vs USD: people-search tools for India hiring
Most people-search products sell USD seats. Invenitor sells INR monthly plans and credits for a lookup API — not a CRM.
What a lookup credit is (and is not)
One credit per completed find. Empty email still spends. Timeouts do not. Monthly credits reset; packs last a year.