Evie Networks

Evie Networks is an Australian electric-vehicle charging infrastructure company, founded in 2017 and backed by the St Baker Energy Innovation Fund, that owns and operates one of the country's largest DC fast and ultrafast public charging networks across 300+ locations in every state and territory. It sits downstream of the electricity retail market as a charge point operator (CPO) and e-mobility service provider, buying energy and reselling it as charging sessions to drivers and fleets, and it also builds and operates charging assets for site hosts, councils, dealerships and commercial property owners. Its API posture is closed: as of 2026-07-27 there is no developer portal, no published API documentation, no OpenAPI or other machine-readable contract, and no named support for the EV charging interoperability standards (OCPP, OCPI, ISO 15118). Evie is not a designated data holder under Australia's Consumer Data Right energy regime — the CDR Register's public energy data-holder brand summary lists 84 brands and Evie is not among them — so the statutory data mandate that produced identical APIs across Australian banks and energy retailers does not reach the EV charging layer at all. A live production API host exists at api.goevie.com.au serving the Evie Charging mobile app, but it is undocumented, unadvertised and returns a Google Cloud Endpoints 404 to anonymous callers. Neither consumer charging-session data nor network/market data is published through any documented public interface; charger location data reaches developers only through third-party aggregators.

Evie Networks is profiled on the APIs.io network. Tagged areas include Energy, Australia, EV Charging, Electricity, and Utilities.

Evie Networks’ developer surface includes engineering blog, support, FAQ, and 13 more developer resources.

🌐 Visit website 📡 Source on GitHub

12.7/100 emerging ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0

0 APIs

EnergyAustraliaEV ChargingElectricityUtilitiesE-MobilityCharging InfrastructureFleetTransport Electrification

Kin Score

Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0

Composite quality — 12.7/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 1.2 / 17

Access Clarity 3.6 / 17

Operational Transparency 0.3 / 11

Contract Governance 0.0 / 10

Discoverability 4.9 / 9

Regulatory Posture 3.9 / 15

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities 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.

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/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/evie-networks: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

Support

Support

FAQ

FAQ

ContactUs

ContactUs

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 6

The organization behind the API

Website

About

Blog

BlogRSS

Careers

LinkedIn

Other 1

Properties that don't map to a standard resource type

Team

Team

Source (apis.yml)

aid: evie-networks
url: https://raw.githubusercontent.com/api-evangelist/evie-networks/refs/heads/main/apis.yml
name: Evie Networks
kind: company
description: 'Evie Networks is an Australian electric-vehicle charging infrastructure company, founded in 2017 and backed
  by the St Baker Energy Innovation Fund, that owns and operates one of the country''s largest DC fast and ultrafast public
  charging networks across 300+ locations in every state and territory. It sits downstream of the electricity retail market
  as a charge point operator (CPO) and e-mobility service provider, buying energy and reselling it as charging sessions to
  drivers and fleets, and it also builds and operates charging assets for site hosts, councils, dealerships and commercial
  property owners. Its API posture is closed: as of 2026-07-27 there is no developer portal, no published API documentation,
  no OpenAPI or other machine-readable contract, and no named support for the EV charging interoperability standards (OCPP,
  OCPI, ISO 15118). Evie is not a designated data holder under Australia''s Consumer Data Right energy regime — the CDR Register''s
  public energy data-holder brand summary lists 84 brands and Evie is not among them — so the statutory data mandate that
  produced identical APIs across Australian banks and energy retailers does not reach the EV charging layer at all. A live
  production API host exists at api.goevie.com.au serving the Evie Charging mobile app, but it is undocumented, unadvertised
  and returns a Google Cloud Endpoints 404 to anonymous callers. Neither consumer charging-session data nor network/market
  data is published through any documented public interface; charger location data reaches developers only through third-party
  aggregators.'
image: https://evie.com.au/wp-content/uploads/2023/07/evie-favicon-300x300.png
tags:
- Energy
- Australia
- EV Charging
- Electricity
- Utilities
- E-Mobility
- Charging Infrastructure
- Fleet
- Transport Electrification
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
apis: []
common:
- type: DomainSecurity
  url: security/evie-networks-domain-security.yml
- type: Website
  url: https://evie.com.au/
- type: About
  url: https://evie.com.au/about-evie/
- type: Blog
  url: https://evie.com.au/blog/
- type: BlogRSS
  url: https://evie.com.au/feed/
- type: Support
  url: https://evie.com.au/help-center/
- type: FAQ
  url: https://evie.com.au/frequently-asked-questions/
- type: ContactUs
  url: https://evie.com.au/contact-us/
- type: Careers
  url: https://evie.com.au/about-evie/careers/
- type: Team
  url: https://evie.com.au/about-evie/our-team/
- type: LLMsTxt
  url: llms/evie-networks-llms.txt
- type: Conformance
  url: conformance/evie-networks-conformance.yml
- type: PrivacyPolicy
  url: https://evie.com.au/privacy-policy/
- type: TermsOfService
  url: https://evie.com.au/terms-of-service/
- type: LinkedIn
  url: https://au.linkedin.com/company/evie-networks
- type: GitHubOrganization
  url: https://github.com/goevie
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com