No fleet of your own
Use the capacity of companies and drivers already active on the network. No couriers to hire, no vans to lease, no dispatch desk to staff — you dispatch, the network delivers.
For merchants
Last mile on the network.
Dispatch your orders with motos, cars, or trucks from the network — whatever the shipment needs — without running your own fleet. Your customer tracks the delivery live from a link, no app, and you get proof of delivery at the door.
Moto Car Truck
Order #4821 · on the way
Picked up at your store14:02 · M01 Bakery
En route to you14:09 · 6 min to drop
Proof of delivery at the doorphoto · signature · code
How it works
From a created dispatch to proof at the door.
Create a dispatch — pickup at your store, drop at the customer. The registry routes it to your city's node and assigns the vehicle by shipment size. Your customer tracks it live; you close it with verifiable proof.
1
Create a dispatch
Pickup at your store, drop at the customer — from the merchant panel, or automatically from your own system on order confirmation. Set the parcel size and any special handling.
2
The registry routes to your city's node
The dispatch is routed to your city's node, which assigns the vehicle by shipment size — moto for a small parcel, truck for freight — drawing on capacity already active on the network. Registry routing · roadmap
3
Your customer tracks it live — no app
A tracking link shows the courier on a live map and the delivery timeline. No download, no account — your customer just opens the link.
4
Proof of delivery
The drop closes with proof — a photo, a signature, or a code at the door — so every delivery has an auditable record, not just a status flag.
What you get
Delivery capacity you don't have to own.
Plug last mile into your store without standing up a fleet, hiring couriers, or building dispatch yourself. The network already moves things — your orders just join it.
The right vehicle
Moto for a small parcel, truck for freight — the node assigns the vehicle by shipment size, so a single box and a pallet are both handled by whatever the load actually needs.
E-commerce & POS integration
Webhooks and an API: your system creates dispatches automatically on order confirmation, then receives status events back — no one re-keying orders into a second tool.
Cash on delivery
Collect cash at the door where the node supports it, with auditable reconciliation — so the money your courier takes in matches the orders, line by line.
Volume
Batch import of dispatches for large operations: upload a day's drops at once instead of creating them one at a time, and let the node fan them out.
Proof of delivery
Every drop closes with a photo, a signature, or a code — an auditable record of who received what, not a status that anyone can flip by hand.
Proof at the door
Three ways to prove the drop happened.
Pick the proof that fits the shipment. Whatever you choose, it lands as an auditable record against the dispatch — usable for support, disputes, and reconciliation.
A photo at the door
The courier captures the parcel where it was left. Best for contactless drops and high-value items.
A signature on receipt
The recipient signs on the courier's device. Best when a named hand-off matters.
A one-time code
Your customer reads back a code to confirm receipt. Best for verified, paid-in-advance orders.
E-commerce & POS integration
Your store creates the dispatch — automatically.
Wire the Merchant API into your checkout or point of sale, and a confirmed order becomes a created dispatch with no one re-keying anything. Status events come back to your system as the courier accepts, picks up, and delivers.
For large operations, batch import sends a whole day of drops at once. Where the node supports it, cash on delivery reconciles against your orders, line by line.
# on order confirmation · create a delivery dispatch
curl -X POST https://api.technorides.dev/api/v1/dispatches \
-H "Authorization: Eye-Key $MERCHANT_KEY" \
-d '{
"pickup": {"store":"bakery-centro"},
"dropoff": {"to":"order_4821"},
"parcel": "small",
"cod": {"amount": 5400, "currency": "ARS"},
"proof": "photo"
}'
# webhook → your store receives status events back
# dispatch.routed · accepted · picked_up · deliveredBuild status. The Merchant API and dispatch, tracking, and payments run on the operation plane against a node today. Cross-city registry routing — picking which node serves a dispatch across the network — is on the roadmap and shown here as a target architecture, not a live service. Cash on delivery is available where the node supports it.
Under the Merchant API
The modules that move your order.
The interface is one Merchant API; behind it, real modules do the work. The operation plane — dispatch, payments, tracking — is what ships today; the registry that routes across every node is in build.
Merchant API · the stack
M17
M17
Merchant API
The interface your store calls — webhooks and endpoints that turn a confirmed order into a created dispatch, with status events back.
M10
M10
Automatic dispatch
Routes the dispatch and assigns the vehicle by shipment size, drawing on capacity already active on the node.
M14
M14
Tracking
Powers the no-app customer link — the courier on a live map and the delivery timeline, in real time.
M13
M13
Payments
Cash on delivery with auditable reconciliation where the node supports it — collected at the door, matched to your orders.
M06
M06
Network Registry & Protocol
Routes a dispatch to whichever city's node can serve it, across the network. In build · roadmap
Start dispatching
Tell us about your last mile.
A few details about your store and volume, and we'll set you up on the network — or point you straight at the Merchant API if you'd rather build.
Get started
Last mile, on the network.
Dispatch with motos, cars, or trucks from the network — the right vehicle for the shipment — without running your own fleet. Live tracking for your customer, proof of delivery at the door.