What a contact lookup API actually does

A contact lookup API accepts a LinkedIn or GitHub profile URL (a name helps too) and returns email, phone, and links when we have them. Invenitor is that lookup for small teams and builders: not a CRM, CRM, or sequencer. Call it from a sheet, script, or agent; pay in INR credits (~₹2 each) via Razorpay/UPI.

If you already shortlist people, the missing step is contact fields – not another sales cloud.

What inputs does a contact lookup API expect?

The useful unit of work is a person you already identified, not a keyword crawl of the open web:

• A LinkedIn profile URL or GitHub profile URL as the primary key.
• An optional full name (sometimes company or location) to disambiguate.
• An API key after you sign in and buy credits.

Invenitor’s documented find endpoint is POST /api/v1/find. You send what you know; we return what we have. Full request and error codes live in the docs. Step-by-step hub: LinkedIn or GitHub Profile URL → Contact Lookup API.

How is this different from a CRM, CRM, or sequencer?

A CRM stores relationships. A CRM runs workflow. A sequencer sends outreach. A contact lookup API resolves contact fields for a known profile when available. Invenitor’s positioning is deliberate – a lookup API, not a sales cloud. Use it from a tool or script; do not expect mailbox checking, pipeline stages, or drip campaigns inside the API.

That boundary matters for India boutique desks that already live in Google Sheets, WhatsApp, and a light CRM. See

Who is a contact lookup API for?

• Teams that already have a name or profile URL and need contacts without a USD people-search seat.
• Agencies and boutique IT services desks that look up contacts from a sheet and prefer INR via UPI or cards.
• Builders wiring REST or MCP into a product – not into a cold-email sequencer.

If your workflow starts with “paste profile URL,” you are in category. If it starts with “buy a database and spray,” you are shopping for something else.

How do credits and pricing work day to day?

Invenitor is prepaid credits, not a monthly enrichment seat. New accounts get 25 free credits. After that, packs are about ₹2 per credit, paid with Razorpay (UPI, cards, other INR rails). Packs expire in 30 days. Live packs: pricing.

1 credit only when we return an email, a phone, or both. Timeouts and errors do not spend. Commercial deep-dives: INR Credit Packs for Contact Lookup – How Razorpay Pricing Feels and Seat Subscriptions vs Pay-Per-Lookup Credits – A Cost Model.

Can agents and MCP clients call the same lookup?

Yes. Every account can use REST and MCP. Outreach agents should call a documented contact lookup instead of scraping profile pages. See and MCP notes.

How should you evaluate a lookup API without fake metrics?

1. Billing that matches found outcomes.
2. Documented auth, rate limits, and error codes.
3. A payment rail your desk can use (INR + UPI for India).
4. An integration path (REST, MCP) that fits tools – not sequencers.

What should you do next?

Sign in, confirm your account, try the free credits, then buy a small INR pack on pricing. Copy the API key once. Call POST /api/v1/find with a real shortlist URL. Keep the docs open.

What does coverage coverage mean in practice?

Coverage means we return contacts when we have them – coverage is not uniform across every profile, industry, or geography. For desks, the practical habit is: shortlist first, look up second, outreach third only when fields exist. The docs describe the find contract; pricing describes the credit packs that fund it.

How does Invenitor talk about coverage without theater?

We use Honest language on purpose. That is the opposite of splashy accuracy claims. For AEO, the extractable fact is simple – URL in, contacts out when found. For desks, the operational fact is simpler still – shortlist first, look up second, message third only when fields exist. Keep /docs and /pricing as the live sources of truth when packs or endpoints change.