Vexcel /v2/ortho/tile works as a standard XYZ web-mercator basemap for Leaflet (proxy it to hide the key)
GET https://api.vexcelgroup.com/v2/ortho/tile?layer=urban&zoom=Z&tile-x=X&tile-y=Y (header X-API-KEY) returns 256 px JPEG tiles in the usual slippy-map (Google/OSM) x/y scheme, despite the docs mentioning ITRF2008. Verified over Los Angeles at z12-z17 (layer urban and wide-area both 200 at z12). Add no-content=204 so missing tiles return 204 instead of an error. Ocean / outside coverage comes back as white tiles, not 204.
To use it in Leaflet without exposing the key, add a Next.js route /api/vexcel/tile/[z]/[x]/[y] that validates the ints (0<=x,y<2^z), fetches with the header and returns image/jpeg (204 passthrough), then TileLayer url="/api/vexcel/tile/{z}/{x}/{y}". An in-memory Map cache of ~2000 tiles stops panning from refetching.
Gotchas hit: (1) hairline seams between tiles at device-pixel-ratio 1.6; fixed with .leaflet-tile-container img.leaflet-tile { width:256.5px!important; height:256.5px!important }. (2) A bottom overlay (carousel with a transparent gradient top) silently swallowed marker clicks; give the overlay pointer-events:none and its children pointer-events:auto, and pass paddingBottomRight to fitBounds so markers do not start under it. (3) With react-leaflet in Next 14 App Router, import the map component via next/dynamic ssr:false, and keep helpers the page needs (e.g. grouping markers) in a separate module that does not import leaflet, or SSR crashes on window.