Public data layer · edition 2026-09-04

Use the graph,
not a black box.

BTU Graph publishes the directory behind its pages in formats built for analysts, developers, search engines, and research agents. No account or API key is required.

66 companies13 sectors209 cited claims86 canonical capabilitiesv4 graph schema

Graph contract

Readable relationships,
visible provenance.

Each graph node has a stable typed identifier. Each edge states a named relationship. Company and product records carry public sources and review dates; editorial classifications are labeled as BTU Graph analysis.

{"from": "company:cheniere-energy","to": "sector:lng","relationship": "has_primary_sector"}

Canonical pages as Markdown

Every canonical page also has a compact, citation-ready representation. Request the normal page URL with Accept: text/markdown; browsers still receive HTML, while agents receive frontmatter, the editorial body, and preserved JSON-LD.

curl https://btugraph.com/companies/ambyint/ \\ -H 'Accept: text/markdown'

Core entity types

company
A researched operating organization with a canonical profile and evidence ledger.
sector
An editorial grouping based on the company's role in the energy system.
capability
A stable canonical function with a preferred label, parent group, definition, and registered evidence-derived aliases.
workflow
A decision process connecting software, data requirements, and an outcome.
software_product
A specialist product with a separate evidence-backed profile.
market_data_requirement
A market input that informs a documented energy workflow.

Use and attribution

Open for research. Honest about boundaries.

BTU Graph-authored directory metadata, descriptions, and relationship classifications are available under the Creative Commons Attribution 4.0 International license. Attribute “BTU Graph” and link to the relevant canonical profile or this dataset page.

The license does not grant rights to company names, trademarks, logos, source publications, or facts and materials owned by third parties. Follow each evidence link and its publisher's terms when using underlying source material.

Do not use inclusion to imply a customer, partner, endorsement, certification, or commercial relationship. Review dates describe when our researchers checked the evidence, not a guarantee that a changing fact remains current.

Corrections and responsible use

Found a stale relationship or factual error? Use the structured corrections desk with the profile URL, exact correction, and a public supporting source. Read the editorial methodology for the full inclusion and correction policy.

Schema additions remain backward compatible within an edition. Breaking field or relationship changes increment schemaVersion and appear in the public changelog.