MODULE
Orders
orders-api.mesh.locate2u.appCreate orders, tag them, attach the driver skills they need, move them through status.
PRIVATE BETA · API V1
Logistics rails
Logistics rails
for the agentic era.
Locate2u Mesh is the delivery operations data plane, exposed as twenty REST APIs. Orders, stops, runs, drivers, vehicles, live tracking, geofences, rates, road distances — each one a documented endpoint, each change a signed webhook. You build the product; Mesh runs what sits underneath it.
EVERY SERVICE, SAME CONTRACT
REST · no GraphQL
OpenAPI 3.1
Swagger UI
Health + version
Idempotent writes
Per-tenant scope
CAPABILITIES · SUBSCRIBE PER MODULE
Twenty services.
One token.
Each module is an independently deployed service on its own hostname, with its own OpenAPI document and its own events. A tenant subscribes to the modules it needs; one OAuth2 client reaches all of them.
MODULE
TELEMETRY & EVENTS
SPATIAL
MODULE
Stops
stops-api.mesh.locate2u.appStops and their locations, timings, capacities, packages, skills and categories.
MODULE
Runs
runs-api.mesh.locate2u.appA driver's route for a date — core CRUD plus the run status lifecycle.
MODULE
Run schedules
run-schedules-api.mesh.locate2u.appRecurring run templates: a weekday cadence in a timezone, stored as a definition.
MODULE
Drivers
drivers-api.mesh.locate2u.appDriver records, licence and insurance compliance, weekly roster, blockouts, skills.
MODULE
Users
users-api.mesh.locate2u.appTenant user records, membership lifecycle, and tenant-defined permission groups.
MODULE
Assets
assets-api.mesh.locate2u.appThe fleet — vehicles and trailers, plus named groupings of them.
MODULE
Facilities
facilities-api.mesh.locate2u.appWarehouses, depots and offices, and the zone / aisle / rack / bin locations inside them.
MODULE
Documents
documents-api.mesh.locate2u.appDocument metadata and expiry: licences, insurance, registrations, certifications.
MODULE
Rates
rates-api.mesh.locate2u.appRate groups, rates, conditions and zones — and the engine that prices a stop into charges and costs.
MODULE
Tracking links
tracking-links-api.mesh.locate2u.appShareable opaque links to a stop, with anonymous resolve. You render the page.
MODULE
White labeling
white-labeling-api.mesh.locate2u.appPer-host brand and theme config, resolvable by hostname without a token.
TELEMETRY
GPS ingest
ingest-api.mesh.locate2u.appWrite-only firehose. Authenticate, stamp, produce to Kafka, return 202. No business logic.
TELEMETRY
Tracking
tracking-api.mesh.locate2u.appThe read side: last-known position from the cache, history from the warm warehouse.
TELEMETRY
Geofences
geofences-api.mesh.locate2u.appNamed boundaries that fire entry, exit and dwell events when the GPS stream crosses them.
TELEMETRY
Webhook subscriptions
subscriptions.mesh.locate2u.appSubscribe to the event stream. Signed with HMAC-SHA256, retried with backoff, dead-lettered.
SPATIAL
Polygons
polygons-api.mesh.locate2u.appOne shared boundary library — geofences, service areas and rate zones all link to it.
SPATIAL
Service areas
service-areas-api.mesh.locate2u.appWhich drivers cover which regions. Passive: unlike geofences, it emits no events.
SPATIAL
Geocoding
geocoding-api.mesh.locate2u.appForward, reverse and bounded batch. One abstraction, so the vendor can change underneath.
SPATIAL
Routing
routing-api.mesh.locate2u.appRoad distance matrix, the driving route, map matching, snap-to-road. Not turn-by-turn.
ARCHITECTURE
Two layers.
Nothing behind a UI.
The Management Layer is where a tenant is set up — modules switched on, OAuth clients issued, permissions granted, webhook subscriptions registered. The Public Layer is where the work happens: orders, stops, runs, vehicles, positions. There is no privileged path into either. Our own portals call the same APIs you do.
- OpenAPI generated from the routes Not hand-maintained — spec drift is impossible by construction
- Signed webhooks, retried and dead-lettered GPS POST to delivered webhook in roughly 520 ms, measured end to end
- Multi-tenant by construction Tenant identity comes from the verified token, never the request body
YOUR APPLICATIONS
CLIENTS
REST · ANY STACK
Your ops product
OPENAPI · MCP
Your AI agent
POST · 202
Your driver app
PUBLIC LAYER · *-api.mesh.locate2u.app
20 services
REST · OPENAPI 3.1
Module APIs
SIGNED · RETRIED
Webhooks
202 · KAFKA
GPS ingest
MANAGEMENT LAYER · management-api.mesh.locate2u.app
tenants · modules · tokens
WEB UI
Management Portal
TOKENS · SCOPES
Management API
/API/SERVICES
Service registry
SERVICES · COMPOSABLE
20 SERVICES
Orders
Stops
Runs
Run schedules
Drivers
Users
Assets
Facilities
Documents
Rates
Tracking links
White labeling
GPS ingest
Tracking
Geofences
Subscriptions
Polygons
Service areas
Geocoding
Routing
BUILT FOR AGENTS
Every endpoint
describes itself.
Each service publishes an OpenAPI 3.1 document at /api/openapi.json,
generated from its own routes — so it cannot drift from the code — plus a plain
GET /api that returns what the service is for, how to authenticate, and
the list of endpoints. An agent reads those and knows how to call Mesh. No SDK to
install, no integration to hand-write, no tool definitions to maintain.
OPENAPI
3.1, generated from the routes
GET /api
Purpose · auth · endpoint list
MCP
Specs published as resources
OAUTH2
Client credentials, tenant-scoped
SPECS & CONTRACTS
Everything you need to call it
OpenAPI 3.1
$ runs-api.mesh.locate2u.app/api/openapi.json
Swagger UI
$ runs-api.mesh.locate2u.app/api/docs
Service root
$ GET /api · purpose, auth, endpoints
Service registry
$ management-api.mesh.locate2u.app/api/services
MCP resources
$ mcp.mesh.locate2u.app/mcp
Webhook signing
$ x-mesh-signature · HMAC-SHA256
READY WHEN YOU ARE
Build your delivery product
on someone else's plumbing.
Mesh is in private beta. Create an account, switch on the modules you need, and issue yourself a client credential — the same path our own portals take.
