CARTO website screenshot

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.

38.2/100 thin ▬ flat Agent 19/100 agent aware saas Full breakdown ↓
scored 2026-08-30 · rubric v0.17.2
AccessSelf serve
1 APIs 1 MCP Servers
CompanyDeveloper ToolsLocation IntelligenceGeospatialMapsSpatial AnalyticsData WarehouseGISAgents

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-30 · rubric v0.17.2
Composite quality — 38.2/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 14.8 / 20
Access Clarity 9.2 / 20
Operational Transparency 4.4 / 13
Contract Governance 2.2 / 12
Discoverability 7.6 / 10
Agent readiness — 19/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 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 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 6 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 6 / 6
Agentic Commerce Surface 0 / 5
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 1

Individual APIs this provider publishes, each with its own machine-readable definition.

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 1

Model Context Protocol servers that expose these APIs to AI agents.

CARTO MCP Server

MCP SERVER

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Cartodb Authentication

apiKey/oauth2/openIdConnect · 3 schemes

SECURITY

Cartodb Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Cartodb Trust Center

trust center published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Cartodb Scopes

4 scopes · authorizationCode/clientCredentials

4 scopes

SCOPES

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

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
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.23'
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

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/cartodb"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/cartodb/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/cartodb/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.