Command reference
Every CARTO CLI command, organized by command group. The CLI uses a hierarchical structure:
carto [global-options] <command> <subcommand> [args...]For global options (--json, --debug, --profile, …) and environment variables, see Configuration.
Personal authentication: log in, log out, switch profiles, check status.
Manage application credentials (API tokens, SPA OAuth clients, M2M OAuth clients).
Manage Builder maps: create, update, validate, publish, schema, agents, copy, screenshot (experimental).
Manage Workflows: create, update, validate, verify, run, share, publish, schedule, mcp enable.
Manage projects (folders) that group maps and workflows, with local-sync workflow.
Manage data warehouse connections.
Manage Named Sources — server-side aliases for SQL queries.
Data Observatory: browse, search, sample, subscribe to spatial datasets.
Import geospatial files (CSV, GeoJSON, GeoPackage, Shapefile, …) from local files or URLs.
Export warehouse tables to file (GeoParquet, GeoJSON, Shapefile, CSV, …) or cloud storage.
Run SQL queries (returns results) and SQL jobs (DDL/DML) on your data warehouse.
Location Data Services: geocoding, reverse geocoding, isolines, routing, OD matrices.
View organization statistics, resources, and quotas.
Manage organization users and pending invitations.
Query and export activity logs and usage data (Enterprise Large+).
Superadmin operations (list-all, batch-delete, transfer) and Admin operations (settings, basemaps).
Chat with the AI agents configured on your maps.
Access CARTO's LLM proxy with an OpenAI-compatible API.
Hosted apps: deploy a frontend bundle behind your organization login, or package a public build you host yourself.
Last updated
Was this helpful?
