
Atlaspi
io.github.Soil911Published by GitHub account Soil911v0.10.2Updated Oct 24, 2026
Historical geography for AI agents: polities, GeoJSON borders, chains & events, 4500 BCE-today
Overview
AtlasPI gives an assistant structured historical geography data: polities, GeoJSON borders, events and sources from 4500 BCE to today.
- What you can do
- Search and browse historical entities by name, type, year, status or continent, with full detail records
- Retrieve world snapshots for a given year, nearby entities by coordinates, and contemporaries or related entities
- Compare two to four entities and trace an entity's chronological evolution, chains and events
- Aggregate statistics by century, type, continent or status, and export data as GeoJSON, CSV or timeline
- When to use it
- Useful when answering questions about historical territories, borders, dynasties or events, or when building maps and timelines that need structured, cited historical geography rather than free-text sources.
- Requirements
- Runs as a local Python package (atlaspi-mcp) over stdio; the ATLASPI_API_URL environment variable can point it at a different API base URL, defaulting to the public AtlasPI service. No API key or registration is described.
Installation
In SourceWeft
- Open Atlaspi in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
🌍 AtlasPI
The structured historical geographic database built for AI agents.
Query any empire, kingdom, or territory from 4500 BCE to 2024 — with coordinates,
boundaries, confidence scores, and 2,000+ academic sources.
[Try it live] [Version] [Entities] [Events] [Periods] [Cities] [Routes] [Chains] [Sites] [Rulers] [Tests] [License] [API] [MCP] [DOI]
✅ Free · No API key · No registration · Apache 2.0 · CORS-enabled
curl https://atlaspi.it/v1/snapshot/year/1250
Live: atlaspi.it · API Docs · Map App · MCP Server
Why AtlasPI exists
AI agents working with historical geography today face a fragmented landscape: raw shapefiles in Natural Earth, unstructured text in Wikipedia, scattered coordinates in Wikidata, and academic datasets locked behind incompatible formats. None of these were designed for machine consumption.
AtlasPI bridges this gap. It provides a single, structured REST API where an AI agent can ask "What territories existed in the Balkans in 1400?" or "Show me the boundary changes of the Ottoman Empire" and get back clean JSON with GeoJSON boundaries, confidence scores, academic citations, and honest metadata about what is certain and what is disputed.
Historical data is never neutral. Borders were drawn through conquest, names were imposed through colonization, populations were erased through genocide. AtlasPI does not sanitize this complexity -- it structures it, documents it, and makes it queryable.
Screenshot
The web UI supports keyboard shortcuts, deep linking (/app?year=1000), continent filtering, time playback animation, dark/light mode, and full i18n (English/Italian). Try it live at atlaspi.it.
Quick Start
The API is now live at http://localhost:10100 and the interactive docs at http://localhost:10100/docs.
Docker
API Documentation
AtlasPI exposes 23 REST endpoints under /v1/. Full interactive documentation is available at /docs (Swagger UI) and /redoc when the server is running.
Core Endpoints
Examples
Search for empires active in 1500 CE:
Get full details for entity #12:
Find entities contemporary to the Roman Empire:
Export all entities as GeoJSON:
Find entities near Rome active in 100 CE:
Snapshot of the world in 1500 CE:
Compare two entities side by side:
Response Example
Dataset Overview
How this data is curated — disclosure and correction (2026-07-23)
Curation of non-boundary records (entities, events, cities, rulers, routes, sites) is AI-assisted: LLM research agents propose metadata and candidate citations, an adversarial verification step rejects citations that do not exist or do not support the claim, and the maintainer supervises the pipeline. Records are not systematically reviewed by professional historians. Until the human citation audit (protocol) is published, treat citations as machine-verified, not human-audited. Earlier versions of this documentation said the dataset was "hand-curated" — that wording was inaccurate and has been retired. Full details: METHODOLOGY §2.4 · ETHICS-028 (EN).
1,006 historical entities + 643 historical events spanning 6,500 years of human civilization, backed by 5,000+ academic sources and documenting 2,000+ territory changes. Plus 1,249 archaeological sites, 105 historical rulers, 29 historical languages, 104 dynasty chains, 41 trade routes, 252 historical cities, and 55 historical periods. Events include battles, treaties, epidemics, genocides, colonial violence, massacres, deportations and natural disasters — with ETHICS-007 (no euphemisms) and ETHICS-008 (known_silence flag for erased/suppressed records).
Coverage by Region
Entity Types
15 categories: empire | kingdom | republic | confederation | city-state | dynasty | colony | disputed_territory | sultanate | khanate | principality | duchy | caliphate | federation | city
Time Coverage
- Earliest entity: 4500 BCE (ancient Mesopotamian civilizations)
- Latest entity: 2024 (modern states and disputed territories)
- Negative years represent BCE dates (e.g.,
-753= 753 BCE)
📖 Citation
If you use AtlasPI in research, teaching, or derivative datasets, please cite the project using the Zenodo concept DOI below. The concept DOI always resolves to the latest release — individual versions get their own per-release DOIs on top.
BibTeX
Plain-text citation
AtlasPI Project (2026). AtlasPI: A structured historical geographic database for AI agents, version 6.14.0. Zenodo. https://doi.org/10.5281/zenodo.19581784
Ethical Framework
Historical data carries the weight of conquest, displacement, and erasure. AtlasPI is built on four principles that govern every data decision:
1. Truth Before Comfort
Historical records include conquest, genocide, forced deportation, and cultural erasure. These facts are represented with precision, never sanitized. If a territory was seized by force, the acquisition_method field says so. If a population was decimated, the data shows it with sources. If a geographic name was imposed by erasing the original, both names are present.
2. No Single Version of History
Contested borders show all known versions, with dates and sources. Place names include the original local form alongside names in other relevant languages. Academic disputes are made explicit, not resolved by fiat. The database does not arbitrate history -- it documents it.
3. Transparency of Uncertainty
Every record carries a confidence_score from 0.0 to 1.0. Every data point includes sources[] with primary source citations. Records scoring below 0.5 are marked as status: "uncertain" (enforced at the data layer — see ETHICS-013; the distinct status: "disputed" is reserved for contested territories, ETHICS-003). An uncertain datum honestly labeled is more valuable than a fabricated certainty.
4. No Geographic or Cultural Bias
Place names use the local-language form as the primary name. Sources include non-Western historiography where available. Colonial conquests are documented from the perspective of the colonized, not only the colonizers.
These principles are enforced through automated ethical tests, documented decisions in
docs/ethics/, and# ETHICS:comments throughout the codebase. See CLAUDE.md for the full governance framework.
Architecture
Tech Stack
Project Structure
Key Design Decisions
- Dual database support: SQLite for zero-config local development, PostgreSQL + PostGIS for production spatial queries.
- Auto-seeding: The database populates itself on first launch from JSON entity files -- no manual migration needed.
- GZip compression, CORS, rate limiting (60 req/min), and security headers enabled by default.
- Structured logging: JSON format in production, human-readable in development.
Testing
The test suite covers five dimensions:
Contributing
Contributions are welcome. Before you start:
- Read CLAUDE.md -- it contains the project's core values and development conventions.
- Check
docs/ethics/-- understand the ethical decisions already made. - Check
docs/adr/-- understand the architectural decisions already made.
Guidelines
- Code is written in English; documentation in Italian (except this README).
- Every function touching sensitive historical data must include an
# ETHICS:comment explaining the design choice. - Tests must cover ethical edge cases, not only technical ones.
- New entity data must include
sources[]with verifiable academic citations. - Disputed territories must have
confidence_score <= 0.7andstatus: "disputed".
Adding Historical Entities
Entity data lives in data/entities/ as JSON files. Each entity requires:
- Primary name in the original/local language
- At least one academic source
- A confidence score reflecting source reliability
- Territory changes with dated boundaries where available
Development Setup
Roadmap
See ROADMAP.md for the full development plan. Key upcoming milestones:
- PostgreSQL + PostGIS spatial queries in production
- Full GeoJSON boundary coverage for all entities
- Wikidata/OpenStreetMap ingestion pipelines
- Premium API tier with higher rate limits
- Hosted instance with public access
How to Cite
If you use AtlasPI in academic work, teaching, or derivative datasets, please cite it. A machine-readable CITATION.cff is provided in the repository root and is recognized by GitHub, Zenodo, Zotero, and most reference managers.
Suggested citation (software)
Ramadani, C. (2026). AtlasPI: A structured historical geographic database for AI agents (Version 6.1.2) [Software]. CRA. https://doi.org/10.5281/zenodo.19581784
BibTeX
Citing the underlying boundary sources
AtlasPI derives its geographic boundaries from two upstream datasets. If your work depends on spatial precision, please also cite them directly:
- Natural Earth (public domain) — post-1800 modern administrative boundaries. https://www.naturalearthdata.com/
- aourednik/historical-basemaps (CC BY 4.0) — pre-1800 historical world timestamps. Ourednik, A. historical-basemaps. https://github.com/aourednik/historical-basemaps
For full methodology on how boundaries are assigned, matched, and confidence-scored, see docs/METHODOLOGY.md.
The dataset has a permanent DOI minted by Zenodo: 10.5281/zenodo.19581784 (concept DOI, always resolves to the latest version). Every tagged release mints a new version DOI; see the Zenodo record for v6.1.2 specifically. Deposition metadata is in .zenodo.json.
License
AtlasPI follows an open core model.
The core project -- API, data models, ethical framework, and documentation -- is released under the Apache License 2.0.
Imported datasets retain their original licenses. Every source is tracked and attributed. Premium components (hosted services, curated datasets, enterprise features) are maintained separately from the open source core.
See LICENSE for the full Apache License 2.0 text and NOTICE for third-party attributions.
Acknowledgments
AtlasPI builds on the work of:
- Natural Earth -- public domain vector map data for modern boundaries
- aourednik/historical-basemaps -- historical world boundary data
- OpenStreetMap -- geographic data under ODbL
- Wikidata -- structured knowledge base under CC0
And the countless historians, cartographers, and researchers whose work makes structured historical geography possible.
Built with the conviction that historical truth, including its uncomfortable parts, should be structured, accessible, and machine-readable.
Source: README.md at commit b5a6107
Tools
0Version history
1- v0.10.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts