The EnergyzedWorld API
Every article on this site is available as JSON and as raw markdown, described by an OpenAPI 3.1 specification. No key, no rate limit, no sign-up. Built so an AI agent can read and cite this work without scraping it.
Start here
Three files describe everything.
OpenAPI specification
/openapi.json — OpenAPI 3.1, with a unique operationId,
description and typed response schema on every operation. Converts directly into
LLM function-calling definitions.
Agent instructions
/agents.md — when to use this source, when not to, how to
call it, and when to hand an enquiry to a human.
llms.txt
/llms.txt — condensed site summary. The full corpus is at
/llms-full.txt.
Endpoints
All GET. All CORS-open. All static files on a CDN.
| Path | operationId | Returns |
|---|---|---|
GET /api/index.json | getApiIndex | Every endpoint, response convention and contact route. |
GET /openapi.json | — | OpenAPI 3.1 specification. Mirrored at /api/openapi.json. |
GET /api/posts.json | listPosts | Every published article, newest first. |
GET /api/posts/{bucket}/{slug}.json | getPost | One article, including its full markdown body. |
GET /api/buckets.json | listBuckets | The content categories and their post counts. |
GET /api/site.json | getSite | Publisher, services, offices and contact routes. |
GET /{bucket}/{slug}.md | getPostMarkdown | One article as raw markdown. |
Categories (bucket): ai-energy, bps, heat-pumps, solar, monitoring, financing, selling-energy, energy-posts
Try it
Nothing to configure.
# What is here? curl -s https://energyzedworld.com/api/index.json # Every article, newest first curl -s https://energyzedworld.com/api/posts.json # One article, with its full markdown body curl -s https://energyzedworld.com/api/posts/monitoring/what-is-a-data-acquisition-system.json # The same article as plain markdown — smaller, no page chrome curl -s https://energyzedworld.com/monitoring/what-is-a-data-acquisition-system.md # Who publishes this, what they do, and how to reach them curl -s https://energyzedworld.com/api/site.json
Markdown variants
Append .md to any article URL.
Each article has a raw-markdown twin at its own stable URL — title, description, source
links, TL;DR, body and FAQ, with no navigation chrome. It is advertised from the article
page as <link rel="alternate" type="text/markdown">, listed in
llms.txt, and described in the OpenAPI spec as
getPostMarkdown.
Content negotiation on Accept: text/markdown is
not supported, and the Vary header cannot be set:
this site is a static build on DigitalOcean App Platform, which does not allow custom
response headers on static-site components. The .md URL is the
supported way to get markdown. See Known limitations below.
Known limitations
Stated plainly, so you do not have to discover them.
No Accept negotiation
Static hosting cannot vary a response on a request header. Use the
.md URL for markdown and the
.json URL for JSON.
Errors are HTML, not JSON
A request to an unbuilt path returns the site's HTML 404 document with a real 404
status. The documented JSON error envelope is served as an example at
/api/errors/not-found.json and described in the spec.
No MCP server yet
An MCP server needs a running process, which this static site does not have. If you want one, say so — tell us what you would call and it moves up the list.
Read-only
There are no write operations, no authentication and no rate limit. If you need volume beyond ordinary crawling, get in touch first.
Using this in a real project?
The people who write these articles do the work too.
Eenovators Limited is a Pure ESCO working across Kenya, Uganda, Tanzania, United States, Colorado — energy audits, monitoring deployments, measurement and verification, Building Performance Standards compliance, and metering hardware procurement. If you are building something on this data, or you have a site, a bill or a project behind the question, we would rather hear from you than not.