# Icypeas People Search

> Icypeas People Search is a paid API for AI agents from x402.orthogonal.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Searches a professional lead database for people matching filters like name, job title, company, skills, location, and more, returning paginated profile, job, and company data.

## Facts

- Endpoint: POST https://x402.orthogonal.com/icypeas/api/find-people
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/icypeas-people-search-dfab31fb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IQSZnjSUbt2GsnJuDo4dn

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 icypeas-people-search-dfab31fb -d '<json body>'
```

Example prompt: Find me people who are currently Senior Software Engineers at companies in the fintech space with a headcount between 50 and 500 — I want up to 10 results, filtered to those with Python skills located in San Francisco.

## When to prefer this

Choose this endpoint when you need to search a professional lead database with multiple simultaneous filters (title, company, skills, location, school, language) and require paginated results. Prefer it over general web search when you need structured, filterable professional profile data rather than raw text. It is especially useful for B2B sales prospecting, recruiting, and alumni or community outreach where precision filters matter.

## Known failure modes

- No results returned when filters are too narrow or specific
- Invalid filter field names cause request rejection
- Pagination token from a different query causes unexpected results
- Rate limiting or quota exhaustion returns an error
- Missing required query wrapper object causes schema validation failure

## How this service works

Search the lead database for people matching filters. Returns paginated results with profile, job, and company data. Filters: firstname, lastname, currentJobTitle, pastJobTitle, currentCompanyName, pastCompanyName, currentCompanyUrn, currentCompanyWebsite, currentCompanyId, school, languages, skills, location, keyword, headcount.

## Output

Returns a paginated list of matching professional profiles, each containing personal details (name, location, languages), current and past job titles, company information (name, website, headcount), skills, education, and a pagination token to fetch the next page of results.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "query": {
   "type": "object",
   "description": "Query with include/exclude filters or range operators"
  },
  "pagination": {
   "type": "object",
   "description": "Pagination with size (results per page) and token (from previous response)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/icypeas-people-search-dfab31fb/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)