For Agents
Check whether a company is hiring, pull its open reqs and hiring momentum, find companies hiring for a role or ICP, and watch companies for new or closed reqs with Reqbeat.
Use for: Is Acme hiring right now?, List all open engineering reqs at this company, Find companies hiring a Head of Data in Germany, Get the hiring momentum for stripe.com before my sales call
Not supported: Does not post jobs, manage applicants, or run an ATS. Use for reading company hiring signals, job market searches, and hiring-event watches only.
The Reqbeat API turns public job postings into company hiring signals: it tells you whether a company is hiring, lists its open reqs deduped across job boards, and scores hiring velocity, first hires per function, hard-to-fill reposts, ATS vendor switches, and a calibrated intent score. It searches open roles and hiring companies across the market, matches live reqs to an ideal customer profile, and returns firmographics gathered from ATS and job board data. Watches on a company or saved search deliver opened, reposted, reobserved, or closed events to your webhooks, with a cursor-based change feed, delivery log, and replay.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Reqbeat API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Freqbeat.com%2Freqbeat" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Freqbeat.com%2Freqbeat" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Reqbeat API.
Check whether a company is hiring and list its open reqs deduped across job boards, filtered by function or country
Read a company's hiring pulse: velocity, direction, and momentum from ATS and board data
Find companies hiring for a role by geo, industry, headcount_band, or source_type, excluding agencies
Match live reqs to an ideal customer profile with salary_min_usd and salary_max_usd bounds
Watch a company or saved search for opened, reposted, reobserved, or closed reqs and deliver them to a webhook
Resolve a company id from a domain or name and enrich it with firmographics
Report a conversion outcome on a company and read back attribution of the signals that won
Patterns agents use Reqbeat API for, with concrete tasks.
★ Agent pre-call research
Before a sales or recruiting outreach, an agent connected through Jentic resolves the company from its domain, then pulls the pre-action brief, which joins hiring signals into one bounded call. When data is cold, the brief returns 202 with a job_id and status crawling, and the agent checks back later.
Call GET /v1/companies/resolve with domain set to acme.com, then GET /v1/companies/{company_id}/pre-action-brief for the returned id
Hiring-intent prospecting
Revenue teams find accounts actively hiring for roles their product serves. The role search filters by role, geo, since, industry, and headcount_band and can exclude agencies, while the qualified-reqs search takes ICP criteria with salary bounds and an option to include each company's pulse.
Call GET /v1/reqs/search with role set to 'data engineer', geo set to DE, and exclude_agencies set to true
Account watches with webhooks
Register a webhook endpoint, then create a watch on a company or saved search with event_types such as opened and closed. Deliveries are logged and can be replayed, and the events feed returns the same changes since a cursor for polling setups.
Call POST /v1/webhooks with url set to the receiver, then POST /v1/watches with company_id, event_types set to ["opened", "closed"], and the returned webhook_endpoint_id
Closed-loop signal attribution
After a deal closes, report the outcome on the company with observed_at and optionally the req_key that triggered it. Reqbeat uses submitted outcomes for its calibrated intent score, and the attribution operation shows which delivered signals were won.
Call POST /v1/companies/{company_id}/outcomes with outcome set to your conversion label and observed_at set to 2026-11-12T00:00:00Z, then GET /v1/attribution
38 endpoints — the reqbeat api turns public job postings into company hiring signals: it tells you whether a company is hiring, lists its open reqs deduped across job boards, and scores hiring velocity, first hires per function, hard-to-fill reposts, ats vendor switches, and a calibrated intent score.
METHOD
PATH
DESCRIPTION
/v1/companies/{company_id}/is-hiring
Is this company hiring?
/v1/companies/{company_id}/open-reqs
Company's open reqs deduped across boards
/v1/companies/{company_id}/hiring-pulse
Hiring velocity and momentum
/v1/reqs/search
Find companies hiring for a role
/v1/reqs/qualified
Find live reqs matching an ICP
/v1/companies/resolve
Find a company id by domain or name
/v1/watches
Watch a company or saved search
/v1/events
Change feed since your cursor
/v1/companies/{company_id}/is-hiring
Is this company hiring?
/v1/companies/{company_id}/open-reqs
Company's open reqs deduped across boards
/v1/companies/{company_id}/hiring-pulse
Hiring velocity and momentum
/v1/reqs/search
Find companies hiring for a role
/v1/reqs/qualified
Find live reqs matching an ICP
/v1/companies/resolve
Find a company id by domain or name
/v1/watches
Watch a company or saved search
/v1/events
Change feed since your cursor
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Wiring Reqbeat by hand means handling its X-API-Key header, Idempotency-Key headers on paid routes, 202 crawling responses, and webhook registration before watches. Through Jentic you install once, import Reqbeat from the API Directory, store the key once, and your agent calls it.
Permission scoping
Reqbeat puts company_id in the URL path (/v1/companies/{company_id}/open-reqs), so a rule can confine your agent to the companies you name. You choose the operations it may call, so destructive ones like key revocation, watch cancellation, or account pause are not included unless you add them.
Credential isolation
Your Reqbeat API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'is this company hiring' or 'watch a company for new jobs', and Jentic returns the matching Reqbeat operation with its input schema so the agent sends the right company_id and filters.
Alternatives and complements available in the Jentic catalogue.
Specific to using Reqbeat API through Jentic.
What authentication does the Reqbeat API use?
Per its OpenAPI spec, the Reqbeat API authenticates with an API key sent in the X-API-Key header, and GET /v1/whoami shows what your key resolves to. Keys can be listed, issued, rotated, and revoked through the /v1/keys operations. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at execution time.
Can I check whether a specific company is hiring with Reqbeat?
Yes. Resolve the company with GET /v1/companies/resolve using its domain or name, then call GET /v1/companies/{company_id}/is-hiring. For detail, GET /v1/companies/{company_id}/open-reqs lists its open reqs deduped across boards and accepts function and country filters.
What happens when Reqbeat has no fresh data for a company?
The hiring pulse and pre-action brief operations honor a max_age parameter in seconds. When no ATS or board data exists yet and max_age demands freshness, they return 202 with a job_id and status crawling instead of a synchronous body, so retry the call later.
How do Reqbeat watches deliver events?
Register an endpoint with POST /v1/webhooks, then create a watch with POST /v1/watches, giving event_types from opened, reobserved, reposted, and closed plus the webhook_endpoint_id. The delivery log at /v1/webhook-deliveries shows each attempt, and a delivery can be replayed.
What are the rate limits for the Reqbeat API?
The OpenAPI spec defines a rate_limited error but does not publish the limits. GET /v1/usage reports your metered usage over a rolling window; see https://reqbeat.com for plan limits.
How do I find companies hiring for a role through Jentic?
Search Jentic for 'find companies hiring for a role'. Jentic returns GET /v1/reqs/search with its input schema; your agent sets role, geo, and since, and Jentic sends the call with your stored key. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a Reqbeat MCP server?
You don't need an MCP server to give your agent Reqbeat. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent discovers the company, search, and watch operations on demand instead of carrying all their tool definitions in context.
Can I limit what my agent is allowed to do with the Reqbeat API?
Yes. A research agent could be allowed the GET operations under /v1/companies/{company_id}/ for the accounts it covers, plus GET /v1/reqs/search, and nothing else. It can then read hiring signals but cannot issue or revoke keys, pause the account, or create watches.
GET STARTED