hyreflow Native

HOW in lib/hyreflow_native.py.

Kind: hyreflow Native — read this first

• First-party capability, no external vendor. Runs on hyreflow infrastructure.
• No BYOK, no API key. You never hold a key, so no separate scraper subscription is needed; every call is metered in hyreflow credits. One tool sits in a waterfall — profile lookup, the second step of linkedin_profile; every other native tool runs on its own.
• Three billing shapes. Job scrapes are async and pay-on-match: launching is free and you're charged per job returned on retrieval, so an empty or still-running result costs nothing. Post feeds, post search and post reactions are a single call charged per request — one page (up to 50 posts for a feed, up to 10 for a search or a reactions page), whatever the page holds; profile lookup is one profile per request, found or not. Postcode radius is free — no credits. Email verification is async and charged per address submitted, at launch; only safe-to-send addresses come back.

Job scrapes — the two-call (async) flow

A scrape takes a few minutes.

1. Launch with scrape_* → {request_id, status: "QUEUED"}. Free.
2. Poll with the matching get_*, passing that request_id → QUEUED → RUNNING → COMPLETED. On COMPLETED, result.jobs holds the scraped roles. Poll every ~10s until COMPLETED or FAILED — re-polls dedup per job, so a tighter loop costs nothing; the terminal poll bills the same page whenever it lands.

career_pages (a company's own careers site) · linkedin_jobs (by title + location, one company's page, or specific postings via linkedin_job_urls / linkedin_job_ids) · indeed_jobs · arbeitsagentur_jobs (the German federal employment board) · stepstone_jobs (Germany's largest commercial job board).

Post feeds — one call

profile_posts (a person, from linkedin.com/in/<username>) · company_posts (a company page, from linkedin.com/company/<username>). One call returns up to 50 posts newest-first with full text, engagement counts, the post URL, when it was posted and any companies tagged. Page back with the next_start each response returns.

Post search — one call

search_posts (alias post_search) finds public posts by what they say: keyword (required), scoped to date_posted — past-week by default, or past-24h / past-month / any. Narrow to authors whose headline matches with author_title ("Recruiter", "Talent Acquisition") — the way to catch recruiting-agency staff announcing a search without knowing their handles. Results are the same post record a feed returns, newest first (sort_by: "relevance" to rank instead), 10 per page; page forward with the next_page each response returns (null once the window is exhausted).

Post reactions — one call

post_reactions (get_post_reactions) reads the people who reacted to a LinkedIn post — the engagement list a feed row's totalReactionCount only counts. Pass the post's postUrl; one call returns up to 10 reactors with name, headline, profile URL and the reaction they left. reaction_type (LIKE, EMPATHY, PRAISE, INTEREST, FUNNY, APPRECIATION) narrows to one kind; total/total_pages report the whole set, so page forward with next_page (null at the end).

Profile lookup — second step of linkedin_profile

get_linkedin_profile reads one person's LinkedIn profile from its URL: name, headline, about, location, open-to-work and hiring flags, experience newest first (company, title, start/end as YYYY-MM, is_current), education, skills, certifications, languages. No email or phone. It runs second in the linkedin_profile waterfall, so reach it through linkedin_profile for a list; a URL with no profile behind it returns success: false and is still one charged request.

Postcode or city radius — free

places_within_radius (alias postcode_radius) turns a full postcode/ZIP or a city name (place) and a radius (unit mi or km, up to 25 km; country ISO-2) into the towns, villages and suburbs inside it, nearest first (50 by default, limit up to 200), as a locations list for people_search. People databases have no radius filter, so this town list is how a "within 3 miles of a postcode" or "within 20 km of a city" search runs.

Email verification — the default verifier

verify_emails checks each inbox for 1 to 50,000 addresses: launch (charged per address), poll get_verified_emails (free) until COMPLETED, then read result.emails — only the addresses safe to send to. Every other address is withheld and counted in result.withheld. Email enrichment already runs this check on every work email it finds. Ask for Enrichley, LeadMagic or Icypeas by name to use one of them instead.

Repost scan — hard-to-fill roles

repost_scan reads a company's PredictLeads job-opening history for the lookback (domain, plus its parent or subsidiary domains as related_domains) and returns only the roles that show a signal, each with its listings as evidence: repost (a fresh listing after an earlier one of the same role at the same site ran 21+ days and stopped), long-open (live 90+ days) or evergreen (three or more monthly relists, the latest live). titles or onet_codes narrow it to one role. Renamed roles come back in needs_review for a read of the two descriptions; warnings flags a cut-off history or stale crawl data.

Cost

Job scrapes: 0.05 credits per job returned, charged on retrieval — not per call (Arbeitsagentur adds +0.1 credits per job with recruiter details, up to 0.15 credits per job). You are charged for the jobs a poll actually delivers, so size the request to the ask: rows on the launch bounds what the scraper collects (Indeed defaults to 25), limit on the poll bounds what one page returns (10), and advancing to a further page bills that page's jobs. Post feeds, post search and post reactions: 0.2 credits per request (a feed page is up to 50 posts, a search or reactions page up to 10), charged whether or not the handle resolves or the keyword matches. Profile lookup: 0.2 credits per request, found or not (free on a miss inside the linkedin_profile waterfall). Postcode radius: free. Repost scan: 0.8 credits/page for each PredictLeads history page it pulls (one page per domain, a page holds 1,000 listings); the scan itself adds nothing. Email verification: 0.05 credits per address submitted, charged at launch; polling is free.

Handoff

The sourcing front end for a hiring-signal pipeline: scrape open roles → identify the hiring company → enrich the decision-maker → sequence. Post feeds add the timing layer — read what an account has been posting to open on a launch, a funding round or a hiring push rather than on nothing. Post search finds the accounts in the first place — who said "we're hiring" this week — before a feed reads one of them. Email verification closes the enrich step: verify the found addresses before they reach a sequence.