Cargo
Vendor domain: getcargo.ai · vendor page id getcargo-ai
A live handshake means the URL answered an MCP initialize as a server on the probe date. It is liveness and nothing more: nobody has run its tools. A tool being catalogued means a server names it, by answering tools/list, in its own source, or in the vendor's documentation. None of them has been called. A tool count of 0 means not measured, never zero tools.
Cargo
A GTM/RevOps engineering platform (YC S23) that lets revenue teams define, version, and automate go-to-market logic - lead sourcing, enrichment, scoring, routing, CRM sync - as code, run by AI agents.
1 of 1 free to start, a solo operator gets API access without talking to anyone.
The gate is the api_gate field on each product entry, established by hand on the last_checked date shown above. It records whether a solo operator can get API access without a contract. Money is not tracked.
- Enrich a company from a domain
- Sync records between systems
- Run an automation workflow
- Route an inbound lead
- Score and prioritize leads
5 distinct job labels, the union across 1 product, tagged 2026-08-25. A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.
- https://docs.getcargo.ai/ (Cargo, docs page, probed 2026-09-04)
An endpoint is where an agent connects. A docs page is where a person reads about connecting. Both are published because both are what the probe found; an agent needs the first.
Cargo cargo official CLI
npm install -g @cargo-ai/cliquoted from https://docs.getcargo.ai/cli/overview on 2026-09-27, via npm
Login or key hint: cargo-ai login --token <
1 more install command, 8 subcommands seen, harvested 2026-09-27, all on the tool page.
A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it.
github.com/getcargohq tied to the vendor by rule 2, account name 'Cargo' equals the entry's display name, confidence check
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| gtm-skills | other | Standalone Cargo GTM agent skills - one job each. Find leads, enrich contacts, verify emails, track signals. | 3 | 2026-09-07 | |
| cargo-skills | CLI | GTM engineering skills for AI coding agents - build lead lists, find & verify emails, waterfall enrichment, lead... | 17 | 2026-09-05 | |
| cargo-manifest | other | The software factory for go-to-market. An open-source monorepo holding your company context (ICP, personas, plays,... | 6 | 2026-09-03 | |
| cargo-partner-skills | other | 0 | 2026-08-19 | ||
| dummy-integration | plugin or integration | 2 | 2026-01-13 |
Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.
A job tag is a vendor claim: it means the vendor says the product does this, and it is not a test result. A listed tool has not been run: the catalogue says what an agent could try, not what works. 1 of 1,252 directory entries are bench tested, meaning somebody personally ran the tool on a stated date, and 0 of this vendor's 1 product are among them. There is no verdict here on whether this vendor is better than another.
Vendor pages group the directory's canonical product entries by vendor_domain. The vendor name is the product display name that matches the domain when several products share it; nothing on this page is typed by hand. Data baked 2026-09-27 by build_directory.py (phase 1).