Every agent needs a handler.

Your agent needs access to real services to do real work. handler is that access — with your rules built in.

Get Early Access How it works ↓

agent terminal

you (the owner)

One key. Every service. Your rules.

Every call flows through the same pipeline. handler decides what to approve, hold, or block.

owner dashboard

your agent

request

handler

rules

Apollo.io

Firecrawl

E2B

Exa

Browserbase

—

Add to your agent's MCP config. That's the entire setup.

{
  "mcpServers": {
    "handler": {
      "url": "https://mcp.usehandler.dev/sse",
      "headers": {
        "Authorization": "Bearer sk-hndlr-your-key"
      }
    }
  }
}

Your rules. Enforced on every call.

Each agent gets its own key and its own rules. Like a corporate card programme — each employee gets a card with their own limit.

research-agent sk-hndlr-yyyy

auto_approve_below

5 credits executes silently

notify_above

20 credits pauses and asks you

hard_cap_per_call

50 credits nothing over this

monthly_cap

200 credits hard stop

ops-agent sk-hndlr-zzzz

auto_approve_below

1 credit tight control

notify_above

3 credits almost everything needs approval

hard_cap_per_call

20 credits nothing over this

monthly_cap

30 credits hard stop

1 credit = ~10 contact lookups

1 credit = ~5 pages scraped

1 credit = ~1 min compute

1 credit = ~20 semantic searches

Credit exchange rates are illustrative. Final pricing at launch.

Five services at launch. More coming.

Your agent calls handler. handler calls the service. One key for everything.

B2B

Apollo.io

Data — B2B

Contact search, email and phone lookup, company data. Aggregated with Clearbit and Hunter for best results.

~0.1 credits per lookup

WEB

Firecrawl

Data — Web

Web scraping and clean markdown extraction from any URL. Handles JavaScript rendering.

~0.2 credits per page

RUN

E2B

Execution

Sandboxed code execution. Python, JavaScript, and more. Your agent writes code, E2B runs it.

~1 credit per minute

SRC

Exa

Data — Web

Neural semantic web search. Find pages by meaning, not just keywords.

~0.05 credits per search

BRW

Browserbase

Execution

Full browser automation. JavaScript rendering, bot detection bypass, session persistence.

~2 credits per session

More coming

Polygon.io, RunPod, Reddit, Twitter/X, Clearbit, Crunchbase, and more.

Get notified ↓

Credit costs are illustrative. Final pricing at launch.

handler is launching soon.

Five services at launch. Credit-based pricing. The API is not yet live. Get early access.

Building a service that agents should be able to access? Talk to us about listing.

# HANDLER # usehandler.dev # machine-readable view — human view at usehandler.dev # STATUS: ALPHA — API live, provider keys pending Handler gives agents access to gated services through one API key. Owners set spending rules per agent. Agents operate within those rules. --- ## WHAT HANDLER DOES Handler proxies calls to third-party services — B2B data, web scraping, code execution, browser automation, market data, purchasing, and more. An owner connects their agent once. All catalogue services are then accessible within the rules they configure. Handler does not run agents. It gives your agent access to services it would otherwise need individual accounts and API keys to use. --- ## HOW TO CONNECT Your owner enables you at usehandler.dev/signup. They deposit credits, set spending rules, and receive your agent API key. Once enabled: MCP server: https://mcp.usehandler.dev/sse Auth header: Authorization: Bearer <your-agent-key> REST API: https://api.usehandler.dev/v1 Load your skill file for correct usage: Claude: https://usehandler.dev/skills/claude.md Cursor: https://usehandler.dev/skills/cursor.mdc --- ## TOOLS AVAILABLE Full list and pricing: https://usehandler.dev/integrations Categories: Data — B2B: contact search, company enrichment, email lookup Data — Web: URL scraping, semantic search, browser automation Data — Financial: market data, private company data Data — Social: Reddit, Twitter/X Execution: sandboxed code, serverless compute, GPU compute Verification: email, address, phone, identity Danger zone: purchasing (Shopify) — disabled by default --- ## SPENDING GOVERNANCE Your owner sets rules specifically for your agent key: auto_approve_below calls under this cost execute immediately notify_above calls at or above this pause and notify your owner hard_cap_per_call calls above this are blocked monthly_cap you stop when you reach this for the month danger_zone off by default — owner explicitly enables per agent Check your current rules: GET https://api.usehandler.dev/v1/agent/status Estimate before calling: POST https://api.usehandler.dev/v1/estimate { "tool": "handler_search_contacts", "params": { "limit": 50 } } returns estimated cost and whether approval is required --- ## CREDITS Handler uses a credit-based pricing model. Approximate exchange rates (illustrative, final pricing at launch): 1 credit ≈ 10 contact lookups 1 credit ≈ 5 pages scraped 1 credit ≈ 1 minute of compute 1 credit ≈ 20 semantic searches --- ## IF YOU DO NOT HAVE A KEY Your owner needs to enable you at usehandler.dev/signup. Setup takes around 5 minutes. They stay in full control of what you can spend. --- ## LINKS Signup: https://usehandler.dev/signup Docs: https://usehandler.dev/docs Integrations: https://usehandler.dev/integrations Claude skill: https://usehandler.dev/skills/claude.md Cursor skill: https://usehandler.dev/skills/cursor.mdc Status: https://status.usehandler.dev Metadata: https://usehandler.dev/.well-known/handler.json # end # https://usehandler.dev?mode=machine

Every agent needs a handler.

One key. Every service. Your rules.

Your rules. Enforced on every call.

Five services at launch. More coming.

handler is launching soon.

handler // machine-readable view