Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

AMEE

AMEE (Avoiding Mass Extinctions Engine, also styled Avoidance of Mass Extinctions Engine) was a London-based environmental-intelligence company founded around 2005 by Gavin Starks out of UK firm Dgen. It ran an open web-service API and cloud database that standardized carbon-emissions and energy-consumption data across 150+ countries, letting applications apply government emission factors to tracked activities. AMEE powered carbon calculators and footprinting for clients including Google, Morgan Stanley, Radiohead, Sun Microsystems, and UK and Irish government programs (notably the Act on CO2 campaign). It raised roughly $7.5M from Union Square Ventures, OATV (O'Reilly AlphaTech Ventures), The Accelerator Group, and Amadeus Capital Partners. AMEE was acquired by Pi (PredictX) in late 2015 / early 2016 and no longer operates as an independent company; the amee.com domain currently returns HTTP 502 with no live API or developer surface.

human only

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.

Kin Score

AMEE is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.

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 — AMEE scores 5.7/100 (minimal), 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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 5.7/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.0 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Regulatory · Government & Public Sector 0.0 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
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

Resources

Every other property we hold for AMEE — 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.

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

AMEE is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.

← All providers · Data indexed from github.com/api-evangelist/amee · machine-readable index on apis.io