Enrich a person profile from an email address with role, department, and company details.
Endpoint: POST https://api.skillboss.co/v1/run · Model: hunter/person-enrichment
Use cURL when you want the clearest raw HTTP example. This is the fastest way to validate auth, inputs, output shape, and the canonical endpoint before wiring the API into code or agent workflows.
curl -X POST https://api.skillboss.co/v1/run \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "hunter/person-enrichment",
"inputs": {
// Your parameters here
}
}'Start using Hunter Person Enrichment in under 60 seconds
FOR AI AGENTS
Base URL: https://api.skillboss.co/v1
Model: hunter/person-enrichment
Auth: Bearer token — get at skillboss.co/console
Pricing: $0.03/1M tokens, no subscription
Or auto-configure everything:
set up skillboss.co/skill.mdFOR DEVELOPERS
Get your API key at skillboss.co/console
POST to api.skillboss.co/v1 with model hunter/person-enrichment
Parse the JSON response. Auth, billing, and rate limits handled automatically.
Call Hunter Person Enrichment through one stable API surface
Ship integrations faster without vendor account setup
Use the capability directly inside human and agent workflows
Hunter Person Enrichment is a api available through SkillBoss. Teams use it to add Hunter Person Enrichment to apps, automations, and AI agent workflows without managing separate vendor credentials. This page gives both humans and agents one stable place to understand the capability, pricing path, and invocation pattern before they ship it into production.
Send a POST request to https://api.skillboss.co/v1/run with "model": "hunter/person-enrichment" and an "inputs" object. SkillBoss handles auth, billing, and the unified API layer. If you are testing the endpoint manually, start with the cURL or Python tab below. If you are wiring an autonomous agent, use the x402 or MPP tabs when the payment path matters.
SkillBoss gives you one API key, pay-as-you-go billing, and a consistent integration flow across many APIs. That reduces setup time and makes the endpoint easier to use in Claude Code, Cursor, Windsurf, and other agents. It also gives you a canonical public page, consistent docs, and one billing surface instead of forcing each team to juggle provider-specific auth and pricing rules.
Yes. This page is designed as a discovery surface for both humans and agents: clear capability framing, direct code examples, and a stable canonical URL make it easier to find, evaluate, and invoke. The structure is deliberate so search engines, agent runtimes, and developers can all understand what the endpoint does, how it is paid for, and which next pages matter.
Hunter Person Enrichment is better served through the standard SkillBoss API key flow. x402 and MPP work best when pricing is deterministic before execution, which is not the safest assumption for this endpoint.
One API key, 100+ models, zero markup
AI Agents
Tell your agent:
set up skillboss.co/skill.mdAuto-configures base URL, auth, and Hunter Person Enrichment access. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible agent.
Developers
1. Get API key at skillboss.co/console
2. POST to api.skillboss.co/v1/run
3. Model: hunter/person-enrichment
Pay-as-you-go. $0.03/1M tokens. No subscription required.