Request drivers
Create orders of any mode — ride, delivery, freight. The registry routes each order to the right node, and you receive status events in real time as it's accepted, dispatched and completed. Registry routing · roadmap
For AI agents
The mobility protocol for agents.
Let your agent hail a car, coordinate a fleet, or dispatch a delivery — by API, across the whole network. One protocol reaches every node: cities, countries, companies, without integrating one by one.
Request Offer capacity Orchestrate
Agent API · request
POST/api/v1/orders
mode"ride"
pickup-34.603, -58.381
dropoff-34.588, -58.420
networkauto · registry routes
Response
200 OK 12 ms{
"order_id": "ord_9fA2",
"status": "routing",
"node": "ba-centro",
"mode": "ride",
"events": "stream"
}What your agent can do
Request, offer, orchestrate — by API.
One interface for moving people and things. Create orders of any mode, publish the capacity you manage, or coordinate many dispatches at once — and receive status events in real time.
Offer capacity
If your agent manages a fleet, publish availability or offer drivers to open orders. Your capacity becomes discoverable to the network without you wiring up each counterparty by hand.
Orchestrate
Coordinate multiple dispatches — an event's transport, a day's logistics — with capacity queries and reservations. One agent, many moving parts, a single protocol underneath.
Why a protocol, not one more API
Speak one protocol. Reach every network.
Your agent speaks a single protocol and reaches every network — cities, countries, companies — without integrating one by one. Reputation and payments stay verifiable, and driver admission always passes identity verification: the protocol is open, the network is trustworthy.
N integrations, N contracts
Every city, country and company is a separate API, a separate key and a separate onboarding. Your agent's reach is capped by how many you've wired up by hand — and each one drifts on its own schedule.
One protocol, every node
Integrate once. The registry routes your order to whichever node can serve it, reputation and payments are verifiable end-to-end, and admission is always identity-checked — so an open protocol stays a trustworthy network. Network plane · roadmap
Real-time status
You dispatch. The network reports back.
After an order is created, the registry routes it to the right node and you receive status events in real time — routed, accepted, en route, completed. Your agent reacts to each step instead of polling for it.
Capacity queries and reservations let one agent coordinate many dispatches at once — and every fare and rating in the stream is verifiable, not asserted.
Order ord_9fA2 · eventslive
00:00.4order.routed → node ba-centroregistry
00:03.1order.accepted by driver drv_7c1ba-centro
00:05.8driver.en_route · 2 min to pickupba-centro
11:42.0trip.completed · fare $ lockedledger
11:42.3rating.settled · reputation updatedledger
Build status. The Agent API on the operation plane lets your agent create and track orders against a node today. The network plane that routes across every node — registry, ledger, roaming and the open protocol — is on the roadmap and shown here as a target architecture, not a live service. Events tagged registry and ledger above illustrate that target.
Start building
From a key to a dispatch in two calls.
Mint an Eye Key, create an order of any mode, and subscribe to its event stream. Your agent speaks one protocol — the network does the routing.
# 1 · create a transport order of any mode
curl -X POST https://api.technorides.dev/api/v1/orders \
-H "Authorization: Eye-Key $KEY" \
-d '{"mode":"ride","pickup":[-34.603,-58.381],"dropoff":[-34.588,-58.420]}'
# 2 · stream real-time status events for the order
curl -N https://api.technorides.dev/api/v1/orders/ord_9fA2/events \
-H "Authorization: Eye-Key $KEY"// Cross-network routing via the registry is roadmap — today an order is created against the node you hold a key for.
Under the Agent API
The modules your agent talks to.
The interface is one Agent API; behind it, real modules do the work. The operation plane is what ships today; the network plane — where one protocol reaches every node — is in build.
Agent API · the stack
M16
M16
Agent API
The programmatic interface your agent calls to request drivers, offer capacity and orchestrate dispatches.
M10
M10
Automatic dispatch
Nearest-driver routing that turns an order into an accepted trip and emits the status events you subscribe to.
M13
M13
Payments
The fare is locked at dispatch and settles verifiably — your agent reads amounts it can trust, not ones it asserts.
M06
M06
Network Registry & Protocol
Routes one order across every node and keeps reputation verifiable, with identity-checked admission. In build · roadmap
Get started
One protocol. Every network. Your agent.
Read the protocol, mint a key, and let your agent hail a car, coordinate a fleet, or dispatch a delivery — by API, across the whole network.