# Leadsforge Phone Enrichment

> Leadsforge Phone Enrichment is a paid API for AI agents from x402.orthogonal.com, paid per call via x402, $0.3/call, status unknown (last checked 2026-09-13).

Finds a phone number for a person given their name and company or LinkedIn URL, returned synchronously.

## Facts

- Endpoint: POST https://x402.orthogonal.com/leadsforge/enrichment/phone
- Price: $0.3/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/leadsforge-phone-enrichment-192d81e7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kw50-Oem9FsJKoHJ-sESU

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 leadsforge-phone-enrichment-192d81e7 -d '<json body>'
```

Example prompt: Can you find the phone number for Sarah Chen, who works at Acme Corp? Her LinkedIn is linkedin.com/in/sarahchen-acme.

## When to prefer this

Use this endpoint when you need a phone number for a specific named individual at a company and have at least their full name plus either company name or LinkedIn profile URL. It is synchronous and returns results immediately, making it suitable for real-time agent workflows. Prefer this over email enrichment endpoints when the goal is direct phone outreach.

## Known failure modes

- Person not found in database — no phone number returned
- Ambiguous identity match when name is common and no LinkedIn URL or company domain is provided
- LinkedIn URL invalid or profile not indexed
- Rate limiting or payment failure via x402 protocol
- Partial match returned if company or name is misspelled

## How this service works

Find phone number for a person synchronously. Provide name + company or LinkedIn URL.

## Output

Returns the phone number associated with the specified person, along with any available contact metadata. Response is delivered synchronously, typically including a direct or mobile number tied to the identified individual.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "company": {
   "type": "string",
   "description": "Company name"
  },
  "lastName": {
   "type": "string",
   "description": "Person's last name"
  },
  "personID": {
   "type": "string",
   "description": "Leadsforge person ID"
  },
  "firstName": {
   "type": "string",
   "description": "Person's first name"
  },
  "externalID": {
   "type": "string",
   "description": "External reference ID"
  },
  "linkedinURL": {
   "type": "string",
   "description": "LinkedIn profile URL"
  },
  "companyDomain": {
   "type": "string",
   "description": "Company domain"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/leadsforge-phone-enrichment-192d81e7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.orthogonal.com](https://www.zero.xyz/host/x402.orthogonal.com/llms.txt)