Applied EV
Applied EV (formerly AEV Robotics, legal entity Applied Electric Vehicles Ltd) is an Australian software-defined vehicle company founded in Melbourne in 2015 by Julian Broadbent and Shane Ambry. It builds the Blanc Robot, a cabinless autonomous-ready electric platform for logistics, industrial, mining and agricultural transport; the Digital Backbone, a safety-rated ASIL-D programmable vehicle control system; and an Internet-of-Vehicles (IoV) Cloud Platform the company markets as API-first. The IoV platform is advertised as a set of vehicle APIs — Access Manager for identity and access management, a Vehicle Task API, a Vehicle Mission API, a Drive API for autonomous driving and motion control, a Pod and Accessory API, and Virtual Vehicles for simulation — together with a Vehicle Management System for fleet telemetry, diagnostics, mapping, mission creation and over-the-air software updates. No public developer portal, API reference or machine-readable contract is served: the developer host resolves but refuses public connections, and the marketing pages route every developer path to an enquiry form.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Applied EV 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 — Applied EV scores 10.4/100 (minimal), with a separate agent-readiness read of 3/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.
Why this profile is thin
Applied EV markets six named IoV Cloud Platform vehicle APIs on https://www.appliedev.com/cloud but serves no public reference for any of them; its developer portal at developer.appliedev.com and its identity host sso.appliedev.com exist in Certificate Transparency and resolve in DNS to 3.105.246.26, yet both origins silently drop public TCP connections on 443 and 80, so the contract is reachable only from a customer tenant or an allowlisted network.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Applied EV's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://www.appliedev.com/cloud→ HTTP 200https://www.appliedev.com/openapi.json→ HTTP 404https://www.appliedev.com/.well-known/api-catalog→ HTTP 404https://www.appliedev.com/llms.txt→ HTTP 404
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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-17 · rubric v0.24.0
Put this on your own site. The badge is drawn live from Applied EV's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aevrobotics/"
title="Applied EV on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aevrobotics.svg"
alt="Applied EV Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/aevrobotics/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/aevrobotics/"
title="Applied EV on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/aevrobotics/card.svg"
alt="Applied EV Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Applied EV
Each block below is one kind of artifact we hold for Applied EV. 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.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Aevrobotics Rate Limits
RATE LIMITSSecurity Posture 1
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.
Resources
Every other property we hold for Applied EV — 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 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/aevrobotics · machine-readable index on apis.io
This is an independent, third-party profile of Applied EV, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.