Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Data Enrichment / Reqbeat API
Reqbeat API logo

Reqbeat API

61
AI ReadinessAI-Aware (B-)61/100
See full scorecard
Official vendor OpenAPI document · agent-readyData EnrichmentCompany DataapiKey (X-API-Key header)38 EndpointsREST

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.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Reqbeat API to your agent

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.

1

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" | sh
2

Step 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 instance

Jentic 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.

Capabilities

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

Use Cases

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

Key Endpoints

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

GET

/v1/companies/{company_id}/is-hiring

Is this company hiring?

GET

/v1/companies/{company_id}/open-reqs

Company's open reqs deduped across boards

GET

/v1/companies/{company_id}/hiring-pulse

Hiring velocity and momentum

GET

/v1/reqs/search

Find companies hiring for a role

POST

/v1/reqs/qualified

Find live reqs matching an ICP

GET

/v1/companies/resolve

Find a company id by domain or name

POST

/v1/watches

Watch a company or saved search

GET

/v1/events

Change feed since your cursor

GET

/v1/companies/{company_id}/is-hiring

Is this company hiring?

GET

/v1/companies/{company_id}/open-reqs

Company's open reqs deduped across boards

GET

/v1/companies/{company_id}/hiring-pulse

Hiring velocity and momentum

GET

/v1/reqs/search

Find companies hiring for a role

POST

/v1/reqs/qualified

Find live reqs matching an ICP

GET

/v1/companies/resolve

Find a company id by domain or name

POST

/v1/watches

Watch a company or saved search

GET

/v1/events

Change feed since your cursor

Jentic AI Readiness Score

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.

R

Reqbeat API

- AI-Aware (B-)
61/100
93
Foundational Compliance
63
Developer Experience & Jentic Compatibility
44
AI-Readiness & Agent Experience
94
Agent Usability
50
Security
56
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
93

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

44

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4
26%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

51%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

50

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1
50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

56

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: CSignals: 1
56%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

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.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

TheirStack API

→

Job postings and technographic data

Choose TheirStack when you need job postings searched by the technologies companies mention

Alternative

Crustdata API

→

Company and people data with headcount signals

Choose Crustdata for broader firmographic and headcount data beyond hiring reqs

Complementary

Apollo.io API

→

Contact search and enrichment for outreach

Use Apollo after Reqbeat flags a hiring account, to find the contacts to reach

FAQs

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

Start building with Reqbeat API

Explore with Jentic One
View OpenAPI Document