FLO is a Quebec City headquartered electric vehicle charging company, founded in 2009 as AddEnergie (addenergie.com now redirects to flo.com), that designs and manufactures its own Level 2 and DC fast charging hardware and operates one of the largest public charging networks in North America. FLO sits on the demand side of the electricity value chain rather than inside the regulated utility layer: it is a charge point operator and e-mobility service provider, not a distributor, transmitter or retailer, so Canada's energy-data obligations do not reach it. Ontario's Green Button regulation binds Ontario electricity and natural gas utilities, and Australia's Consumer Data Right for energy is a different jurisdiction entirely; neither applies to FLO, and FLO publishes no consumer energy data API of any kind. Its API posture is closed and partner-mediated. flo.com has no developer subdomain and no published API reference: developer.flo.com, developers.flo.com, api.flo.com, docs.flo.com and data.flo.com all fail to resolve, and /developers, /api, /openapi.json, /swagger.json and /api-docs all return 404. FLO does name real interoperability standards on its own pages - OCPP 1.6J on the station-to-network side, OCPI for roaming with partner networks, and OpenADR 2.0 alongside "FLO's flexible API" for utility demand response and smart grid integration - but each of those is reached through a commercial agreement rather than a signup form. Customer charging and session data is reachable only by the account holder through the account.flo.com login, and FLO publishes no open market, grid or station-location data feed under its own name. A second enrichment round in July 2026 did find live machine-readable surfaces on flo.com hosts, but all of them are platform-provided rather than FLO-authored: a Shopify storefront MCP server with five tools at store.flo.com/api/mcp plus public products.json and collections.json feeds, RFC 8414/9728 and OIDC discovery documents on store.flo.com, Salesforce Experience Cloud OIDC discovery on network.flo.com, and a Vanta trust center at trust.flo.com carrying FLO's SOC 2 Type 2. FLO also runs real but entirely private API infrastructure - auth.flo.com is an AWS API Gateway that answers every path with 403 Missing Authentication Token, alongside csnms.flo.com and an EMS host - so the charging network itself remains closed.
FLO publishes 1 API on the APIs.io network. Tagged areas include Energy, Canada, EV Charging, Electricity, and Grid.
FLO’s developer surface includes authentication, engineering blog, support, documentation, and 26 more developer resources.
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/.
The only live, anonymously callable machine-readable surface in FLO's estate. FLO's hardware and accessories store runs on Shopify, and that platform serves a Model Context Prot...
aid: flo-ev
url: https://raw.githubusercontent.com/api-evangelist/flo-ev/refs/heads/main/apis.yml
name: FLO
kind: company
description: 'FLO is a Quebec City headquartered electric vehicle charging company, founded in 2009 as AddEnergie (addenergie.com
now redirects to flo.com), that designs and manufactures its own Level 2 and DC fast charging hardware and operates one
of the largest public charging networks in North America. FLO sits on the demand side of the electricity value chain rather
than inside the regulated utility layer: it is a charge point operator and e-mobility service provider, not a distributor,
transmitter or retailer, so Canada''s energy-data obligations do not reach it. Ontario''s Green Button regulation binds
Ontario electricity and natural gas utilities, and Australia''s Consumer Data Right for energy is a different jurisdiction
entirely; neither applies to FLO, and FLO publishes no consumer energy data API of any kind. Its API posture is closed and
partner-mediated. flo.com has no developer subdomain and no published API reference: developer.flo.com, developers.flo.com,
api.flo.com, docs.flo.com and data.flo.com all fail to resolve, and /developers, /api, /openapi.json, /swagger.json and
/api-docs all return 404. FLO does name real interoperability standards on its own pages - OCPP 1.6J on the station-to-network
side, OCPI for roaming with partner networks, and OpenADR 2.0 alongside "FLO''s flexible API" for utility demand response
and smart grid integration - but each of those is reached through a commercial agreement rather than a signup form. Customer
charging and session data is reachable only by the account holder through the account.flo.com login, and FLO publishes no
open market, grid or station-location data feed under its own name. A second enrichment round in July 2026 did find live
machine-readable surfaces on flo.com hosts, but all of them are platform-provided rather than FLO-authored: a Shopify storefront
MCP server with five tools at store.flo.com/api/mcp plus public products.json and collections.json feeds, RFC 8414/9728
and OIDC discovery documents on store.flo.com, Salesforce Experience Cloud OIDC discovery on network.flo.com, and a Vanta
trust center at trust.flo.com carrying FLO''s SOC 2 Type 2. FLO also runs real but entirely private API infrastructure -
auth.flo.com is an AWS API Gateway that answers every path with 403 Missing Authentication Token, alongside csnms.flo.com
and an EMS host - so the charging network itself remains closed.'
accessModel:
pricing: unknown
onboarding: partner-only
trial: false
try_now: false
public: false
label: No public developer program - partner/commercial integration only
confidence: high
source:
- website
generated: '2026-07-27'
method: manual
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/flo-ev.png
tags:
- Energy
- Canada
- EV Charging
- Electricity
- Grid
- Demand Response
- Interoperability
- OCPP
- OCPI
- OpenADR
- Charge Point Operator
- Quebec
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
apis:
- name: FLO Store (Shopify Storefront MCP)
description: 'The only live, anonymously callable machine-readable surface in FLO''s estate. FLO''s hardware and accessories
store runs on Shopify, and that platform serves a Model Context Protocol server at https://store.flo.com/api/mcp - protocol
version 2025-06-18, serverInfo "storefront-renderer" 0.1.0 - exposing five tools over FLO''s own product catalogue, store
policies and cart/checkout flow, plus public JSON product and collection feeds. It is platform-provided rather than FLO-authored,
and it is commerce only: it says nothing about charging sessions, station telemetry, roaming (OCPI) or demand response
(OpenADR), all of which remain partner-mediated with no published contract.'
humanURL: https://store.flo.com/
baseURL: https://store.flo.com
tags:
- MCP
- Commerce
- EV Charging
- Agents
properties:
- type: MCPServer
url: mcp/flo-ev-mcp.yml
name: FLO Store MCP server
- type: AgentSkill
url: skills/flo-ev-shop-flo-store.md
name: Shop the FLO store with MCP
- type: WellKnown
url: well-known/flo-ev-well-known.yml
- type: Authentication
url: authentication/flo-ev-authentication.yml
- type: OAuthScopes
url: scopes/flo-ev-scopes.yml
- type: ErrorCatalog
url: errors/flo-ev-problem-types.yml
common:
- type: DomainSecurity
url: security/flo-ev-domain-security.yml
- type: MCPServer
url: mcp/flo-ev-mcp.yml
name: FLO Store MCP server
description: Live Shopify storefront MCP server on store.flo.com - 5 tools, anonymous tools/list.
- type: AgentSkill
url: skills/_index.yml
name: Agent skills
- type: WellKnown
url: well-known/flo-ev-well-known.yml
name: Well-known discovery index
- type: Authentication
url: authentication/flo-ev-authentication.yml
- type: OAuthScopes
url: scopes/flo-ev-scopes.yml
- type: ErrorCatalog
url: errors/flo-ev-problem-types.yml
- type: Conformance
url: conformance/flo-ev-conformance.yml
- type: Compliance
url: https://trust.flo.com/
name: FLO Trust Center
description: SOC 2 Type 2 (BARR Advisory, announced 2024-10-22); Vanta-hosted.
- type: TrustCenter
url: security/flo-ev-trust-center.yml
- type: Lifecycle
url: lifecycle/flo-ev-lifecycle.yml
- type: LLMsTxt
url: llms/flo-ev-llms.txt
- type: HelpCenter
url: https://helpdesk.flo.com/support/home
name: FLO Help Desk
- type: Store
url: https://store.flo.com/
name: FLO Store
- type: Website
url: https://www.flo.com/
- type: Blog
url: https://www.flo.com/ev-charging-insights/
- type: BlogRSS
url: https://www.flo.com/feed/
- type: PressRoom
url: https://www.flo.com/news-press/
- type: MediaRoom
url: https://www.flo.com/media-room/
- type: Support
url: https://www.flo.com/support/
- type: Documentation
url: https://www.flo.com/business/product-documentation/
name: Product Documentation
description: Hardware spec sheets, installation guides and user guides. Product literature only - no API reference is published.
- type: Login
url: https://account.flo.com/
name: FLO Account
description: Customer/station-owner login. Not a developer portal; no self-serve API key issuance is published.
- type: Partners
url: https://www.flo.com/company/partner-networks/
name: Partner Networks
description: Roaming partners (BC Hydro EV, ChargePoint, eCharge Network, Electric Circuit, Shell Recharge, SWTCH).
- type: Documentation
url: https://www.flo.com/insights/ev-charging-roaming/
name: EV Charging Roaming
description: FLO's own explainer naming the Open Charge Point Interface (OCPI) as the roaming communication protocol.
- type: Documentation
url: https://www.flo.com/business/utilities/
name: FLO for Utilities
description: States that FLO supports utility demand response and smart grid integration "Through OpenADR 2.0 or FLO's flexible
API". No endpoint, reference or onboarding path is published.
- type: PrivacyPolicy
url: https://www.flo.com/privacy-policy/
- type: TermsOfService
url: https://www.flo.com/terms-conditions/
- type: LinkedIn
url: https://www.linkedin.com/company/floevcharging/
- type: Twitter
url: https://twitter.com/FLOevcharging
- type: Patents
url: https://www.flo.com/patents/
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
Kin Score
How this is scored →