Skip to main content
Can you try Cargo without an account? Partly. The CLI lists every action (cargo-ai orchestration action list), previews one with cargo-ai orchestration action execute --dry-run (a free sample result, nothing runs), and plans a project (cargo-ai project plan, cargo-ai project types) with no credential. Running anything needs one, and there is no demo key. Getting one takes a single command, no browser and no card: a new account starts with 100 free credits.
--email mails a one-time code and creates the account and a workspace on first use. In an agent or sandbox shell the first call sends the code and exits; re-run it with --code <code> once the user reads it to you. There is one credential. The CLI holds it, and everything reads it: the REST API, your project, the skills, and the MCP bridge. Sign in once and nothing else needs configuring.
Cargo here is the go-to-market platform at getcargo.ai, not Rust’s package manager. Its binary is cargo-ai, installed from npm (@cargo-ai/cli), and it needs no cargo, rustc or Cargo.toml.

Methods

If sign-in does not finish

auth.getcargo.io serves only the OAuth endpoints below and has no pages to visit. The human walkthrough for Claude Code is www.getcargo.ai/with/claude-code.

Calling the API

See API Reference for the rest of the surface.

OAuth

Authorization-server metadata (RFC 8414): https://auth.getcargo.io/.well-known/oauth-authorization-server. Device code, authorization code with PKCE (S256), registration, and revocation. The product MCP server at https://mcp.getcargo.io challenges with OAuth. See MCP servers.

Machine-readable walkthrough

The WorkOS auth.md walkthrough — Discover, Pick a method, Register, Claim, Use, Revocation — is https://www.getcargo.ai/auth.md.