thinair-co

thinair-co Routing API

The Routing API from thinair-co — 6 operation(s) for routing.

GitHub OpenAPI

Operations 6

GET /v1/isochrone Generate reachability polygons (isochrones) #
POST /v1/directions Compute a route between two locations #
GET /v1/locate Locate — road-network context for one coordinate #
POST /v1/distance-matrix Compute an N×M distance + duration matrix #
POST /v1/map-match Snap raw GPS breadcrumbs to the road network #
POST /v1/trace-attributes Road attributes along a matched GPS trace #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/thinair-co/openapi/thinair-co-routing-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/thinair-co/json-schema/thinair-co-optimize-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/thinair-co/json-schema/thinair-co-migrations-generate-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/thinair-co/json-schema/thinair-co-quota-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/thinair-co/json-schema/thinair-co-tables-profile-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/thinair-co/json-schema/thinair-co-query-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/thinair-co/json-schema/thinair-co-connection-health-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/thinair-co/json-schema/thinair-co-directions-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/thinair-co/json-schema/thinair-co-directions-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/thinair-co/json-schema/thinair-co-map-match-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/thinair-co/json-schema/thinair-co-locate-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/thinair-co/json-schema/thinair-co-explore-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/thinair-co/json-schema/thinair-co-autocomplete-response-schema.json

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/thinair-co:thinair-co-routing-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

thinair-co-routing-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: ThinAir Geo Routing API
  version: 1.0.0
  description: '## Overview


    Geocoding, autocomplete, structured search, place IDs, intersections, routing, distance matrix, isochrones, map matching, traffic, weather, and POI search — one API. REST and MCP consume the same ThinAir Geo service layer; this spec describes the REST surface.


    ## Base URL & authentication


    All endpoints live under `https://geo.thinair.co`. Authenticate with a bearer API key:


    ```bash

    curl "https://geo.thinair.co/v1/geocode?text=Pike Place Market Seattle" \

    -H "Authorization: Bearer ta_geo_…"

    ```


    ## Observability


    Every REST response carries a correlation pair (`X-Request-Id` / `X-Trace-Id`), a cache status (`X-Cache: HIT | HIT-EDGE | STALE | MISS | BYPASS`), and a per-stage timing family (`X-Auth-Ms`, `X-Quota-Ms`, `X-Upstream-Ms`, `X-Worker-Ms`, `X-Edge-Ms`, `X-Total-Ms`) — see components.headers for the full surface. Edge-cached lookups answer in single-digit milliseconds at the edge (verifiable via `X-Edge-Ms`); cold geocoding runs through the regional engine.


    ## Quota


    The daily-quota debit is write-behind on all API-key plans, so `X-Quota-Used` / `X-Quota-Remaining` are eventually consistent (typically within ~30 seconds); `GET /v1/quota` is the authoritative synchronous count.


    ## Enterprise access


    `https://geo.thinair.co` is the canonical public API and MCP surface. Azure API Management (APIM) is available as an enterprise access layer — private deployments, custom quota/SLA, VNET/private-link connectivity, subscription keys, and customer-side governance. APIM is an enterprise access layer. It does not own product behavior. All product behavior lives in the shared ThinAir Geo service layer consumed by REST, MCP, and APIM. APIM calls the same service layer (no separate business logic), preserves request/trace ids and ThinAir response shapes, and may add enterprise auth, quota, IP policy, logging, and private networking. Public documentation keeps `https://geo.thinair.co` as the canonical base URL; enterprise base URLs are issued per customer.'
servers:
- url: https://geo.thinair.co
security:
- bearerAuth: []
tags:


# --- truncated at 32 KB (92 KB total) ---
# Full source: https://artifacts.apis.io/thinair-co/openapi/thinair-co-routing-api-openapi.yml