Audisory

Private beta · Rwanda first

Routing built for the way Rwanda moves.

Directions, matrices, isochrones and elevation for teams moving people and goods across Rwanda. Local travel profiles, the hills in every route, and prepaid pricing with hard caps.

Try a live routeRequest access
Kigali route lab
Open full playground

Route from Kigali city centre to Kigali International Airport by Motorcycle taxi: calculating.

Six travel profilesMoto as a first-class profileCopernicus 30 m terrainOpenStreetMap roadsVersioned data releasesPriced in RWFHard spend caps by defaultBuilt in Kigali

01 / The platform

The details make the difference.

Mapping is a working part of your product. We focus on a few things and try to do them properly, starting with the roads and hills of one country.

01

Routes with the whole story.

Alternatives, waypoint legs and turn-by-turn steps, with distance, duration and average speed on every leg.

Directions · Matrix · Isochrone

02

The terrain is in the answer.

Ascent, descent and maximum grade come back with each route, so a climb up Mont Kigali never looks like a flat road.

Elevation · Grades

03

Know what answered you.

Each response carries a request ID, the data release it used and the credits it cost. Trace any result back to its source.

request_id · data_version · credits_charged

4

API endpoints

6

travel profiles

30 m

terrain resolution

RWF

local pricing

02 / The API

Four endpoints. One honest envelope.

Plain JSON over HTTPS with a bearer key. Every response tells you what it cost and which data answered it.

1 credit per route

Routes with the whole story.

  • 2–50 coordinates
  • 0–3 alternatives
  • polyline6 or GeoJSON
POST/v1/directions
{
  "coordinates": [
    [
      30.0606,
      -1.9441
    ],
    [
      30.1395,
      -1.9686
    ]
  ],
  "profile": "moto",
  "alternatives": 2,
  "include_steps": true
}

03 / Rwanda first

A thousand hills change the maths.

Generic routing treats every country the same. We started with one, and built the profiles, terrain and pricing around how it actually moves.

  1. Moto is a first-class profile.

    Motorcycle taxis and delivery riders do a lot of Kigali's moving. They get their own travel profile, not a car profile with a different label.

  2. Hills are part of the answer.

    Routes report ascent, descent and maximum grade from Copernicus terrain. Four kilometres uphill and four kilometres on the flat are different trips.

  3. People carry things.

    Alongside walking, a loaded-walking profile covers trips on foot with goods: market runs, last metres, deliveries up a hillside path.

  4. Priced in Rwandan francs.

    Credit packs are quoted in RWF and paid through local checkout. Your balance and caps live in the console, not in a surprise invoice.

04 / Built for real work

Different journeys. Common ground.

A delivery, a daily commute, a product taking shape. The same API underneath, tuned to the trip.

Delivery & logistics01 / 03

A better view of the last mile.

Compare routes between depots and drop-offs, batch riders with a matrix, and see the climb before a rider leaves. Built around the motorcycle, because that is how much of Kigali delivers.

  • Moto, car and truck profiles
  • Matrix for dispatch and batching
  • Ascent and grade on every route
Explore in the playground
Your distribution pointThe next delivery
Mobility02 / 03

Built around how people move.

Estimate trips for riders and drivers, show honest ETAs, and draw reachable areas around a pickup. Walking and loaded-walking profiles cover the trips that never touch a road vehicle.

  • Six travel profiles
  • Isochrones for service areas
  • Alternatives with legs and steps
Explore in the playground
Where the journey startsWhere it needs to go
Developers03 / 03

Local infrastructure. Your interface.

A familiar JSON API with request IDs, data versions and credit charges in every response. Try your own key in the console playground, then copy the request into your code.

  • Server-side secret keys
  • Daily credit caps you control
  • Usage and receipts in the console
Explore in the playground
Your applicationA traceable response

05 / Made for builders

From first request to the road.

  1. 01

    Request access

    Tell us what you are building. We invite teams in small cohorts.

  2. 02

    Create a key

    Secret keys live in the console. The full key is shown once, then only its prefix.

  3. 03

    Try it with your key

    The console playground runs your own requests: click the map, edit the body, read the response.

  4. 04

    Ship with caps on

    Daily limits and a prepaid balance mean a bug can never become a bill.

Try a live request

Your first connection

POST /v1/directions
curl -X POST https://api.audisory.example/v1/directions \
  -H "authorization: Bearer sk_live_..." \
  -H "content-type: application/json" \
  -d '{
    "coordinates": [[30.0619, -1.9441], [30.1395, -1.9686]],
    "profile": "moto",
    "departure_time": "2026-09-02T07:15:00+02:00"
  }'
  • Traceable request IDs
  • Explicit credit charges
  • Versioned map data

06 / Data & trust

Boring where it matters.

Infrastructure should be predictable. Here is how we keep the data honest and the bill bounded.

Open map data

Roads from OpenStreetMap, credited on every map as the ODbL requires. Our own operational data is kept separate from it.

Releases with gates

Each data release is built, checked against routing and terrain QA gates, then switched over in one step. A bad build never goes live.

Metered and capped

Credits are reserved before work starts and settled after. At zero balance or at your daily cap, requests stop with a clear 402.

07 / Predictable by design

Your usage. Your limits.

Prepaid credits keep usage visible. Hard spend caps are on by default; at zero credits, requests stop. Access is currently by invitation.

Free

Free

2,000 credits

2,000 credits a day, non-commercial. For developers, students and NGOs.

Request pilot access

Find your starting point.

Estimate a month of requests with the credit calculator.

Monthly usage
Credits per month90,000
PackStarter
You payRWF 72,159 per pack
Effective rateRWF 144 per 1,000
Google Maps PlatformRWF 1,325,376/mo
You saveRWF 1,253,217/mo

Google's figure uses a flat $5 per 1,000 requests and ignores their monthly credit, so treat it as indicative. Amounts use our fixed catalog exchange rate. Audisory packs are prepaid; there is no recurring subscription or overage.

08 / Where we are

Early, and honest about it.

We are a small team in private beta. This is what works today and what we are building next.

Now

  • Directions, matrix, isochrone, elevation
  • Customer console with keys, usage and receipts
  • Prepaid RWF credit packs with hard caps

Next

  • Reviewed road closures and construction in routing
  • Time-of-day speed rules
  • Address search and geocoding for Rwanda

Later

  • Traffic from de-identified partner aggregates
  • Static map images
  • Neighbouring countries, once Rwanda is right

09 / A little more context

Good questions. Clear answers.

Something missing? Ask in your access request and we will answer it there.

10 / Build with us

Your next idea. A local foundation.

Tell us what you are building. We review access requests and invite teams in small cohorts, so we can help each one get started properly.

  1. 01Share your use case
  2. 02We review your request
  3. 03Receive an invitation by email

Request early access

Roughly. Zero is a fine answer.

We store only what is on this form, and we use it to decide who to invite next. No newsletter, no reselling. Rwanda Law No. 058/2021 applies and you can ask us to delete your entry at any time.