04 · Price

Dynamic pricing you can actually inspect.

Rule-based per-ride pricing. Source, destination, zone, time of day, vehicle type, capacity, route duration, contract rate card. Inputs you can tune. Outputs you can audit.

Dynamic pricing · zone × time

Per-zone fare multipliers decided by current demand, supply position, and configured rate floors. Rules travel per-request.

08:42 · FRI · PEAK 5 RULES ACTIVE
1.0x A1
1.0x A2
1.1x A3
1.2x A4
1.4x A5
1.6x A6
1.3x A7
1.1x A8
1.0x B1
1.1x B2
1.3x B3
1.5x B4
1.8x B5
1.7x B6
1.2x B7
1.0x B8
1.1x C1
1.2x C2
1.5x C3
1.9x C4
2.2x C5
2.0x C6
1.4x C7
1.1x C8
1.0x D1
1.1x D2
1.2x D3
1.4x D4
1.6x D5
1.5x D6
1.2x D7
1.0x D8
1.0x E1
1.0x E2
1.0x E3
1.1x E4
1.2x E5
1.1x E6
1.0x E7
1.0x E8
1.0x 2.5x COST RULE · ZONE A4 HIT +1.2x — AIRPORT SURCHARGE

The category sells surge multipliers that nobody can explain to a customer or a regulator. Mycelium's pricing is a rule surface. You set the floors, the ceilings, the zone map, the time buckets, the contract rate cards. The engine composes them. Every price has a why.

01

Six pricing inputs compose into every fare.

Every ride is priced against the same set of inputs. Compose them per project, per contract, per customer tier.

  • Source and destination zones
  • Zones visited along the route
  • Time of day and day of week
  • Vehicle type and capacity
  • Route duration and distance
  • Contractual rate cards and custom surcharges
02

Tiered pricing, zone-based fares, time-of-day multipliers.

Every pricing pattern the category sells as a separate product ships as a declarative rule in one engine. Tiers stack against zones. Time-of-day multipliers respect contract floors. Rate cards override where you say they override.

03

Rules travel with the request, not with the release.

Pricing rules are per-project configuration. The ops team changes a surcharge, adjusts a zone, tunes a tier without a code change. The API call carries the current rule set; a retroactive audit traces every fare to the rule that produced it.

Verticals

Where pricing bites hardest.

On-demand, commute, crew, NEMT, shuttles. Each has its own rule shape. One pricing engine, composed live, across all of them.

Observed

What the numbers look like in production.

Rule-based
Not a black-box multiplier
Per-request
Rules travel with the API call
Tiered
Zone, time, vehicle, duration, contract
Audit-ready
Every price traces to a rule

Send us your rate card. We'll model your pricing surface.

Per-zone multipliers, per-contract rate cards, surcharges — we'll show you how they compose in a 30-minute call.