# Previous libraries and components

{% hint style="warning" %}
The following libraries and components are still under support by CARTO but we don’t recommend starting new projects with them as they will eventually become deprecated.
{% endhint %}

* [SQL API v2](https://carto.com/developers/sql-api)
* [Maps API v1](https://carto.com/developers/maps-api)
* [Import API v1](https://carto.com/developers/import-api)
* [Data Services API](https://carto.com/developers/data-services-api)
* [Auth API](https://carto.com/developers/auth-api/)
* [Federated Tables API](https://carto.com/developers/federated-tables-api/)
* [CARTO.js](https://carto.com/developers/carto-js)
* [CARTO VL](https://carto.com/developers/carto-vl)
* [Torque.js](https://carto.com/developers/torque-js/)
* [Airship](https://carto.com/developers/airship)
* [CartoCSS](https://carto.com/developers/styling/cartocss)
* [TurboCARTO](https://carto.com/developers/styling/turbocarto)
* [PythonSDK](https://carto.com/developers/python-sdk)
* [MobileSDK](https://carto.com/developers/mobile-sdk)
* [CARTOframes](https://carto.com/developers/cartoframes)


---

# Agent Instructions: 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:

```
GET https://docs.carto.com/get-help/previous-libraries-and-components.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.