Live API·people · companies · jobs · activity

The freshest answer, the moment you ask.

A record that aged out last quarter is worse than no record. The Live API resolves a person, a company, a job posting, or its activity in real time, fetched on request, so the data you act on is true right now. Every endpoint is one focused lookup.

Start Free Read the docs

Real-time on demandSub-second typicalOne key across products

200 · 312ms

await renidly.live.people.enrich(eid)

{
  "entityId": "prsn_9f2a41",
  "headline": "VP Engineering at Vercel",
  "company": "Vercel",
  "location": "Berlin, DE",
  "follower_count": 18204
}

Data Live Emails

//What you can do

One subject, resolved fresh, every angle of it.

200 · 298ms

await renidly.live.people.employmentHistory(eid)

{
  "experience": [
    {
      "company": "Vercel",
      "title": "VP Engineering",
      "start_year": 2023,
      "end_year": 0
    },
    {
      "company": "Stripe",
      "title": "Staff Engineer",
      "start_year": 2020,
      "end_year": 2023
    }
  ]
}

01History

The full career, in order

Pull a person’s complete employment history on demand, every role and company with its dates, resolved fresh. Reach for endorsements, interests, and look-alikes on the same subject when you need the fuller picture.

Every role and company, with tenure
Endorsements, interests, and look-alikes
Resolved live, not from a stale export

200 · 181ms

await renidly.live.discover.people({ keyword: "founder" })

{
  "count": 128,
  "results": [
    {
      "full_name": "Nadia Frost",
      "headline": "Founder · fintech · London"
    },
    {
      "full_name": "Ravi Oke",
      "headline": "Co-founder · payments · NYC"
    }
  ]
}

03Discover

Search all three, live

Run a real-time discovery search across people, organizations, and job postings by keyword and filters. You get the current result set, not an index that went stale between crawls, then feed any result straight into an enrich call.

People, companies, and opportunities
Keyword and structured filters
Resolve a handle or slug once, reuse the id

200 · 205ms

await renidly.live.activities.feed(eid)

{
  "activities": [
    {
      "type": "post",
      "text": "Shipped v2 of the pipeline SDK",
      "reactions": 214
    },
    {
      "type": "reaction",
      "text": "on data quality at scale"
    }
  ]
}

02Activity

Read intent as it happens

The latest posts, reactions, and replies for a person or a company, fresh enough to time your outreach to a real moment. Pull the feed, a single post in detail, its reactions, or the replies, including the ones a person wrote elsewhere.

Posts, reactions, and replies
Per person or per organization
Fresh enough for intent signals

200 · 286ms

await renidly.live.organizations.headcount(id)

{
  "id": "1441",
  "name": "Vercel",
  "staff_count": 460,
  "growth_30d": 22,
  "top_function": "Engineering"
}

04Companies

A company, resolved right now

Enrich an organization to its full profile, read live headcount and where it is growing, and pull its posts, its open roles, and the pages affiliated with it. The current picture, never a cached one.

Full profile and live headcount
Similar and affiliated companies
Its posts and its open roles

//In depth

Everything the Live API resolves, up close.

01People

One person, every angle

Resolve a public handle to a stable id, then enrich the full profile, walk the employment history, read endorsements and interests, or find look-alikes. Each one is a single focused call that returns fresh.

02Jobs

The hiring signal, live

Open a job posting in full, see the people on its hiring team, find similar and related roles, and list every opportunity a company or a person has posted. Timing a pitch to a real opening starts here.

03Discovery

Find, do not just fetch

When you do not have an id yet, discover people, organizations, and opportunities by keyword and filters, then pass the results straight into any enrich call. No id to construct, no guesswork.

04Freshness

Fetched on request

Every endpoint returns fresh data on demand. Repeat lookups of the same subject are served from a short cache for free, so re-reading a record inside a window never bills twice.

//In practice

One handle in, a full record out.

One typed client, the same key across all three APIs. No SDK? It is one authenticated HTTPS call and one JSON envelope.

python · pip install renidlyready

# resolve a handle once, reuse the id
eid = renidly.live.people.resolve_handle("adameyer").entityId
person = renidly.live.people.enrich(eid)
→ VP Engineering · Vercel · Berlin
 
# live headcount for a company
renidly.live.organizations.headcount(oid)
→ 460 (+22 this month)
$ ▍

// Latency

<500ms

Typical time to resolve a live lookup.

// Coverage

99.99%

Coverage of the B2B identity graph.

// Billing

0 credits

On cache hits and on failed calls.

//Why Renidly

Fresh enough to trust in a live path.

Fresh, not cached-stale

Every call fetches the current snapshot on demand. When you need the truth as of now, not last month, this is the surface to reach for.

One key, one envelope

The same header and JSON shape as the Data and Email APIs, billed from one balance. Mix all three in a single integration.

Sync and async SDKs

The identical surface in Python and Node, sync or async, with retries and pagination already handled for you.

You pay only for success

Cache hits and failed lookups cost nothing. Credits move only on a live result that comes back.

//What changes for you

Every lead is resolved the moment it lands and routed in the same request, so speed to lead drops from minutes to milliseconds and no rep ever works a stale record again.

Start Free