Archiving the physical world so AI can speak to maps.

The world's physical data, structured for agents.
Point of Interest Data
Footfall Data
Road Traffic Data
Parcel Ownership Data
For thirty years, maps were made for humans to look at. Now they need to be read by machines that act.
What can you build on xMap?
A real estate investor's agent evaluates a plot on Bleecker St, NYC.
Works wherever your agent lives.
agent = Agent(api_key=os.environ["XMAP_KEY"])
result = agent.evaluate(
parcel="314 Bleecker St, NYC",
objective="cafe_concept",
layers=["mobility","competition",
"demographics","parcel_price",
"attractions"],
radius_m=500,
)
print(result.decision) # "PROCEED"
print(result.confidence) # 0.84
print(result.recommended_action)# "lease, not buy"
{
"mcpServers": {
"xmap": {
"command": "npx",
"args": ["-y", "@xmap/mcp-server"],
"env": { "XMAP_API_KEY": "xm_..." }
}
}
}
// Tools available automatically:
// xmap_poi_search · xmap_mobility_query
// xmap_parcel_lookup · xmap_traffic_flow
// xmap_demographics_profile
-H "Authorization: Bearer xm_..." \
-d '{
"parcel": "314 Bleecker St, NYC",
"objective": "cafe_concept",
"layers": ["mobility","competition",
"demographics","parcel_price"],
"radius_m": 500
}'
# → { "decision": "PROCEED",
# "confidence": 0.84,
# "reasoning_trace": [...] }
Two ways to use xMap data.
https://api.poi-data.com/mcp/
YOUR_API_KEY
# REST
GET /v1/search?q=coffee
&near=40.730,-73.935&radius_m=500
How xMap fits into your agent stack.
model: "claude-opus-4-5",
tools: xmap.mcp_tools(),
messages: [{
role: "user",
content: "Evaluate 314 Bleecker St for a café"
}]
});
// Claude calls xmap_poi_search,
// xmap_mobility_query, xmap_parcel_lookup
// automatically - no routing needed.
agent = Agent(api_key=os.environ["XMAP_KEY"])
result = agent.evaluate(
parcel="314 Bleecker St, NYC",
objective="cafe_concept",
layers=["mobility","competition",
"demographics","parcel_price"],
radius_m=500,
)
print(result.decision) # "PROCEED"
print(result.confidence) # 0.84
m.daily_foot_traffic,
v.est_value_sqft,
COUNT(c.poi_id) AS competitors
FROM xmap.parcels p
LEFT JOIN xmap.mobility m
ON p.geom && m.bbox AND m.window='30d'
LEFT JOIN xmap.parcel_values v
ON p.parcel_id = v.parcel_id
LEFT JOIN xmap.poi c
ON ST_DWithin(p.geom,c.geom,500)
AND c.category='cafe'
WHERE p.city='New York'
AND m.daily_foot_traffic > 10000
GROUP BY 1,2,3,4;
700+ full integrations.
Your agents, connected.
Try it. No signup.
In production with builders shaping the next decade.
How xMap fits into your agent stack.
Live in 100+ countries.
Built for developers.
Pricing built for builders.
Questions worth answering up front.
Google Maps and Mapbox are built for displaying maps to human eyes - navigation, tiles, embeds. xMap is built for machines. Every layer ships with agent-ready schemas, tool definitions, and MCP bindings. There are no tiles, no SDKs for rendering, no visual map component. It's a data infrastructure layer, not a mapping product.
We meter usage in credits. Developer includes 1,000 credits at no cost. Pro starts at $99/mo with credit top-ups and auto-reload, and scales to 25 requests per second. Enterprise starts at 1M+ credits per month with unlimited queries per second, VPC or on-prem options, and custom SLAs. Every tier includes the full data stack your agents need.
POI data refreshes daily. Car traffic and GPS mobility update hourly. Parcel ownership and parcel price update weekly (or on public record filing for ownership). Demographics update monthly from aggregated panel data. Every snapshot is version-controlled - you can always query a specific date.
xMap aggregates from satellite imagery providers, anonymized mobile SDK panels, public land records, commercial data partners, and government open-data sources. All layers are licensed for commercial use. Our mobility data is privacy-preserving by design - no PII, no individual-level tracking, all data is aggregated and anonymized at source.
Run 'npx @xmap/mcp-server' and point Claude Desktop (or any MCP-compatible client) at it. The server exposes all 10 layers as named MCP tools. Your agent discovers them automatically - no routing code, no schema definitions to write. See our docs for a working Claude config in under 5 minutes.
Developer is capped at 5 requests per second. Pro supports 25 requests per second with production SLAs. Enterprise removes the ceiling with unlimited queries per second and limits tailored to your contract. Latency and uptime targets are agreed with your team on Pro and Enterprise.
Yes - Enterprise plans include VPC deployment on AWS, GCP, or Azure. We also support air-gapped deployments for regulated industries (banking, insurance, government). Contact sales for a scoping call.
All mobility data is aggregated and anonymized before it enters xMap. We never store or expose individual device IDs, individual trajectories, or any PII. Aggregates require a minimum cohort size before they're surfaced. xMap is GDPR-compliant, and our mobility data processing is certified under relevant privacy frameworks in each jurisdiction.
We believe agents need a shared map of the world.
That model has never existed in a form an agent can use. Maps were built for human eyes. Databases were built for human queries. Dashboards were built for human attention. None of them were built for a system that thinks at machine speed and operates at machine scale.
xMap is that model. We are building the canonical, queryable, live archive of the physical world - and we're making it the easiest layer in the agent stack to integrate.