APIDirect API access through SkillBoss

Hunter Domain Search API

Find company email addresses and contact patterns for a domain using Hunter.

Modelhunter/domain-search
Pricing$0.04/1M tokens
AuthBearer YOUR_API_KEY
Paymentsx402 + MPP

Interface

Endpoint: POST https://api.skillboss.co/v1/run · Model: hunter/domain-search

Standard API flow

cURL interface

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
curl -X POST https://api.skillboss.co/v1/run \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "hunter/domain-search",
    "inputs": {
      // Your parameters here
    }
  }'

Quick Start

Start using Hunter Domain Search in under 60 seconds

FOR AI AGENTS

Base URL: https://api.skillboss.co/v1

Model: hunter/domain-search

Auth: Bearer token — get at skillboss.co/console

Pricing: $0.04/1M tokens, no subscription

Or auto-configure everything:

set up skillboss.co/skill.md

FOR DEVELOPERS

1

Get your API key at skillboss.co/console

2

POST to api.skillboss.co/v1 with model hunter/domain-search

3

Parse the JSON response. Auth, billing, and rate limits handled automatically.

Best-Fit Use Cases

3 workflows
01

Call Hunter Domain Search through one stable API surface

02

Ship integrations faster without vendor account setup

03

Use the capability directly inside human and agent workflows

Frequently Asked Questions

Docs · Browse all APIs

What is the Hunter Domain Search API used for?

Hunter Domain Search is a api available through SkillBoss. Teams use it to add Hunter Domain Search 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.

How do I call Hunter Domain Search on SkillBoss?

Send a POST request to https://api.skillboss.co/v1/run with "model": "hunter/domain-search" 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.

Why use SkillBoss instead of the native hunter setup?

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.

Is Hunter Domain Search good for AI agents as well as human developers?

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.

Does Hunter Domain Search support x402 or MPP machine payments?

Hunter Domain Search 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.

Start using Hunter Domain Search now

One API key, 100+ models, zero markup

AI Agents

Tell your agent:

set up skillboss.co/skill.md

Auto-configures base URL, auth, and Hunter Domain Search 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/domain-search

Pay-as-you-go. $0.04/1M tokens. No subscription required.