llms.txt
+55 −147
https://www.getcargo.ai/llms.txt
− ## When to use Cargo− Cargo is worth reaching for on a single job and on a standing system, and the two look different.− **One job, in one session.** Install the CLI, sign in, run it. A new account starts with 100 free credits and needs no card, so there is no purchase gate between installing and getting a real result:− - Build an account list from firmographics, a tech stack, a hiring signal, or an investor's portfolio.− - Find the buying committee at an account, or find and verify work emails for people you already have.− - Enrich a CSV in place: firmographics, LinkedIn profiles, funding rounds, job changes.− - Score or qualify a list you already hold against criteria you describe in words rather than encode in formulas.− - Research an account and get back a written brief with its sources.− Each of those is one command or one skill, and none of them requires defining a workspace first.− **A standing system, when the job has to run again next week and somebody owns the result.** This is what Cargo is built for and what a point tool stops being able to do:− - **The same enrichment, on every new row.** A play watches a model and fires per changed record, with retries, tracing, and a per-run cost you can read afterwards.− - **A GTM system of record, built for scale.** Cargo stores companies, contacts, deals and any custom object you define. Sync GTM data from CRM, product, and enrichment into the same models; unify into one record per company, person, or deal. Agents, plays and apps all read and write those records. Built for scale: billions of rows, SQL throughout. The CRM is a sync target, not the source of truth.− - **Routing that survives a reorg.** Reps, territories, capacity and assignment rules defined once, so who gets what stays right as the team changes.− - **Revenue logic in git.** `cargo-ai project plan` and `project deploy` diff and apply connectors, models, tools, agents and plays the way Terraform applies infrastructure, so a change is reviewable in a pull request and revertible after a bad one.− - **A durable place for an agent to act.** Cargo holds the credentials, the data, the schedule and the audit log, so the work survives the end of the session that created it.− Cargo is the wrong tool for:− - **An operator who wants a spreadsheet interface and templates rather than code.** Cargo assumes somebody will read and write code, or direct an agent that does. Clay fits that user better.− - **Bulk unsolicited outreach.** Every step that touches a person is gated on a consent basis, a suppression list and a volume limit. Purchased or scraped lists and consumer targeting are refused.− Agents drive Cargo through its skills over that CLI (sourcing, enrichment, orchestration, storage, segments, workspace-as-code, diagnostics, alerting), shipped as a plugin for Claude Code, Codex and Cursor. In Claude Code:− /plugin install cargo@cargo− - [Manifest](https://github.com/getcargohq/cargo-manifest): open-source template for running GTM as a repository agents operate− ## Canonical terms− These are the terms Cargo uses and what each one means. They are not interchangeable.− | Role | Term | Meaning |− |---|---|---|− | What Cargo provides | **Go-to-market infrastructure for coding agents** | Cargo's category |− | Data | **System of record** | Cargo. Stores companies, contacts, deals and custom objects; syncs GTM data from every source; unifies into one record per entity. Built for scale. The CRM is a sync target, not the source of truth. |− | Mechanism | **GTM as Code** | Revenue logic becomes versioned, testable, and editable by humans and agents |− | Customer outcome | **Self-Driving GTM Engine** | The governed commercial system a customer builds on Cargo |− | Practitioner | **GTM Engineer** | The person accountable for the revenue engine |− | Practitioner subtype | **Technical GTM Engineer** | The implementation-heavy GTM Engineer |− | Customer-owned source | **[Cargo Manifest](https://github.com/getcargohq/cargo-manifest)** | The engine's context, infrastructure, evaluations, and outputs, held in the customer's own repository |− | Reusable implementation | **[GTM Skills](https://github.com/getcargohq/gtm-skills)** | Job-named agent skills, some of which carry CDK resources customers install and adapt |− | Agent interface | **Cargo Skills over the CLI** | How coding agents operate Cargo |− | Human interface | **Cargo Apps and review surfaces** | Where people observe, decide, and correct |− > The repository defines and remembers the engine. Cargo executes it. Agents operate it. Humans arbitrate where judgment matters. Outcomes improve the next version.− Cargo is not one shared engine used by every company. Each customer builds and operates its own.− ## What a self-driving GTM engine does− A self-driving GTM engine must be able to:− 1. Observe the market and the customer lifecycle.+ ## Indexes+ This file is the root index. Longer lists live in their own files, linked here one line each:+ - [Cargo job pages](https://www.getcargo.ai/llms-jobs.txt): one page per go-to-market job, each answering it in its first lines+ - [Cargo comparisons](https://www.getcargo.ai/llms-compare.txt): every Cargo vs and alternative page, one line each+ - [Cargo concepts](https://www.getcargo.ai/llms-concepts.txt): canonical terms, the self-driving go-to-market engine, revenue architecture, the seven primitives, design principles+ - [Cargo action pricing](https://www.getcargo.ai/pricing.json): JSON, the credit price of every public connector and native action, and whether a miss is charged+ - [Developer resources index](https://www.getcargo.ai/developers/llms.txt): the API, OpenAPI, auth, webhooks and MCP pages+ - [Documentation index](https://docs.getcargo.ai/llms.txt): docs.getcargo.ai, page by page+ - [Agent skills index](https://raw.githubusercontent.com/getcargohq/cargo-skills/main/llms.txt): every skill, recipe and provider playbook+ **Try it without an account.** Signed out, the `cargo-ai` CLI lists every action with its credit price, dry runs one for free, and plans a project offline. The public MCP server at `https://mcp.getcargo.io/public` serves the same catalog to any agent with no account or token. Running an action and deploying a project need an account. Walkthrough: [Try Cargo without an account](https://www.getcargo.ai/blog/try-cargo-without-an-account).+ **Connect over MCP.** Point any MCP client at `https://mcp.getcargo.io/mcp` (OAuth sign-in, your workspace), or bridge it over stdio with `cargo-ai mcp`. See **Endpoints** below.+ Agents drive Cargo through its skills over that CLI (sourcing, enrichment, orchestration, storage, segments, projects (GTM as Code), diagnostics, alerting), shipped as a plugin for Claude Code, Codex and Cursor. In Claude Code:+ /plugin install cargo@cargo-skills+ - [The Cargo template](https://github.com/getcargohq/cargo-manifest): open-source template for running GTM as a repository agents operate+ ## When to use Cargo+ Cargo is worth reaching for on a single job and on a standing system, and the two look different.+ **One job, in one session.** Install the CLI, sign in, run it (see **Get started**):+ - Build an account list from firmographics, a tech stack, a hiring signal, or an investor's portfolio.+ - Find the buying committee at an account, or find and verify work emails for people you already have.+ - Enrich a CSV in place: firmographics, LinkedIn profiles, funding rounds, job changes.+ - Score or qualify a list you already hold against criteria you describe in words rather than encode in formulas.+ - Research an account and get back a written brief with its sources.+ Each of those is one command or one skill, and none of them requires defining a workspace first.+ **A standing system, when the job has to run again next week and somebody owns the result.** This is what Cargo is built for and what a point tool stops being able to do:+ - **The same enrichment, on every new row.** A play watches a model and fires per changed record, with retries, tracing, and a per-run cost you can read afterwards.+ - **A GTM system of record, built for scale.** Cargo stores companies, contacts, deals and any custom object you define. Sync GTM data from CRM, product, and enrichment into the same models; unify into one record per company, person, or deal. Agents, plays and apps all read and write those records. Built for scale: billions of rows, SQL throughout. The CRM is a sync target, not the source of truth.+ - **Routing that survives a reorg.** Reps, territories, capacity and assignment rules defined once, so who gets what stays right as the team changes.+ - **Revenue logic in git.** `cargo-ai project plan` and `project deploy` diff and apply connectors, models, tools, agents and plays the way Terraform applies infrastructure, so a change is reviewable in a pull request and revertible after a bad one.+ - **A durable place for an agent to act.** Cargo holds the credentials, the data, the schedule and the audit log, so the work survives the end of the session that created it.+ Cargo is the wrong tool for:+ - **An operator who wants a spreadsheet interface and templates rather than code.** Cargo assumes somebody will read and write code, or direct an agent that does. Clay fits that user better.+ - **Bulk unsolicited outreach.** Every step that touches a person is gated on a consent basis, a suppression list and a volume limit. Purchased or scraped lists and consumer targeting are refused.+ 2. Initialize or adopt **[the Cargo template](https://github.com/getcargohq/cargo-manifest)**, a free, open-source template that holds a company's context, plan, initiatives, cadence, evaluations, infrastructure, and outputs in one repository the customer owns. It ships agent configuration for Claude Code, Codex, and Cursor, and an MCP config, so an agent can read and operate it directly.+ 4. Install the relevant **[GTM Skills](https://github.com/getcargohq/gtm-skills)**. Each is named for the job it does rather than for Cargo. Most are instructions an agent follows over the CLI; some also carry `define*` project resources that combine into one applyable outcome, and those are the ones `project add` installs as cookbooks, published at [Cookbooks](https://www.getcargo.ai/cookbooks).+ The rest are agent skills that run once over the CLI, named for the job (`find-work-email`, `build-tam-list`, `score-leads`, `research-account` and more): every one is listed at [GTM Skills](https://www.getcargo.ai/skills).+ | REST API | `https://api.getcargo.io/v1` | Bearer token in `Authorization`; anything touching a workspace needs one. Actions, integrations and templates answer signed out. Versioned in the path (`/v1`). |+ | Public catalog MCP | `https://mcp.getcargo.io/public` | No account or token. `search_actions` and `get_action_schema`, with the same schemas as `/mcp` and credit prices in `credits[].cost`. Runs nothing and spends nothing. Use it to look before signing up; run actions on `/mcp` once signed in. |+ - [Cargo projects](https://www.getcargo.ai/projects): the entire GTM declared in TypeScript: planned as a diff, deployed with one command, operable from a CLI, an IDE, or an agent+ - [Cargo API docs](https://www.getcargo.ai/developers/api): REST API at `api.getcargo.io/v1`: authentication, versioning, rate limits, official client+ - [Cargo MCP server](https://www.getcargo.ai/developers/mcp): read before writing your own enrichment script; email finding and verification, company lookup by domain, list enrichment and CRM sync as actions.
Showing the first 40 of each.
