Developers

Every capability is a REST endpoint.

Optimize routes, auto-dispatch, and orchestrate across carriers from your own stack. OAuth2 + JWT. Production-grade since 2016.

Talk to an engineer See the architecture

POST /v1/routes/optimize OAUTH2 · TLS · JWT

SDK v1.2.0 · py / js / curl

REQUEST bash

"tk-kw">curl -"tk-kw">X "tk-kw">POST /v1/routes/optimize \
  -H "Authorization: ">Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "project_id": "proj_7c2f",
    "objective": "minimize_vehicles",
    "constraints": {
      "max_route_duration_min": 480,
      "capacity": { "weight_kg": 1200, "volume_m3": 8 },
      "territories": ["tlv_north"],
      "time_windows": "per_stop"
    },
    "orders": [ /* 412 orders */ ],
    "vehicles": [ /* 18 vehicles */ ]
  }'

RESPONSE · 200 json

{
  "run_id": "run_8f02e41a",
  "status": "solved",
  "objective_value": 452.0,
  "solver_time_ms": 31840,
  "routes": [
    {
      "route_id": "R-0042",
      "vehicle_id": "v_0031",
      "stops": 14,
      "distance_km": 131.4,
      "duration_min": 452,
      "utilization": 0.87
    },
    { "route_id": "R-0043", "vehicle_id": "v_0032", "stops": 9,  "distance_km": 61.2,  "duration_min": 298, "utilization": 0.64 },
    { "route_id": "R-0044", "vehicle_id": "v_0033", "stops": 22, "distance_km": 148.9, "duration_min": 461, "utilization": 0.92 }
    /* +10 more routes */
  ],
  "unrouted_orders": [],
  "metrics": {
    "total_distance_km": 1740.3,
    "total_duration_min": 5892,
    "vehicles_used": 13
  }
}

What's in the API

Seven endpoints cover the full dispatch loop.

Order in. Optimize. Dispatch. Track. Reconcile. Every step is callable from your stack via REST.

/v1/routes/optimize
VRPTW solver. Hundreds of orders, dozens of constraints, seconds.
/v1/orders
Ingest, validate, enrich. Time windows, capacity, skills.
/v1/vehicles
Fleet, shifts, capacities, cost model, territory rules.
/v1/runs
Dispatcher runs. Status, metrics, plan versions.
/v1/carriers
Owned · contracted · on-demand. Per-ride decisioning.
/v1/pricing
Rule-based rate cards. Zone, time, vehicle, contract.
/v1/events
Stream surface. Status changes, exceptions, ETAs.

Architecture

Your stack on the left. Your fleet on the right. Mycelium in the middle.

One API surface between your systems of record and every carrier you dispatch to. Multi-tenant, multi-region, horizontally scaled.

YOUR STACK

YOUR ERP Scheduled sync or webhook

YOUR OMS Order feed · inventory

YOUR FLEET MGMT Bidirectional · REST/SOAP

YOUR APPS SDK · web · mobile

↓

MYCELIUM API

OAuth2 · TLS · JWT

/v1/routes/optimize

/v1/orders

/v1/vehicles

/v1/runs

/v1/carriers

/v1/pricing

/v1/events (stream)

SDK · PY · JS · CURL

↓

YOUR CARRIERS

OWNED FLEET Driver app · push

CONTRACTED Carrier webhook · SFTP

ON-DEMAND Ride-hail · dispatcher API

TRACKING · GPS Position · exceptions

Deployment shapes

Two deployment shapes.

Pick the shape that fits your stack. Identical capability surface in both.

Core.A

Full-stack deployment

Admin portal, consumer and employee apps, API, background workers, notifications, every integration.

Standard enterprise. Replaces a dispatcher workflow end to end.

Core.B

API-only deployment

API surface plus the optimization and dispatch workers. No UI layer. Present your own brand end to end.

Embedded partners, high-volume API customers, cost-optimized deployments.

Integration surface

Eight integration categories. Production-grade.

Every category listed below runs in at least one production deployment. Specific partners and endpoints ship on request.

RIDE-HAILING

Partner dispatch APIs
Branded consumer flow
Per-ride decisioning

In production since 2016

FLEET MANAGEMENT

SOAP and REST feeds
Bidirectional sync
Custom fleet APIs

Vehicle status · driver availability

ERPs · OMS · E-COMMERCE

Scheduled sync
Webhook push
Custom endpoints

Orders in · status out

AIRLINE BOOKING

Crew-scheduling feeds
Custom airline APIs

Flight-schedule triggers

PAYMENTS · NOTIFICATIONS

SMS gateway
Email (SMTP)
Custom webhooks

Delivery receipts · alerts

MAPPING

Multi-provider routing
Automatic fallback
Traffic blended into cost

Provider-agnostic by design

HR · WORKFORCE

Shift management
Eligibility sync
Role and policy

Employee directory · budget

TRACKING · GPS

Multi-tracker aggregation
Plan-vs-actual overlay

Presentation layer across carriers

Auth

OAuth2 client-credentials. JWT everywhere.

Short-lived access tokens, per-tenant service accounts, per-user scopes, administrator-controlled rotation. Customer data is partitioned per tenant. Mechanism specifics (isolation enforcement layer, audit-log format, key management) are implemented per our ISO 27001 ISMS scope; details available under DPA on request.

Authorization scopes travel in the token claim.
RBAC per user.
Audit logs on state-changing API calls. Read APIs are logged.
IP allowlists available on request.

ISO 27001 certified. Full security posture, certificate downloads, data-flow model.

Scale

Built for production load, not pilot traffic.

100-500

orders per optimization run

1000s

API requests per hour, second-scale response

Async

queue-backed long runs, synchronous short runs

Stateless

horizontal scaling, no sticky sessions

Talk to us about API access.

Tell us the integration shape you're after. We'll reply with the right engineer on the thread within one business day. Embedded partner? See white-label apps →

Talk to an engineer See how pricing works