> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-for-developers/reference.md).

# Reference

- [Data Sources](https://docs.carto.com/carto-for-developers/reference/data-sources.md)
- [vectorTableSource](https://docs.carto.com/carto-for-developers/reference/data-sources/vectortablesource.md)
- [vectorQuerySource](https://docs.carto.com/carto-for-developers/reference/data-sources/vectorquerysource.md)
- [vectorTilesetSource](https://docs.carto.com/carto-for-developers/reference/data-sources/vectortilesetsource.md)
- [h3TableSource](https://docs.carto.com/carto-for-developers/reference/data-sources/h3tablesource.md)
- [h3QuerySource](https://docs.carto.com/carto-for-developers/reference/data-sources/h3querysource.md)
- [h3TilesetSource](https://docs.carto.com/carto-for-developers/reference/data-sources/h3tilesetsource.md)
- [quadbinTableSource](https://docs.carto.com/carto-for-developers/reference/data-sources/quadbintablesource.md)
- [quadbinQuerySource](https://docs.carto.com/carto-for-developers/reference/data-sources/quadbinquerysource.md)
- [quadbinTilesetSource](https://docs.carto.com/carto-for-developers/reference/data-sources/quadbintilesetsource.md)
- [rasterSource](https://docs.carto.com/carto-for-developers/reference/data-sources/rastersource.md)
- [boundaryTableSource](https://docs.carto.com/carto-for-developers/reference/data-sources/boundarytablesource.md)
- [boundaryQuerySource](https://docs.carto.com/carto-for-developers/reference/data-sources/boundaryquerysource.md)
- [Widgets](https://docs.carto.com/carto-for-developers/reference/carto-widgets-reference.md)
- [Data Sources](https://docs.carto.com/carto-for-developers/reference/carto-widgets-reference/data-sources.md)
- [Server-side vs. client-side](https://docs.carto.com/carto-for-developers/reference/carto-widgets-reference/server-side-vs.-client-side.md)
- [Models](https://docs.carto.com/carto-for-developers/reference/carto-widgets-reference/models.md)
- [getFormula](https://docs.carto.com/carto-for-developers/reference/carto-widgets-reference/models/getformula.md)
- [getCategories](https://docs.carto.com/carto-for-developers/reference/carto-widgets-reference/models/getcategories.md)
- [getHistogram](https://docs.carto.com/carto-for-developers/reference/carto-widgets-reference/models/gethistogram.md)
- [getRange](https://docs.carto.com/carto-for-developers/reference/carto-widgets-reference/models/getrange.md)
- [getScatter](https://docs.carto.com/carto-for-developers/reference/carto-widgets-reference/models/getscatter.md)
- [getTimeSeries](https://docs.carto.com/carto-for-developers/reference/carto-widgets-reference/models/gettimeseries.md)
- [getTable](https://docs.carto.com/carto-for-developers/reference/carto-widgets-reference/models/gettable.md)
- [Filters](https://docs.carto.com/carto-for-developers/reference/filters.md)
- [Column filters](https://docs.carto.com/carto-for-developers/reference/filters/column-filters.md)
- [Spatial filters](https://docs.carto.com/carto-for-developers/reference/filters/spatial-filters.md)
- [fetchMap](https://docs.carto.com/carto-for-developers/reference/fetchmap.md)
- [@carto/agentic-deckgl](https://docs.carto.com/carto-for-developers/reference/agentic-deckgl.md)
- [CARTO API Reference](https://docs.carto.com/carto-for-developers/reference/carto-api.md): Reference for the CARTO API
- [Maps API](https://docs.carto.com/carto-for-developers/reference/carto-api/maps-api.md): Create map layers from queries, tables and tilesets.
- [SQL API](https://docs.carto.com/carto-for-developers/reference/carto-api/sql-api.md): Run SQL queries in your data warehouse.
- [Tokens API](https://docs.carto.com/carto-for-developers/reference/carto-api/tokens-api.md): Create and manage API Access Tokens.
- [Imports API](https://docs.carto.com/carto-for-developers/reference/carto-api/imports-api.md): Import geospatial files into your data warehouse.
- [Exports API](https://docs.carto.com/carto-for-developers/reference/carto-api/exports-api.md): Export tables and query results to a file.
- [Location Data Services API](https://docs.carto.com/carto-for-developers/reference/carto-api/lds-api.md): Geocoding, isolines and routing.
- [Named Sources API](https://docs.carto.com/carto-for-developers/reference/carto-api/named-sources-api.md): Server-side aliases for SQL queries.
- [Resources API](https://docs.carto.com/carto-for-developers/reference/carto-api/resources-api.md): Manage maps, workflows and connections.
- [Connections](https://docs.carto.com/carto-for-developers/reference/carto-api/resources-api/connections.md): Manage connections to your data warehouses.
- [Maps and workflows](https://docs.carto.com/carto-for-developers/reference/carto-api/resources-api/maps-and-workflows.md): List and delete the maps and workflows you can access.
- [Organization resources](https://docs.carto.com/carto-for-developers/reference/carto-api/resources-api/organization-resources.md): Administer every resource in the organization.
- [Activity Data API](https://docs.carto.com/carto-for-developers/reference/carto-api/activity-data-api.md): Export activity and API usage data.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.carto.com/carto-for-developers/reference.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.