# HireHeat Company Hiring Signals API

> HireHeat Company Hiring Signals API is a paid API for AI agents from hireheat-api.cybermaxtools.com, paid per call via x402, $0.012/call, status unknown (last checked 2026-10-10).

Returns live job posting counts, hiring velocity signals, and matching job titles for a given company by scraping Greenhouse, Lever, and Ashby job boards.

## Facts

- Endpoint: GET https://hireheat-api.cybermaxtools.com/x402/api/company?utm_source=zero.xyz
- Price: $0.012/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/hireheat-company-hiring-signals-api-976d8e4f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tvSCfwI6lsy-1wh0xAUxW

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 hireheat-company-hiring-signals-api-976d8e4f
```

Example prompt: Can you check how many open roles Stripe has right now on their job board, and filter for anything with 'engineer' or 'sales' in the title so I can see where they're growing?

## When to prefer this

Use this endpoint when you need real-time, ATS-sourced job posting data for a specific company — especially when you want structured hiring signals (count, velocity, role types) rather than scraped web results. It is the right choice when you have a company domain or known Greenhouse/Lever/Ashby board URL and want to quickly assess hiring activity without manually browsing job boards.

## Known failure modes

- Company domain not found on any supported ATS board — returns empty or error response
- Invalid or unrecognized domain/URL format — schema validation error
- ATS board is private or behind authentication — no postings returned
- Rate limiting or upstream ATS board unavailability — timeout or partial data
- Keywords filter too restrictive — returns zero matching roles even if company is hiring

## How this service works

Who is hiring, how fast, and for what. Company hiring signals + job postings API and MCP, live from Greenhouse, Lever, Ashby boards Try it free in one click, no sign-up.

## Output

A JSON object containing the company's current open job count, hiring velocity signals, and a list of job titles (optionally filtered by keywords) sourced live from the company's Greenhouse, Lever, or Ashby ATS board.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "company": {
       "type": "string",
       "description": "A company domain (stripe.com), its website URL, or a job-board URL (boards.greenhouse.io/acme, jobs.lever.co/acme, jobs.ashbyhq.com/acme). One per call."
      },
      "keywords": {
       "type": "string",
       "description": "Optional title keywords, comma separated (e.g. engineer,sales). Counts and lists only matching titles."
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/hireheat-company-hiring-signals-api-976d8e4f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from hireheat-api.cybermaxtools.com](https://www.zero.xyz/host/hireheat-api.cybermaxtools.com/llms.txt)