CARTO for Agents
Hubungkan agen AI ke CARTO, platform GIS Agentic terkemuka: kueri data gudang yang terkelola, jalankan analisis spasial, buat atau edit peta dan alur kerja, serta render peta interaktif, semuanya tanpa data Anda meninggalkan gudang Anda.
Dokumentasi
For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending
.mdto page URLs; this page is available as Markdown.
CARTO for Agents
- Overview
- Connect your platform
- Claude
- Claude Code
- ChatGPT
- Codex
- GitHub Copilot
- Antigravity
- Microsoft Copilot Studio
- Google Gemini Enterprise
- Snowflake CoWork
- Snowflake CoCo
- Databricks Genie Code
- Oracle (OCI Generative AI)
- CARTO MCP Server
- Connecting with OAuth
- Connecting with API Access Tokens
- MCP Tools Reference
- Maps tools
- Workflow tools
- Data tools
- Workspace tools
- CARTO Agent Skills
- Installation
- Skills catalog
- CARTO CLI
- Installation
- Authentication & profiles
- Configuration
- Command reference
- auth
- credentials
- maps
- workflows
- projects
- connections
- named-sources
- do (Data Observatory)
- import
- export
- transfer
- sql
- lds
- org
- users
- activity
- admin
- ai
- app
- Examples
- Release notes
Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the ask and goal query parameters:
GET https://docs.carto.com/carto-for-agents.md?ask=<question>&goal=<user_goal>
ask is the immediate question: it should be specific, self-contained, and written in natural language.
goal is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with ask=how do I create an API token, a goal like automate deployments from our CI pipeline lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.