Person Enrichment API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026

Person lookup from email: name, title, company, social profiles. x402.

The publisher's own server: person.work — Agent-maintained CV

Overview

AI-generated overview

A remote MCP endpoint that enriches a person's profile from an email address, returning name, job title, company, social links and location for a per-call fee.

What you can do
Enrich a person profile from an email address, returning structured JSON with full name, job title, company, LinkedIn, GitHub, Twitter, avatar, location and domain.
When to use it
Useful for sales prospecting, lead qualification, account mapping, personalizing outreach emails, or filling in CRM contact records when you already have an email address.
Requirements
A remote MCP endpoint; no local runtime, signup or API key. Calls are paid per request in USDC on the Base L2 network through the x402 protocol, so an x402-capable client and a funded wallet are needed.
Before you install
Every enrichment call costs money (listed at $0.02 per call) in USDC on Base, so an agent can spend funds automatically. Email addresses are sent to a third-party service, and returned profile data about individuals should be handled with privacy care.

Installation

In SourceWeft

  1. Open Person Enrichment API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fperson-enrichment/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "person-enrichment-api": {
      "type": "sse",
      "url": "https://person-enrichment.api.klymax402.com/mcp"
    }
  }
}

README

Person Enrichment API

[MCP Server] [x402] [License: MIT]

Person enrichment from email. Full name, job title, company, LinkedIn, GitHub, Twitter, avatar, location. Ideal for lead research. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

json
{  "mcpServers": {    "person-enrichment": {      "url": "https://person-enrichment.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash
curl "https://person-enrichment.api.klymax402.com/api/[email protected]"# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
person_enrich_from_emailGET/api/enrich$0.02Enrich a person profile from their email address
person_enrich_from_emailPOST/api/enrich$0.02Enrich a person profile from their email address

person_enrich_from_email

Enrich a person's profile with additional data from their email address, name, domain, or LinkedIn URL. Alternative to Apollo people-enrich at 5x lower cost. Returns structured JSON with full contact and professional details.

Parameters

NameTypeRequiredDescription
emailstringyesEmail address to enrich (e.g. [email protected])

Example response:

json
{"fullName":"Jane Smith","jobTitle":"VP Engineering","company":"Acme Corp","linkedin":"https://linkedin.com/in/janesmith","github":"https://github.com/janesmith","location":"San Francisco, CA","avatar":"https://gravatar.com/abc123","domain":"acme.com"}

When to use: outreach to personalize emails, enrich CRM records, search for people/contacts, or research decision-makers. Essential for sales prospecting, lead qualification, and account mapping. Drop-in replacement for Apollo person enrichment.

Not for: email validation (use email_verify_address), company data (use company_enrich_from_domain), social profiles by username (use social_lookup_profile), finding email addresses (use email_find_by_name).

person_enrich_from_email

Enrich a person's profile with additional data from their email address, name, domain, or LinkedIn URL. Alternative to Apollo people-enrich at 5x lower cost. Returns structured JSON with full contact and professional details.

Parameters

NameTypeRequiredDescription
emailstringyesEmail address to enrich (e.g. [email protected])

Example response:

json
{"fullName":"Jane Smith","jobTitle":"VP Engineering","company":"Acme Corp","linkedin":"https://linkedin.com/in/janesmith","github":"https://github.com/janesmith","location":"San Francisco, CA","avatar":"https://gravatar.com/abc123","domain":"acme.com"}

When to use: outreach to personalize emails, enrich CRM records, search for people/contacts, or research decision-makers. Essential for sales prospecting, lead qualification, and account mapping. Drop-in replacement for Apollo person enrichment.

Not for: email validation (use email_verify_address), company data (use company_enrich_from_domain), social profiles by username (use social_lookup_profile), finding email addresses (use email_find_by_name).

Example agent prompts

  • "Enrich a person's profile with additional data from their email address, name, domain, or LinkedIn URL"
  • "Enrich a person's profile with additional data from their email address, name, domain, or LinkedIn URL"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Source: README.md at commit b21bdd4

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Person integrations