People data API for Claude Code
One API for people data, built to be called by an agent: unify 30+ providers behind clean tools with JSON envelopes and a cost on every call.
you › Find a verified work email and a mobile number for the head of growth at acme.com, and save both to my leads table.
oxygen › Claude Code calls oxygen_find_email and oxygen_find_phone — one schema-shaped contract over 30+ providers. Each call returns a JSON envelope with the value, the source, and the cost, and persists straight to your table.
Wiring up people-data providers one by one, each with its own auth, schema, and rate limits, is the tax on every GTM project. Oxygen is the one contract over all of them, exposed as MCP tools and CLI commands an agent can call directly.
From Claude Code, call a single tool to find an email, a phone, a LinkedIn profile, or a full person record. Oxygen handles routing, fallback, rate limits, and cost, and returns a clean JSON envelope you can act on.
How it works
- 1
Add the Oxygen MCP server
Claude Code gets a set of people-data tools with clear descriptors and JSON envelopes, no per-provider glue code.
- 2
Call one tool
Find an email, phone, LinkedIn, or search for people by criteria. Oxygen routes across providers and falls back automatically.
- 3
Get a clean envelope
Every response carries the value, its source, and its cost, so your agent can decide what to do next.
- 4
Persist and reuse
Write results to your own Postgres tables so the same lookup is never paid for twice.
What you get
- One contract over 30+ people-data providers
- MCP tools and CLI commands with schema-shaped JSON envelopes
- Automatic provider routing, fallback, and rate-limit handling
- Cost and source on every call; bring your own keys or use credits
- Results persist to a Postgres database you own
Frequently asked questions
Is this a REST API or MCP tools?
Both. The same behavior is exposed as MCP tools for agents like Claude Code, as CLI commands, and over HTTP, with one auth and one response envelope across all three.
How is this different from calling a provider directly?
You call one contract instead of many. Oxygen handles routing, fallback across providers, rate limits, cost tracking, and caching, and stores results in your own database.
Can I bring my own provider keys?
Yes. Use your own keys for BYOK economics, or use Oxygen managed credits. Either way the cost is recorded per call.
Run people data api from your agent
Point Claude Code at Oxygen and let it do the work, on a database you own.