One API Key for All AI Agent Tools
Managing separate API keys, billing cards, and OAuth flows for LLMs, search, scraping, speech, finance, and code execution slows down every agent build. With Helve, one sk_live_ key unlocks 313+ live tools across 255 providers.
The 3-Step Agent Loop: Search, Call, Request
1. Discover dynamically (search_tools): Your agent sends a natural-language intent like "extract markdown from url" or "sec 10-k filings" to POST /v1/tools/search (or MCP search_tools) and receives matching tool IDs + JSON schemas.
2. Execute with one key (call_tool): Your agent invokes POST /v1/tools/call (or MCP call_tool) using the same Authorization: Bearer sk_live_... header. Public tools cost $0; metered tools debit exact upstream cost + 15% only on success.
3. Log missing tools (request_tool): If no tool matches, search_tools returns a missing_tool_hint so the agent can call POST /v1/tools/request automatically.
Example: Search & Call with One Key
curl -sS -X POST https://helve.dev/v1/tools/call -H "Authorization: Bearer $HELVE_API_KEY" -H "Content-Type: application/json" -d '{"tool_id":"exa.search","arguments":{"query":"MCP tool gateway","num_results":5}}'
Every key supports a hard spend_limit_usd cap so you can safely issue scoped keys per agent, workflow, or environment.
Get Your Free $0.50 Key Spend Limits Guide
FAQ
Yes. A single Helve sk_live_ key authenticates both REST (https://helve.dev/v1) and MCP (https://helve.dev/mcp) across 313+ live tools and 255 providers—including OpenRouter, Cohere, Perplexity, Exa, Tavily, Firecrawl, Brave, ElevenLabs, Deepgram, SEC EDGAR, and Judge0—with zero third-party signups.
Set a deterministic spend_limit_usd on each API key via the dashboard or PATCH /dashboard-api/keys/:id. Helve checks the cap synchronously before calling any upstream provider and returns 402 spend_limit_exceeded at the exact limit.