# Mundi
> Mundi is an open source, AI-native web GIS for creating maps, analyzing geospatial data, and connecting to databases like PostGIS.
- Mundi open source is AGPLv3 and self-hostable. Mundi cloud is a hosted service and is also available for on-premise deployments using Kubernetes.
- Supports data sources like PostGIS, OGR-compatible vector files and GDAL-compatible rasters.
- Mundi was created by Bunting Labs, Inc. (https://buntinglabs.com)
You can try Mundi free at https://app.mundi.ai or self-host using Docker Compose.
## Documentation Sets
- [Abridged documentation](https://docs.mundi.ai/llms-small.txt): a compact version of the documentation for Mundi, with non-essential content removed
- [Complete documentation](https://docs.mundi.ai/llms-full.txt): the full documentation for Mundi
## Notes
- The complete documentation includes all content from the official documentation
- The content is automatically generated from the same source as the official documentation
## Optional
- [GitHub Repository](https://github.com/BuntingLabs/mundi.ai): Source code and contributions
- [Mundi Cloud](https://app.mundi.ai): Hosted cloud service
- [Landing Page](https://mundi.ai): Mundi landing page with pricing links, features, and more information
Measured from the saved file
Linked document
UTF-8 text size
1.2 KB1270 bytes
Token count
287o200k_base encoding
Markdown links
55 distinct URLs
Fenced code blocks
026 lines in the file
Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.
Project H1
Mundi
Opening blockquote
Mundi is an open source, AI-native web GIS for creating maps, analyzing geospatial data, and connecting to databases like PostGIS.
Context architecture
How the content is divided
3 H2 sections organize 5 parsed Markdown links. 0 links point to .md or .markdown paths; 3 link occurrences use another hostname. Linked destinations have not been recursively validated.
H2 section
Links
UTF-8 bytes
Tokens
Documentation SetsLine 12
2
251
60
NotesLine 17
0
176
28
OptionalLine 22 · Optional
3
261
65
Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.
Embedded material
Code, installation and API examples
Fenced blocks
0 closed
Declared languages
No fenced blocks detected
Package-install commands
0 detected in fenced or inline code
Authentication examples
0 fenced lines match API-key, Authorization, Bearer, OAuth or access-token patterns
HTTP request examples
0 fenced lines match request-method patterns
Authentication links
0 links have authentication-related labels
Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.
Publisher prioritization
The Optional section
1 H2 section named “Optional” contain 3 parsed links. 2 links sit outside those sections. That puts 60.0% of the file’s parsed links under Optional.
The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.
Machine-readable routes
MCP references and configuration text
No MCP or Model Context Protocol term was detected in the captured file. 0 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.
These are text and link observations. No MCP server connection, authentication or tool call was tested.
A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.
Change evidence
What can be said about freshness
This capture establishes a baseline. Update frequency cannot be determined from one observation.
File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.
Counts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.