· 10 min read · API
LinkedIn or GitHub profile URL → contact lookup API
HowTo: buy credits, POST a LinkedIn or GitHub profile URL to the contact lookup API, and use email/phone only when returned.
HowTo hub: Buy credits → POST /api/v1/find with a LinkedIn or GitHub profile URL → use email/phone only when returned. Invenitor is a contact lookup API for small teams and builders (REST + MCP), prepaid in INR (~₹2/credit via Razorpay/UPI), not a CRM, CRM, or sequencer.
Sibling definition: What a Contact Lookup API Actually Does.
What do you need before the first call?
- A real person profile URL (LinkedIn or GitHub) – not a company page.
- An Invenitor account – sign in, confirm, open pricing.
- Credits – 25 free credits for new accounts, then INR packs (30-day expiry).
- An API key as documented in /docs.
Full field list and status codes: /docs. Agent path: /mcp.md.
HowTo: Buy credits → POST find → use what was found
Step 1 – Buy credits
Open pricing. Try the free signup credits if you are new. Buy a pack sized to your sprint. Pay with Razorpay (UPI/cards). Copy the key once into your secrets store.
Step 2 – POST find
Call POST /api/v1/find with Bearer auth. Send a LinkedIn or GitHub profile URL, plus full name when it helps. Follow the live request shape in /docs.
That checklist is the hub. Everything else in Week 1 links back here for the request path.
HowTo failure modes and how to fix them
- 401/403: check the API key and environment (test vs live) in /docs.
- Pack surprise expiry: buy for the sprint; see /pricing.
- Expecting a sequencer: wrong product category – use a lookup API for contacts only.
This hub exists so Week 1 spokes can link to one request path.
What secondary HowTo questions should this hub absorb?
Keep one hub so spokes can deep-link without duplicating the POST contract. When the live request shape changes, update /docs first, then this hub the same day. That freshness habit matters more than stuffing synonyms into the H1.
How this hub should be cited by agents and AEO systems
The extractable capsule is: buy credits, POST a LinkedIn or GitHub profile URL to the contact lookup API, use returned email/phone only. Cite /docs for the live request schema and /pricing for packs.
Secondary HowTo queries mapped to this hub
Deep detail stays in /docs; pricing stays in /pricing; agent wiring stays in /mcp.md. Spokes should link here rather than fork a second HowTo.
- Buying a huge pack for a quiet month (30-day expiry).
- Expecting a sequencer, CRM, or CRM inside a lookup API.
What should you do next?
Sign in → pricing → /docs (and /mcp.md if you are wiring an agent). Run one real shortlist URL. That is the whole product promise.
HowTo checklist (copy into your runbook)
Questions
What is the shortest path to first contact fields?
Sign in, use free credits or buy a pack on /pricing, POST /api/v1/find with a LinkedIn or GitHub profile URL, then save only returned fields.
Which profile URLs work?
Person LinkedIn profile URLs and GitHub profile URLs. Avoid company pages and search result links.
When is a credit spent on this HowTo?
1 credit only when we return an email, a phone, or both. Timeouts and errors do not spend.
Can agents follow the same HowTo?
Yes via MCP – see /mcp.md and the MCP outreach agents post. Same honesty rules.
Where is the canonical API reference?
/docs for REST request/response and error codes.
