CARTO

CARTO (formerly CartoDB) is a cloud-native location intelligence and spatial analytics platform that runs directly on top of modern cloud data warehouses including Google BigQuery, Snowflake, Amazon Redshift, Databricks, PostgreSQL and Oracle. Developers use the CARTO Cloud-Native (v3) APIs — SQL API, Maps API, Import/Export API, Location Data Services (geocoding, routing, isolines) and the Data Observatory — together with the deck.gl visualization stack, the CARTO for React library, and Python packages to build interactive geospatial applications and analytical workflows. CARTO is notably agent-native: it ships a hosted MCP Server, a first-party `carto` CLI, and a public catalog of 23 Agent Skills for spatial analysis. Authentication is via permanent API Access Tokens or Auth0-backed OAuth (SPA authorization-code and machine-to-machine client-credentials) scoped to the `carto-cloud-native-api` audience.

CARTO publishes 1 API on the APIs.io network. Tagged areas include Company, Developer Tools, Location Intelligence, Geospatial, and Maps.

CARTO’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, changelog, pricing, and 21 more developer resources.

🌐 Visit website 📡 Source on GitHub
40.6/100 thin Agent 30/100 agent aware Full breakdown ↓
scored 2026-07-20 · rubric v0.4
1 APIs 1 MCP Servers 0 Features
CompanyDeveloper ToolsLocation IntelligenceGeospatialMapsSpatial AnalyticsData WarehouseGISAgents

API Rating

API Evangelist API Evangelist Rating How this is scored →
scored 2026-07-20 · rubric v0.4
Composite quality — 40.6/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 16.1 / 20
Commercial Clarity 10.5 / 20
Operational Transparency 4.8 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 30/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/cartodb: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs

CARTO Cloud-Native API

The CARTO Cloud-Native (v3) REST API surface — SQL API (query and async SQL jobs against a connected data warehouse), Maps API (vector/tile map instantiation), Import/Export API...

MCP Servers

cartodb-mcp.yml

MCP SERVER

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 GettingStarted
GettingStarted
 SignUp
SignUp
 Login
Login

Documentation 2

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt
 WellKnown
WellKnown
 MCPServer
MCPServer
 AgentSkill
AgentSkill

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 Conformance
Conformance
 Lifecycle
Lifecycle

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 Packages
Packages
 SDKs
SDKs
 CLI
CLI

Access & Security 4

Authentication, authorization, and security posture

Authentication
Authentication
 OAuthScopes
OAuthScopes
 TrustCenter
TrustCenter
 DomainSecurity
DomainSecurity

Operate 3

Status, limits, changes, and where to get help

Support
Support
 ChangeLog
ChangeLog
 StatusPage
StatusPage

Commercial 3

Pricing, plans, and the legal terms of use

Pricing
Pricing
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy

Company 1

The organization behind the API

Blog
Blog

Source (apis.yml)

apis.yml Raw ↑ 
aid: cartodb
name: CARTO
description: 'CARTO (formerly CartoDB) is a cloud-native location intelligence and spatial analytics platform that runs directly
  on top of modern cloud data warehouses including Google BigQuery, Snowflake, Amazon Redshift, Databricks, PostgreSQL and
  Oracle. Developers use the CARTO Cloud-Native (v3) APIs — SQL API, Maps API, Import/Export API, Location Data Services (geocoding,
  routing, isolines) and the Data Observatory — together with the deck.gl visualization stack, the CARTO for React library,
  and Python packages to build interactive geospatial applications and analytical workflows. CARTO is notably agent-native:
  it ships a hosted MCP Server, a first-party `carto` CLI, and a public catalog of 23 Agent Skills for spatial analysis. Authentication
  is via permanent API Access Tokens or Auth0-backed OAuth (SPA authorization-code and machine-to-machine client-credentials)
  scoped to the `carto-cloud-native-api` audience.'
url: https://raw.githubusercontent.com/api-evangelist/cartodb/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- earlybird
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-18'
image: https://carto.com/favicon.ico
tags:
- Company
- Developer Tools
- Location Intelligence
- Geospatial
- Maps
- Spatial Analytics
- Data Warehouse
- GIS
- Agents
apis:
- name: CARTO Cloud-Native API
  description: The CARTO Cloud-Native (v3) REST API surface — SQL API (query and async SQL jobs against a connected data warehouse),
    Maps API (vector/tile map instantiation), Import/Export API, Location Data Services (geocoding, routing, isolines), Data
    Observatory, and the Workflow API. Regional base host; US Cloud shown. Authenticated with API Access Tokens or OAuth bearer
    tokens.
  humanURL: https://docs.carto.com/carto-for-developers
  baseURL: https://gcp-us-east1.api.carto.com
  tags:
  - SQL API
  - Maps API
  - Geospatial
  - Location Data Services
  properties:
  - type: Documentation
    url: https://docs.carto.com/carto-for-developers
  - type: APIReference
    url: https://docs.carto.com/carto-for-developers/reference
  - type: Authentication
    url: authentication/cartodb-authentication.yml
  - type: OAuthScopes
    url: scopes/cartodb-scopes.yml
  - type: Conventions
    url: conventions/cartodb-conventions.yml
  - type: Lifecycle
    url: lifecycle/cartodb-lifecycle.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DeveloperPortal
  url: https://docs.carto.com/carto-for-developers
- type: Documentation
  url: https://docs.carto.com/
- type: APIReference
  url: https://docs.carto.com/carto-for-developers/reference
- type: GettingStarted
  url: https://docs.carto.com/carto-for-developers/overview
- type: Support
  url: https://docs.carto.com/carto-user-manual/carto-support
- type: Blog
  url: https://carto.com/blog
- type: GitHubOrganization
  url: https://github.com/CartoDB
- type: ChangeLog
  url: https://docs.carto.com/whats-new
- type: LLMsTxt
  url: llms/cartodb-llms.txt
- type: Pricing
  url: https://carto.com/pricing/
- type: SignUp
  url: https://app.carto.com/signup
- type: Login
  url: https://app.carto.com
- type: TermsOfService
  url: https://carto.com/legal/tcs/
- type: PrivacyPolicy
  url: https://carto.com/privacy/
- type: Authentication
  url: authentication/cartodb-authentication.yml
- type: OAuthScopes
  url: scopes/cartodb-scopes.yml
- type: WellKnown
  url: well-known/cartodb-well-known.yml
- type: MCPServer
  url: mcp/cartodb-mcp.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Packages
  url: packages/cartodb-packages.yml
- type: SDKs
  url: packages/cartodb-packages.yml
- type: CLI
  url: cli/cartodb-cli.yml
- type: Conventions
  url: conventions/cartodb-conventions.yml
- type: Conformance
  url: conformance/cartodb-conformance.yml
- type: Lifecycle
  url: lifecycle/cartodb-lifecycle.yml
- type: StatusPage
  url: https://status.carto.com
- type: TrustCenter
  url: security/cartodb-trust-center.yml
- type: DomainSecurity
  url: security/cartodb-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence