> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://gtm-tools.sh/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://gtm-tools.sh/_mcp/server.

# What is GTM Tools?

> The platform in one page

GTM Tools gives AI agents the building blocks of a modern go-to-market motion: LinkedIn automation, Reddit engagement, buying-intent signals, SMTP-verified email finding, and centralized auth + billing. Instead of stitching together a dozen provider APIs, scraping rules, SMTP libraries, and rate-limit handling, you point your agent at a handful of tool calls.

Everything ships behind one host (`api.gtm-tools.sh`) with one auth boundary and one wallet, reachable over [MCP](/integrations/mcp), plain HTTP, or the [CLI](/integrations/cli).

| Category     | What it does                                                  |
| ------------ | ------------------------------------------------------------- |
| **Billing**  | API keys, credit balance, card top-ups, auto-reload, invoices |
| **LinkedIn** | Search, profiles, companies, posts, jobs, DMs, invitations    |
| **Reddit**   | Read threads, post + comment, vote, DM via Reddit Chat        |
| **Email**    | SMTP-verified professional email finding                      |
| **Signals**  | Buying intent: hiring, Trustpilot, social spikes, tech stack  |

## Key differences

Traditional GTM platforms are seat-licensed UIs with a partial API bolted on. The differences that matter for an agent:

| Feature                 | GTM Tools                           | Traditional GTM platforms     |
| ----------------------- | ----------------------------------- | ----------------------------- |
| Pricing model           | ✅ Per-tool credit metering          | ❌ Per-seat licenses           |
| Getting started         | ✅ 100 free credits, no card         | ⚠️ Gated demo or sales call   |
| Primary surface         | ✅ MCP + HTTP + CLI                  | ❌ UI with a partial API       |
| Agent self-registration | ✅ `auth.md`, no signup form         | ❌ Human signup required       |
| Writes                  | ✅ From your own logged-in account   | ⚠️ Gated partner APIs         |
| Data breadth            | ⚠️ LinkedIn, Reddit, email, signals | ✅ Larger warehoused databases |

That last row is the honest trade: we don't sell a contact database. Every call fetches live.

## When to use GTM Tools

Reach for it when:

* An agent needs to **qualify accounts** on real buying signals before spending effort on them.
* An agent needs a **verified way to reach** a specific person: LinkedIn URL, then an SMTP-checked email.
* An agent should **act as you** on LinkedIn or Reddit, from your own logged-in session.
* You want **usage-based cost** you can reason about per call, rather than a seat you pay for whether the agent runs or not.

Reach for something else when you need a warehoused contact database to filter offline, a CRM of record, or a sending platform with deliverability infrastructure.

## What this is not

* **Not a CRM.** No contact storage, deal pipeline, or activity timeline.
* **Not an outbound automation suite.** `send_linkedin_message` exists, but cadence and sequencing logic is your agent's job.
* **Not an enrichment warehouse like Clay.** Output is per-tool and isn't warehoused for you, beyond the internal caches that keep repeat lookups cheap.
* **Not an email sender.** `get_email` speaks SMTP only as far as `RCPT TO` and never issues `DATA`, so no mail ever leaves. Deliverability, domains, and DNS stay with whatever you send through.

If you need any of those, GTM Tools is the layer underneath: call its tools from your agent, CRM, or outbound platform.

## Can I use this alongside Apollo or ZoomInfo?

Yes, and most teams should. The handoff is deliberately tool-agnostic: the [`outbound-sales` skill](/skills/outbound-sales) returns drafts as structured fields (`email_subject`, `email_body`, `linkedin_dm`, `signals_fired`) that paste into Apollo, Outreach, Salesloft, Lemlist, Smartlead, or your own CRM. Nothing on the sending side needs to know GTM Tools exists.

A common split: your existing platform owns the contact database and the sending infrastructure, GTM Tools owns the **timing** (which accounts are worth touching this week) and the **last mile** (who exactly, and does the address resolve).

## What's open

The [Agent Skills catalog](https://github.com/arnaudjnn/gtm-skills) is public: read it, fork it, or send a PR to improve a skill. The platform behind the tools is closed source. Feature requests and bug reports go to [support](/support).