Carto
CARTO is a cloud-native location intelligence platform that lets developers and analysts build spatial applications directly on top of modern data warehouses (BigQuery, Snowflake, Redshift, Databricks). It exposes a Maps API for vector and tileset map data, an SQL API for spatial analytics, a Workflows API for executing no-code spatial pipelines, an Import API for data ingestion, and the Data Observatory for curated third-party spatial datasets — all backed by OAuth access tokens and API access tokens.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Carto the way a machine reads it — 46 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Carto scores 44.3/100 (developing), with a separate agent-readiness read of 27/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Carto's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/carto/"
title="Carto on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/carto.svg"
alt="Carto Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/carto/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/carto/"
title="Carto on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/carto/card.svg"
alt="Carto Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Carto
Each block below is one kind of artifact we hold for Carto. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 10
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
CARTO Maps API
Serves vector tables, SQL-query-backed tilesets, tileset sources, and raster/H3/quadbin tilesets for visualization in deck.gl, MapLibre, Google Maps, Amazon Location, or Mapbox ...
CARTO SQL API
Executes SQL (including CARTO's spatial functions and analytics extensions) against a connected data warehouse from applications, returning GeoJSON / JSON results for spatial an...
CARTO Workflows API
Executes visually-designed CARTO Workflows (spatial data pipelines) programmatically, enabling scheduled, CI-driven, or application- triggered spatial analytics runs.
CARTO Import API
Ingests files and URLs (CSV, GeoJSON, Shapefile, etc.) into a user's connected CARTO data warehouse for downstream spatial analysis and mapping.
CARTO Data Observatory
Curated catalog of third-party spatial datasets (demographics, POIs, mobility, financial, environmental) accessible via subscription and queryable directly from the customer's c...
CARTO Accounts API
Manages CARTO user accounts, organizations, and API access tokens, including OAuth clients used for secure programmatic access.
CARTO for deck.gl
Client library providing deck.gl layers for CARTO vector, H3, quadbin, raster, and query sources, simplifying application-layer integration with the Maps API.
CARTO for React
React library of components and hooks for building CARTO-powered location intelligence applications with widgets, filters, and deck.gl map integration.
Carto Jobs API
The Jobs API from Carto — 2 operation(s) for jobs.
Carto SQL API
The SQL API from Carto — 1 operation(s) for sql.
Scroll within the panel for all 10 ·
Open Collections 4
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONCARTO Platform Jobs API
OPEN COLLECTIONCARTO Platform Jobs SQL API
OPEN COLLECTIONCARTO Platform API
OPEN COLLECTIONMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
MCP Server
MCP SERVERAgent Skills 23
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
carto-arcgis-migration
AGENT SKILLcarto-basics
AGENT SKILLcarto-composite-scoring
AGENT SKILLcarto-connect-datawarehouse
AGENT SKILLcarto-create-builder-maps
AGENT SKILLcarto-create-workflow
AGENT SKILLcarto-develop-app
AGENT SKILLcarto-explore-datawarehouse
AGENT SKILLcarto-find-spatial-data
AGENT SKILLcarto-geocoding
AGENT SKILLcarto-gwr
AGENT SKILLcarto-hotspot-analysis
AGENT SKILLcarto-import-export-data
AGENT SKILLcarto-manage-platform
AGENT SKILLcarto-preview-builder-map
AGENT SKILLcarto-query-datawarehouse
AGENT SKILLcarto-render-inline-map
AGENT SKILLcarto-routing-od-analysis
AGENT SKILLcarto-site-selection
AGENT SKILLcarto-spatial-autocorrelation
AGENT SKILLcarto-spatial-enrichment
AGENT SKILLcarto-territory-planning
AGENT SKILLcarto-trade-area-analysis
AGENT SKILLScroll within the panel for all 23 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
CARTO GraphQL Schema
This conceptual GraphQL schema models the CARTO location intelligence and spatial analytics platform. CARTO exposes REST APIs for Maps, SQL analytics, Workflows, Data Import, Da...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Carto Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Carto Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Carto Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Carto Context
JSON-LDSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Carto — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/carto · machine-readable index on apis.io
This is an independent, third-party profile of Carto, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.