ROOTE website screenshot

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.

31.1/100 thin ▬ flat Agent 27/100 agent aware Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →
1 published contract 1 MCP Servers 1 Agent Skills
MobilityFrenchArtificial IntelligenceTransportation

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 Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0
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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for ROOTE 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):
6 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
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.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
Ask about:
Roote · a person reads this and replies by email.
or email info@apis.io
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 →

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (documented)
measured — observed by APIs.io (published)

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.

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

ROOTE API Rules

15 rules · 10 error-severity 1 warn-severity 4 info-severity

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 (API Evangelist recommendations) 1

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

ROOTE Agentic Access

20 operations · 1 acting

20 operations · 1 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Company 1

The organization behind the API

Other 3

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
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)
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-13'
  method: derived
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-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.1 out of 100 (thin) and an Agent Readiness score of 27.4 (agent-aware), scored by API Evangelist on 2026-11-13.

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"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

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