# Radar Company Hiring Signals History

> Radar Company Hiring Signals History is a paid API for AI agents from 2-29-135-242.sslip.io, paid per call via x402, $0.02/call, status unknown (last checked 2026-11-21).

Returns historical and current job posting data for companies, including hiring activity rankings, new/closed/open postings, and daily hiring history filtered by ATS, keywords, location, and department.

## Facts

- Endpoint: POST https://2-29-135-242.sslip.io/x402/company-hiring-signals-history?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/radar-company-hiring-signals-history-39562ead
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3LqVXaYcz54--iDeH5PWV

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability radar-company-hiring-signals-history-39562ead -d '<json body>'
```

Example prompt: Show me the top 50 companies ranked by new job postings since 2024-01-01, filtered to engineering roles only, using Greenhouse or Lever as their ATS — I want to see which companies are on the biggest hiring sprees right now.

## When to prefer this

Use this endpoint when you need structured, historical job posting data aggregated across multiple companies and ATS platforms (Greenhouse, Lever, Ashby). It is ideal for competitive intelligence, talent market research, recruiting signal monitoring, or tracking hiring ramps at specific companies. Prefer this over generic job search APIs when you need daily time-series hiring data, ranking by hiring velocity, or filtering across company, location, department, and ATS simultaneously.

## Known failure modes

- Missing required 'mode' field returns a validation error
- Invalid company slug returns empty results with no error
- 'companies' mode without specifying companies array returns an error
- Date format not in YYYY-MM-DD causes rejection
- Exceeding limit of 100 returns capped or error response
- No matching postings for given filters returns count 0 with empty items
- Payment failure via x402 returns 402 and no results

## How this service works

Fast tools (web read, domain RDAP/DNS/SSL, Federal Register, clinical trials, OSV vulnerabilities, literature, e-mail auth) and data APIs on official/open data (leads, tenders, SEC filings, VAT, geocoding, aviation...). POST JSON, pay per call in USDC on Base via x402. Charged only when results are returned.

## Output

A JSON object with a count and an array of result items, each representing a company or job posting with fields like company slug, job title, location, department, ATS, posting dates, open/new/closed job counts, and daily history depending on the selected mode.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ats": {
   "type": "array",
   "items": {
    "enum": [
     "greenhouse",
     "lever",
     "ashby"
    ],
    "type": "string"
   },
   "maxItems": 100,
   "description": "Limit to companies using these systems. Empty = all three."
  },
  "mode": {
   "enum": [
    "top_hiring",
    "companies",
    "new_jobs",
    "closed_jobs",
    "open_jobs"
   ],
   "type": "string",
   "example": "top_hiring",
   "description": "top_hiring = companies ranked by hiring activity; companies = current numbers plus daily history for chosen companies; new_jobs = postings first seen after the archive baseline; closed_jobs = postings that disappeared (with days open); open_jobs = currently open postings."
  },
  "limit": {
   "type": "integer",
   "default": 20,
   "example": 50,
   "maximum": 100,
   "minimum": 1,
   "description": "Maximum number of rows to return (1 to 1000). You pay per result."
  },
  "since": {
   "type": "string",
   "description": "Job modes only: postings first seen (or closed) since this date, format YYYY-MM-DD. Empty = since the start of the archive."
  },
  "sortBy": {
   "enum": [
    "newJobs",
    "openJobs",
    "openJobsDelta",
    "closedJobs"
   ],
   "type": "string",
   "example": "newJobs",
   "description": "Ranking for top_hiring mode: new postings, open postings, change in open postings, or closed postings over the lookback window."
  },
  "keywords": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "example": [
    "engineer",
    "sales"
   ],
   "maxItems": 100,
   "description": "Job modes only: keep postings whose title contains any of these words (case-insensitive). Empty = all titles."
  },
  "location": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "maxItems": 100,
   "description": "Job modes only: keep postings whose location contains any of these texts, for example Berlin or United States. Empty = all locations."
  },
  "companies": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "example": [
    "stripe",
    "writer"
   ],
   "maxItems": 100,
   "description": "Company board slugs (for example stripe) or company names. Required in companies mode; optional filter in the job modes."
  },
  "department": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "maxItems": 100,
   "description": "Job modes only: keep postings in these departments, for example Sales or Engineering. Empty = all departments."
  },
  "remo
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "count": 1,
  "items": [
   {
    "...": "one result object"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/radar-company-hiring-signals-history-39562ead/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 2-29-135-242.sslip.io](https://www.zero.xyz/host/2-29-135-242.sslip.io/llms.txt)
