# Hunter Company Enrichment via Locus x402

> Hunter Company Enrichment via Locus x402 is a paid API for AI agents from hunter.x402.paywithlocus.com, paid per call via x402, $0.013/call, status unknown (last checked 2026-09-15).

Enriches a company domain with firmographic and contact data using Hunter's company enrichment API, billed per-call via x402 micropayments.

## Facts

- Endpoint: POST https://hunter.x402.paywithlocus.com/hunter/company-enrichment
- Price: $0.013/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/hunter-company-enrichment-via-locus-x402-9812b733
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gqt2uwNLYYJ36CCoOVL35

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 hunter-company-enrichment-via-locus-x402-9812b733 -d '<json body>'
```

Example prompt: Can you pull up the company details for stripe.com — I need their industry, size, and any other firmographic info Hunter has on them?

## When to prefer this

Use this endpoint when you need structured firmographic data about a company given only its domain name, especially in B2B sales, lead qualification, or outreach workflows. Prefer this over email-finding endpoints when the goal is company-level intelligence (size, industry, location) rather than individual contact discovery. The x402 micropayment model makes it cost-effective for per-domain lookups without subscription overhead.

## Known failure modes

- Domain not found in Hunter's database — returns empty or sparse data object
- Invalid domain format — may return validation error
- Domain exists but has no enrichment data — data field returns empty object
- Network or upstream Hunter API timeout — request may fail without data
- x402 payment failure — call not processed if micropayment is rejected

## How this service works

Locus public pay-per-use API

## Output

Returns a JSON object containing firmographic details about the company associated with the provided domain, including fields such as company name, industry, employee count, location, description, and social media profiles, along with x402 payment confirmation metadata (settled USDC, request ID, and status URL).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "domain": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "payment": {
   "scheme": "exact",
   "settledUsdc": "0.001000",
   "authorizedMaxUsdc": "0.001000"
  },
  "request": {
   "id": "00000000-0000-4000-8000-000000000000",
   "statusUrl": "/requests/00000000-0000-4000-8000-000000000000"
  },
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/hunter-company-enrichment-via-locus-x402-9812b733/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from hunter.x402.paywithlocus.com](https://www.zero.xyz/host/hunter.x402.paywithlocus.com/llms.txt)