ROOTE

ROOTE provides a French-language mobility platform that offers live mobility data, geocoding, nearby transport options, and urban services via a REST API. The service targets developers building AI agents, mobile apps, and location‑based products, delivering real‑time information on transport options, routes, and availability across multiple cities.

ROOTE publishes 15 API contracts indexed on the APIs.io network, including Capabilities API, Changelog.json API, Charging API, and 12 more. Tagged areas include Mobility, French, Artificial Intelligence, and Transportation.

The ROOTE catalog on APIs.io includes 1 Spectral governance ruleset.

ROOTE’s developer surface includes changelog, authentication, API reference, documentation, getting-started guide, and 13 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

31.9/100 thin ▬ flat Agent 25/100 agent aware Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

1 published contract 1 MCP Servers 1 Agent Skills

MobilityFrenchArtificial Intelligence Transportation

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Location & Mapping

AE-120

ChargingGeocodeParkingPlace SearchReverse Geocode

GET /v1/geocode GET /v1/place-search GET /v1/reverse-geocode GET /v1/charging/nearby

Consumer Travel, Events & Local Services

AE-210

Ride HailingTransit

GET /v1/ride-hailing/estimates

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 31.9/100 · thin

Contract Quality 10.1 / 21

Developer Ergonomics 8.8 / 17

Access Clarity 0.0 / 17

Operational Transparency 1.7 / 11

Contract Governance 1.9 / 10

Discoverability 4.5 / 9

Regulatory Posture 2.3 / 15

Agent readiness — 25/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/roote/"><img src="https://apis.io/badge/roote/card.svg" alt="ROOTE on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 0.0 — up to +20.0 composite points
Contract Quality scores 47.5 — up to +13.1 composite points
Operational Transparency scores 15.8 — up to +10.9 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/roote/apis.yml: open an issue on github.com/api-evangelist/roote to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 15

Individual APIs this provider publishes, each with its own machine-readable definition.

ROOTE Capabilities API

The Capabilities API from ROOTE — 1 operation(s) for capabilities.

ROOTE Changelog.json API

The Changelog.json API from ROOTE — 1 operation(s) for changelog.json.

ROOTE Charging API

The Charging API from ROOTE — 1 operation(s) for charging.

ROOTE Geocode API

The Geocode API from ROOTE — 1 operation(s) for geocode.

ROOTE Health API

The Health API from ROOTE — 1 operation(s) for health.

ROOTE Mobility API

The Mobility API from ROOTE — 1 operation(s) for mobility.

ROOTE Nearby API

The Nearby API from ROOTE — 1 operation(s) for nearby.

ROOTE Openapi.json API

The Openapi.json API from ROOTE — 1 operation(s) for openapi.json.

ROOTE Parking API

The Parking API from ROOTE — 1 operation(s) for parking.

ROOTE Place Search API

The Place Search API from ROOTE — 1 operation(s) for place search.

ROOTE Reverse Geocode API

The Reverse Geocode API from ROOTE — 1 operation(s) for reverse geocode.

ROOTE Ride Hailing API

The Ride Hailing API from ROOTE — 1 operation(s) for ride hailing.

ROOTE Services API

The Services API from ROOTE — 1 operation(s) for services.

ROOTE Transit API

The Transit API from ROOTE — 5 operation(s) for transit.

ROOTE Usage API

The Usage API from ROOTE — 1 operation(s) for usage.

Scroll for all 15

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

ROOTE MCP Server

Remote MCP server at mcp.roote.ai.

MCP SERVER

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

roote-find-nearby-transport-departures

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

ROOTE API Rules

15 rules · 10 errors 1 warnings 4 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Roote Openapi Overlay

0 actions · update

UNRECORDED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Roote Authentication

1 scheme

SECURITY

Roote Domain Security

TLSv1.3 · HSTS

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Roote Agentic Access

20 operations · 2 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

APIReference

APIReference

Documentation

Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgentSkill

LLMsTxt

MCPServer

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Spectral

Spectral

ErrorCatalog

ErrorCatalog

Conformance

Conformance

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

Company 1

The organization behind the API

Website

Website

Other 3

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: roote
name: ROOTE
description: ROOTE provides a French-language mobility platform that offers live mobility data, geocoding, nearby transport
  options, and urban services via a REST API. The service targets developers building AI agents, mobile apps, and location‑based
  products, delivering real‑time information on transport options, routes, and availability across multiple cities.
url: https://raw.githubusercontent.com/api-evangelist/roote/refs/heads/main/apis.yml
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-05 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-05'
modified: '2026-10-05'
tags:
- Mobility
- French
- Artificial Intelligence
- Transportation
tags_raw:
- Mobility
- API
- French
- AI
- Transportation
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/roote-capability-edges.yml
  name: ROOTE Business Capability Map
- type: AgenticAccess
  url: agentic-access/roote-agentic-access.yml
- type: Spectral
  url: rules/roote-rules.yml
- type: AgentSkill
  url: skills/_index.yml
- type: ChangeLog
  url: changelog/roote-changelog.yml
- type: Authentication
  url: authentication/roote-authentication.yml
- type: ErrorCatalog
  url: errors/roote-problem-types.yml
- type: Conformance
  url: conformance/roote-conformance.yml
- type: LLMsTxt
  url: llms/roote-llms.txt
- type: MCPServer
  url: mcp/roote-mcp.yml
- type: Hosts
  url: hosts/roote-hosts.yml
- type: Vendors
  url: vendors/roote-vendors.yml
- type: DeveloperPortal
  url: https://doc.roote.ai\\\
- type: APIReference
  url: https://doc.roote.ai/resources/changelog
- type: DomainSecurity
  url: security/roote-domain-security.yml
- type: Website
  url: https://roote.ai
- type: Documentation
  url: https://doc.roote.ai
- type: GettingStarted
  url: https://doc.roote.ai/getting-started
apis:
- aid: roote:roote-capabilities-api
  name: ROOTE Capabilities API
  description: The Capabilities API from ROOTE — 1 operation(s) for capabilities.
  humanURL: https://doc.roote.ai
  baseURL: https://api.roote.ai
  tags:
  - Capabilities
  properties:
  - type: OpenAPI
    url: openapi/roote-capabilities-api-openapi.yml
- aid: roote:roote-changelog-json-api
  name: ROOTE Changelog.json API
  description: The Changelog.json API from ROOTE — 1 operation(s) for changelog.json.
  humanURL: https://doc.roote.ai
  baseURL: https://api.roote.ai
  tags:
  - Changelog.json
  properties:
  - type: OpenAPI
    url: openapi/roote-changelog-json-api-openapi.yml
- aid: roote:roote-charging-api
  name: ROOTE Charging API
  description: The Charging API from ROOTE — 1 operation(s) for charging.
  humanURL: https://doc.roote.ai
  baseURL: https://api.roote.ai
  tags:
  - Charging
  properties:
  - type: OpenAPI
    url: openapi/roote-charging-api-openapi.yml
- aid: roote:roote-geocode-api
  name: ROOTE Geocode API
  description: The Geocode API from ROOTE — 1 operation(s) for geocode.
  humanURL: https://doc.roote.ai
  baseURL: https://api.roote.ai
  tags:
  - Geocode
  properties:
  - type: OpenAPI
    url: openapi/roote-geocode-api-openapi.yml
- aid: roote:roote-health-api
  name: ROOTE Health API
  description: The Health API from ROOTE — 1 operation(s) for health.
  humanURL: https://doc.roote.ai
  baseURL: https://api.roote.ai
  tags:
  - Health
  properties:
  - type: OpenAPI
    url: openapi/roote-health-api-openapi.yml
- aid: roote:roote-mobility-api
  name: ROOTE Mobility API
  description: The Mobility API from ROOTE — 1 operation(s) for mobility.
  humanURL: https://doc.roote.ai
  baseURL: https://api.roote.ai
  tags:
  - Mobility
  properties:
  - type: OpenAPI
    url: openapi/roote-mobility-api-openapi.yml
- aid: roote:roote-nearby-api
  name: ROOTE Nearby API
  description: The Nearby API from ROOTE — 1 operation(s) for nearby.
  humanURL: https://doc.roote.ai
  baseURL: https://api.roote.ai
  tags:
  - Nearby
  properties:
  - type: OpenAPI
    url: openapi/roote-nearby-api-openapi.yml
- aid: roote:roote-openapi-json-api
  name: ROOTE Openapi.json API
  description: The Openapi.json API from ROOTE — 1 operation(s) for openapi.json.
  humanURL: https://doc.roote.ai
  baseURL: https://api.roote.ai
  tags:
  - Openapi.json
  properties:
  - type: OpenAPI
    url: openapi/roote-openapi-json-api-openapi.yml
- aid: roote:roote-parking-api
  name: ROOTE Parking API
  description: The Parking API from ROOTE — 1 operation(s) for parking.
  humanURL: https://doc.roote.ai
  baseURL: https://api.roote.ai
  tags:
  - Parking
  properties:
  - type: OpenAPI
    url: openapi/roote-parking-api-openapi.yml
- aid: roote:roote-place-search-api
  name: ROOTE Place Search API
  description: The Place Search API from ROOTE — 1 operation(s) for place search.
  humanURL: https://doc.roote.ai
  baseURL: https://api.roote.ai
  tags:
  - Place Search
  properties:
  - type: OpenAPI
    url: openapi/roote-place-search-api-openapi.yml
- aid: roote:roote-reverse-geocode-api
  name: ROOTE Reverse Geocode API
  description: The Reverse Geocode API from ROOTE — 1 operation(s) for reverse geocode.
  humanURL: https://doc.roote.ai
  baseURL: https://api.roote.ai
  tags:
  - Reverse Geocode
  properties:
  - type: OpenAPI
    url: openapi/roote-reverse-geocode-api-openapi.yml
- aid: roote:roote-ride-hailing-api
  name: ROOTE Ride Hailing API
  description: The Ride Hailing API from ROOTE — 1 operation(s) for ride hailing.
  humanURL: https://doc.roote.ai
  baseURL: https://api.roote.ai
  tags:
  - Ride Hailing
  properties:
  - type: OpenAPI
    url: openapi/roote-ride-hailing-api-openapi.yml
- aid: roote:roote-services-api
  name: ROOTE Services API
  description: The Services API from ROOTE — 1 operation(s) for services.
  humanURL: https://doc.roote.ai
  baseURL: https://api.roote.ai
  tags:
  - Services
  properties:
  - type: OpenAPI
    url: openapi/roote-services-api-openapi.yml
- aid: roote:roote-transit-api
  name: ROOTE Transit API
  description: The Transit API from ROOTE — 5 operation(s) for transit.
  humanURL: https://doc.roote.ai
  baseURL: https://api.roote.ai
  tags:
  - Transit
  properties:
  - type: OpenAPI
    url: openapi/roote-transit-api-openapi.yml
- aid: roote:roote-usage-api
  name: ROOTE Usage API
  description: The Usage API from ROOTE — 1 operation(s) for usage.
  humanURL: https://doc.roote.ai
  baseURL: https://api.roote.ai
  tags:
  - Usage
  properties:
  - type: OpenAPI
    url: openapi/roote-usage-api-openapi.yml
x-submission-notes: French-language marketing site; slug 'roote' (not a common word).
x-submission-probe: api.roote.ai/openapi.json 200 (OAS 3.1, 19 paths incl. /v1/nearby); /health 200 JSON ok; invented API
  path 404 JSON NOT_FOUND; doc.roote.ai 200; roote.ai root is an SPA (soft-200 on invented path).
x-submitted-by: contact@roote.ai (apis.io/add, 2026-10-04T06:34:24.078Z)
x-enrichment:
  date: '2026-10-05'
  status: enriched
  artifacts_added: 19
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

ROOTE API — frequently asked questions

Does ROOTE have an API?

Yes. APIs.io lists 15 APIs from ROOTE, including ROOTE Capabilities API, ROOTE Changelog.json API and ROOTE Charging API, and 12 more.

Is there an OpenAPI specification for the ROOTE API?

Yes. APIs.io indexes 15 OpenAPI specifications for ROOTE, each linked for download from this page.

How do I authenticate with the ROOTE API?

ROOTE uses bearer-token authentication (1 scheme). The details are profiled on APIs.io as Roote Authentication.

Does ROOTE have an MCP server?

Yes. APIs.io lists 1 MCP server for ROOTE: Remote MCP server at mcp.roote.ai.

Is the ROOTE API ready for AI agents?

ROOTE has a Kin Score of 31.9 out of 100 (thin) and an Agent Readiness score of 24.9 (agent-aware), scored by API Evangelist on 2026-10-31.

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/roote"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/roote/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/roote/evidence"

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.