Ridecell
Ridecell is an AI-powered asset intelligence and orchestration platform for automotive leasing, fleet, and finance companies. Its five intelligence modules (Client, Spend, Supplier, Asset, and Operational Intelligence) and the "Maya" AI agent monitor fleets, flag invoice overcharges, track garage/supplier performance, optimize vehicle remarketing and residual value, and resolve idle-vehicle inefficiencies. The platform processes 12M+ events daily across 500K+ assets, 100+ connected systems, and 14+ countries. It was surfaced as a portfolio company of Initialized Capital. Ridecell does not currently publish a public developer API, OpenAPI specification, or SDK; this profile captures its public information, security, and compliance surfaces.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Ridecell the way a machine reads it — 3 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Ridecell scores 16.6/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Ridecell
Each block below is one kind of artifact we hold for Ridecell. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Ridecell Trust Center
AICPA SOC for Service Organizations, IBM Cloud for Financial Services Validated
SECURITYResources
Every other property we hold for Ridecell — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/ridecell · machine-readable index on apis.io