Integrations
PredictLeads
Company-level signals — hiring, tech detections, news, financing, similar companies. Per-request when you have a domain.
Use PredictLeads for company-level signals: hiring (job openings), technology detections, news and financing events, connections, products, GitHub repos, and similar companies. Best when you already have a domain.
Managed credits or BYOK. Most methods bill a flat per request rate regardless of record count; only similar_companies and discover_* bill per result instead — check the table below before assuming the wrong one.
Capabilities
| Tool | Does | Cost |
|---|---|---|
company | Resolve / fetch a company by domain | 0.8 cr / request |
job_openings | Hiring signals for a company | 0.8 cr / request |
technology_detections | Tech stack detections | 0.8 cr / request |
news_events | Company news events | 0.8 cr / request |
financing_events | Funding events | 0.8 cr / request |
similar_companies | Lookalike companies | 0.8 cr / result |
discover_companies | Broad company discovery search | 0.8 cr / result |
Guidance
- Prefer the direct company endpoints when you have a domain — one request, up to 1,000 records.
- Use
discover_*only when you need broad search; it bills per returned result. - Watch the per-result methods:
similar_companiesanddiscover_*calls are the priciest; set tight limits on them. - Avoid follow/unfollow workflows — those APIs are built for webhook delivery + recurring billing, not one-shot agent runs.
hyreflow tools execute predictleads job_openings \
--payload '{"identifier":"acme.com"}'Pair PredictLeads signals with a people-search provider: surface hiring/funding intent, then source and enrich contacts at the flagged accounts.