Developers
People search API for developers: plain-words queries over REST
Developers use Invenitor's REST API to send a plain-words query and get people back as JSON, with a flat search price and contacts charged only when found.
By Invenitor team. Updated .
What can you call?
- POST /api/v1/people/search with a plain-language query
- POST /api/v1/find with a LinkedIn or GitHub link
- GET /api/v1/usage to read your usage
What does the API give you?
Two main calls. People search takes a sentence and returns people with name, headline, company and profile links. Contact lookup takes a LinkedIn or GitHub link and returns an email, phone and links when available. See the API guide.
How does billing behave?
A search is 20 credits (₹40) and is free if it finds nobody. A contact is 1 credit (₹2) when an email or phone comes back. Timeouts and errors do not spend. That makes it simple to budget in code: read your usage before a batch.
What should you build around it?
Keep the key on your server, not in browser code. Handle empty contact fields as a normal result. Respect the lookup rate limit, which the pricing page lists as five lookups a minute. For agents, use MCP rather than wrapping the API yourself.
Common questions
- Is there a sandbox?
- There is no separate sandbox on the public docs. New accounts get 25 free credits, which is enough to test both calls.
- Where are the live prices?
- GET the pricing endpoint to get the current packs and credit costs as JSON.