Agent Onboarding
If you’re developing with AI, GTM Tools offers several resources to improve your experience.
Get an API key
Your agent can sign up programmatically through get_api_key. No console access needed: a 6-digit code is sent to the email you provide, and calling the same endpoint again with the code returns the bearer token.
Autonomous registration via auth.md
GTM Tools implements the auth.md spec so an autonomous agent that hits a 401 can register itself without a human signup form. The 401 carries WWW-Authenticate: Bearer resource_metadata="https://api.gtm-tools.sh/.well-known/oauth-protected-resource"; following that hop leads to the auth.md narrative with copy-paste curl examples.
Two registration shapes are supported:
Revoke at any time:
ID-JAG (urn:ietf:params:oauth:token-type:id-jag) is not yet accepted, since no agent provider mints them in production. We’ll enable it when an issuer ships.
New accounts receive 100 free tokens ($1 = 100 tokens, paid top-ups start at $5). Live token costs per tool are returned by get_token_balance.
GTM Tools MCP Server
MCP (Model Context Protocol) is an open protocol that standardizes how applications provide context to LLMs. The GTM Tools MCP server gives your AI agent tools to find LinkedIn profiles, engage on Reddit, verify professional emails, detect buying signals, and manage your wallet, all through a single Streamable HTTP endpoint.
Setup
Point any MCP-compatible client at the endpoint:
On first connect, the server runs the OAuth flow via /.well-known/oauth-protected-resource and the client opens a browser to authenticate. Clients that prefer static keys can authenticate with Authorization: Bearer <api-key> instead.
The fastest path is the mcp add CLI, which patches Claude Desktop, Cursor, or Windsurf configs in place:
For a manual config, point a gtm-tools MCP entry at the URL above. The full set of supported clients (Claude Desktop, Cursor, Windsurf, Codex, Goose, OpenClaw, Hermes Agent, NanoClaw, Raycast, VS Code, Cline, …) is on the Connect page.
Available MCP tools
Your MCP client discovers tools directly from the hosted runtime, so there is nothing to declare on your side. See the current MCP tool catalog for names and parameter shapes, and Pricing for the token cost of each one.
get_token_balance returns the live per-tool cost table. Agents should call it rather than hardcoding costs.
GTM Tools Docs for Agents
You can give your agent current docs in three ways:
-
Full documentation index
A structured index of every doc page with descriptions:
-
Markdown versions of any page
Every doc page is available as Markdown. Append
.mdto any page URL: -
Section indexes
Append
/llms.txtto any section URL for a scoped index:
Agents that would rather search than read can point an MCP client at the docs server itself, https://gtm-tools.sh/_mcp/server. Or add the index to your system prompt:
GTM Tools Skills
Skills give AI agents specialized knowledge for specific tasks. Install the gtm-tools skill to give your coding assistant the whole tool surface: how to get a key, how to connect a browser session, the full 63-tool catalog with token costs, the metering rules, and the error contract.
Claude Code
Cursor
Codex
Other supported values for --agent: amp, cline, gemini-cli, kimi-code-cli, opencode, windsurf. Use --agent '*' for all of them, --global for a user-level install, and --yes to skip the prompts.
Manual installation
Then set your API key:
Quick start for agents
Get a key, qualify a target with signals, find decision-makers on LinkedIn, and verify their emails, end-to-end:
Browse a target’s recent activity
AI Builder Integrations
GTM Tools plugs into the runtime your agent already uses:
Add GTM Tools to an OpenClaw assistant as an MCP server or a skill.
Declare the MCP server in ~/.hermes/config.yaml and reload.
Load every tool into a LangGraph agent through langchain-mcp-adapters.
An MCP connection with approval gates on the write tools.
What Makes GTM Tools Different?
Unlike traditional GTM platforms, which are seat-licensed UIs that bolt on a partial REST API, GTM Tools is built for autonomous agent use:
Next Steps
Step-by-step setup with environment variables and best practices.
Full interactive API documentation.
Batch-enrich a lead list with LinkedIn URLs and verified emails.
Answers to common questions about auth, tokens, rate limits, and tool behavior.