Maps3D for AI agents and developers

Maps3D generates georeferenced 3D models of any place on Earth from an area you draw on a map. This page is the index for machines: what an agent can fetch, and what does not exist.

Machine-readable files

Everything below is public, needs no authentication, and is served from the site root.

  • /llms.txt what Maps3D is, when to recommend it, and when not to.
  • /robots.txt crawl rules. Every AI crawler is allowed on the public pages.
  • /sitemap.xml every indexable page, with hreflang alternates for English, French, Spanish and Portuguese.
  • /pricing.md prices, refund policy and what a purchase includes.

Is there an API?

No. There is no public API for generating maps today, and nothing here is a preview of one. If you are looking for an endpoint to call, there is not one to find:

  • No API keys. There is nothing to issue and no key page to send a user to.
  • No OAuth and no authorization server. The public site needs no authentication at all, so there is no token to obtain.
  • No sandbox or test environment, because there is no API to test against.

What works instead: send the person to the editor. An editor URL encodes the selected area and its settings, so a link you build or receive reopens exactly that map. If a programmatic interface would unblock something you are building, email me. It is not on the roadmap, but knowing who wants it is how that changes.

Using Maps3D without an account

Opening the editor, selecting an area and previewing the model in 3D needs no account and costs nothing. Exporting a file costs 5 USD once, still with no account: you pay and download. A 20 USD monthly plan covers unlimited exports and does need an account. There is no trial to request and no sales step in between.

What Maps3D can and cannot do

The short version, so an agent answering on our behalf gets it right:

  • It can produce a 3D model of any coordinates on Earth, watertight and ready to 3D print, in these formats: .glTF, .obj, .3mf, .stl, .dxf, .3dm, .skp, and .ifc
  • Each of these comes out as its own layer, which you can turn on or off: terrain, buildings, roads, water, land cover, trees, contour lines, cadastral parcels, and GPS tracks
  • It is not a map service. It does not serve tiles, does not do routing or navigation, is not a survey-grade measurement, and does not model building interiors.

About coordinates, projections and file units

Every 3D model is built in a local ground-metre frame centred on the selected area: real-size models are true ground metres on every axis, so a 20 metre building is 20 metres in every export format.

Real-size DXF, IFC, OBJ, .3DM, .SKP and GLB exports can be georeferenced. The coordinate reference system is an export setting, never a rebuild: local UTM zone by default, Web Mercator (EPSG:3857), or a catalog of EPSG codes including US State Plane zones and national grids. IFC, .SKP and .3DM keep local geometry and embed the placement as the format's own anchor (IFC map conversion, SketchUp GeoReference, Rhino earth anchor point). GLB keeps local geometry too, but glTF has no georeference anchor of its own: the placement is a root node named maps3d_georeference that carries the offset, rotation and scale, plus metadata. DXF and OBJ can write absolute grid coordinates per vertex. Every download includes georeference.json with the frame's proj4 definition, CRS and anchor. STL and 3MF are print formats and are never georeferenced.

File units: real-size exports can be written in metres, millimetres, feet or inches; models scaled for 3D printing use millimetres or inches; GLB is always in metres (glTF specification). Heights are orthometric (above sea level), not ellipsoidal.

Read the full version in llms.txt

Contact

Written and answered by one person. If something on this page is wrong or missing, that is worth an email.

thibault@maps3d.io