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

# Developers

Build on LumiDB with the HTTP API, 3D Tiles streaming and MCP.

Use LumiDB from your own code. Query datasets through the HTTP API, stream them as 3D Tiles into your own viewers, or connect AI assistants over MCP.

* [Quickstart: your first API request](https://docs.lumidb.com/api-reference/quickstart-your-first-api-request.md): create an API key, list your datasets and search an area.
* [Import data with the API](https://docs.lumidb.com/import-data/import-data-with-the-api.md): upload a file and import it from your own code.
* [API keys](https://docs.lumidb.com/archive-management/api-keys.md): create a key and send it with your requests.
* [Cesium 3D Tileset export](https://docs.lumidb.com/integrations/cesium-3d-tileset-export.md): stream a dataset as 3D Tiles.
* [Connecting AI assistants (MCP)](https://docs.lumidb.com/integrations/connecting-ai-assistants-mcp.md): let an AI assistant search and describe your datasets.
* [Interactive reference](https://api.lumidb.com/api): try the endpoints in your browser.

The API reference below lists the endpoints by resource.


---

# 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.lumidb.com/api-reference.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.
