> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/how-to/user-interface/mapbox-map-layer.md).

# Use Mapbox as a map layer

This small guide will show you how to use Mapbox as Map provider / Map Layer in any Appfarm Solution

### On mapbox.com

1. Visit Mapbox Studio at `https://account.mapbox.com`. Sign up or sign in
2. From the dashboard, click **Design in Mapbox Studio**
3. Click **New Style**
4. Select from a template
5. Click **Customize Basic**
6. Click **Share** in the top-right corner
7. Locate section **Developer resources** and click **Third Party**
8. In the dropdown menu, select **CARTO**
9. Copy or save the integration URL

### In Appfarm Create

1. Add a new [Map UI component](/library/ui-components/map.md), or find your existing Map UI component in your App.
2. Add a new Layer to your Map
3. Select **Layer Type**: **Map**
4. Setting **URL**: Copy the integration URL (copied from Mapbox) and set this as URL of the layer.
5. **Environments Config**: For each environment, do the following
6. Section **Content Security** > **Image Sources**: Add an entry with name `Mapbox` and value `https://api.mapbox.com`


---

# 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.appfarm.io/how-to/user-interface/mapbox-map-layer.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.