Introduction
Real-time agent matching and live location tracking, delivered as an API for your dispatch platform.
RideWiseCore is a hosted, multi-tenant dispatch engine. It does two jobs that are hard to build and run yourself:
- Matching: given a pickup point and a vehicle type, find the nearest available agent and offer them the ride. If they decline or don't answer in time, RideWiseCore offers it to the next closest agent.
- Tracking: take in live agent locations over a WebSocket, keep each agent's current position and status, and push updates back to you in real time.
You keep running your own passenger app, agent app and backend. Your backend calls RideWiseCore when it needs an agent or live positions.
What RideWiseCore does and doesn't handle
| RideWiseCore handles | Your platform keeps |
|---|---|
| Live agent positions and availability | Trip records and trip lifecycle |
| Finding the nearest eligible agent | Fares, pricing and payments with riders/agents |
| Offer → accept / decline / timeout escalation | Passenger and agent identity (names, phones, documents) |
| Real-time fan-out of agent and match updates | Your apps and your end-user authentication |
RideWiseCore only ever sees an opaque agent ID that you choose, plus coordinates, status and vehicle type. It never sees who your riders or agents are.
How your system connects
┌──────────────┐ ┌──────────────┐
│ Passenger app│ │ Agent app │
└──────┬───────┘ └──────┬───────┘
│ your own APIs / sockets │
▼ ▼
┌─────────────────────────────────────┐
│ YOUR BACKEND │ ← holds your RideWiseCore API key
└──────┬──────────────────────┬───────┘
│ HTTPS (REST) │ Socket.IO (WebSocket)
│ POST /matches … │ agent:location, ride:respond
▼ ▼ ▲ ride:offer, match:update, agent:update
┌─────────────────────────────────────┐
│ RIDEWISECORE │
└─────────────────────────────────────┘Only your backend talks to RideWiseCore. Your apps never connect to it directly, and your API key never ships inside a mobile app or browser.
Isolation
Every tenant's data lives in its own namespace. Your API key can only read and write your own agents, matches, usage and invoices; no request can reach another tenant's data.