LinkedIn data, as an API.

People, organizations, jobs and work contact details as JSON — and the part most of these services leave out: tracking who changes job, and telling you when they do.

Join the waitlist Read the docs Invitation only while in early access — the first 10 on the waitlist start with 1,000 credits, the next 10 with 500.

endpoints

sections

response envelope

0.1s

every call after the first

First 10: 1,000 credits · next 10: 500

Request early access

Rynora is invitation-only while it is in early access. Leave your email and we’ll send you an invitation. The first 10 people to join get 1,000 credits to start and the next 10 get 500 — the usual free tier is 100.

What’s your email? * This is where we’ll send access and credits. What best describes you? * What would you primarily use Rynora for? * How are you currently finding contact / company data? What’s the biggest problem with your current solution? * Roughly how many contacts would you need per month? * What would make Rynora worth paying for? Would you talk with us for 15 minutes about how you find leads / data?

What you can ask it

One key, one response shape, and a credit cost printed on every reply.

People

Enrich one, or a thousand

Full profiles: positions, education, skills, endorsements, employment history. One at a time, or a list in one batch job.

Organizations

Companies and who works there

Company pages, headcount, similar and affiliated pages, posts and open roles.

Contact

Work email and phone

Find an address from a name and a domain, with an honest confidence score — or look up who an address or number belongs to.

Watchlist

Know when something changes

Track people and companies over time and get a structured diff: job moves, headline edits, new posts, headcount. By API, or emailed.

Opportunity

Jobs and hiring teams

Postings, the people hiring for them, and every job a given person has posted.

Discover

Search LinkedIn itself

For people, companies and jobs the store has never seen, go and find them.

Slow once, then fast

The slow part of this is going to LinkedIn. It happens the first time a subject is asked about; every call after answers from what that fetch stored.

GET /api/v2/person/enrich
    ?handle=jane-doe-example

goes to LinkedIn now
seconds to minutes on a first call

One credit, charged only if somebody is found.

GET /api/v2/person/employment-history
    ?handle=jane-doe-example

answers from what enrich stored
milliseconds, never blocks

So are endorsements, interests and lookalikes.

Working in about a minute

Accept your invitation, choose a password, and call it.

curl 'https://api.rynora.dev/api/v2/person/enrich?handle=jane-doe-example' \
  -H 'X-API-Key: lsk_...'

{
  "success": true,
  "statusCode": 200,
  "data": {
    "name": "Jane Doe",
    "headline": "Engineer at Example Corp",
    "positions": [ ... ],
    "education": [ ... ]
  }
}

Every response carries X-Credits-Charged and X-Credits-Remaining.

Built to be used from a chat session

Rynora is an MCP server. Connect it and ask in plain language — the client calls the tools, and every call is billed and rate-limited exactly as if you had made it yourself.

claude mcp add --transport http rynora https://api.rynora.dev/mcp/   --header "Authorization: Bearer lsk_YOUR_KEY"

> use rynora to find engineers at example-corp who moved job this month

Or point any agent at the plain-text reference at /llms.txt, which has every endpoint, its parameters and the shape of what comes back.