Hildebrand

Hildebrand Technology Limited is a London-based energy data company and, since 2019, the United Kingdom's first independent DCC Other User with a direct connection to the Smart Data Communications Company network. It sits between Britain's mandated smart-metering infrastructure and the applications built on top of it: it makes Glow hardware (CADs, in-home displays, sub-meters, temperature sensors), ingests and stores smart-meter reads at scale, and republishes them through the Glowmarkt Platform APIs, the consumer Bright app, and the commercial Glow Data Service. Its API posture is an honest reflection of the British market seam — Britain mandated the metering INFRASTRUCTURE, not a consumer data right, so there is no Consumer Data Right or Green Button obligation on Hildebrand and no standards-conformant data-sharing surface to point at. What exists instead is a proprietary but genuinely well-documented platform: five public Swagger 2.0 definitions are served anonymously from api.glowmarkt.com/api-docs, and any individual who installs Bright, creates an account and passes meter-point verification can call the same production API for their own household data with a published applicationId. Third-party organisational access to other people's data is the closed half — it runs through Glow Data Service on a signed contract from GBP 595/month per MPxN, with consumer verification and consent captured per meter point. Hildebrand publishes no open grid or market data of any kind: every documented endpoint returns HTTP 400 without an applicationId header, so this is a closed-market-data, consent-gated-consumer-data provider.

Hildebrand publishes 22 APIs on the APIs.io network, including Account API, Account Profile API, Account Session API, and 19 more. Tagged areas include Energy, United Kingdom, Utilities, Electricity, and Gas.

The Hildebrand catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Hildebrand’s developer surface includes getting-started guide, engineering blog, authentication, documentation, API reference, signup flow, pricing, and 27 more developer resources.

🌐 Visit website 📡 Source on GitHub

54.1/100 developing ▬ flat Agent 31/100 agent ready saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

AccessPaid

5 APIs

Energy United Kingdom Utilities Electricity Gas Smart Metering Energy Data Demand Response IoT Metering

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 54.1/100 · developing

Contract Quality 11.4 / 19

Developer Ergonomics 7.4 / 15

Access Clarity 10.3 / 15

Operational Transparency 1.0 / 10

Contract Governance 1.6 / 9

Discoverability 5.6 / 8

Regulatory Posture 7.9 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 31/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

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.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% 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/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/hildebrand: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 22

Individual APIs this provider publishes, each with its own machine-readable definition.

Hildebrand Account API

The Account API from Hildebrand — 8 operation(s) for account.

Hildebrand Account Profile API

The Account Profile API from Hildebrand — 2 operation(s) for account profile.

Hildebrand Account Session API

The Account Session API from Hildebrand — 1 operation(s) for account session.

Hildebrand Accountsession API

The accountsession API from Hildebrand — 1 operation(s) for accountsession.

Hildebrand Alert API

An application can send an alert to a customer across multiple channels (email, push, inbox) which will convey some type of specific message (defined by the alert type).

Hildebrand Alerttype API

The definition of an alert, what functionality the alert represents. It is an identifier which amongst other elements will point us to the correct template. An alert type belong...

Hildebrand Auth API

The Auth API from Hildebrand — 5 operation(s) for auth.

Hildebrand Device API

The Device API from Hildebrand — 5 operation(s) for device.

Hildebrand Device Meter Point DCC inventory API

The Device Meter Point DCC inventory API from Hildebrand — 3 operation(s) for device meter point dcc inventory.

Hildebrand Device Type API

The DeviceType API from Hildebrand — 2 operation(s) for devicetype.

Hildebrand Discover API

The discover API from Hildebrand — 1 operation(s) for discover.

Hildebrand Meter Point Consent & Verification API

The Meter Point Consent & Verification API from Hildebrand — 5 operation(s) for meter point consent & verification.

Hildebrand Notification API

When an application triggeers an alert, for each channel of communication a notification is created. This enables the system to monitor seperately whant happens in each channel.

Hildebrand O Auth API

The OAuth API from Hildebrand — 2 operation(s) for oauth.

Hildebrand Resource API

A Resource is a representation of data collected from a physical device, like sensor readings, or changes in an actuating device state etc.

Hildebrand Resource Type API

A Resource Type defines the storage structure of the resources supported by the Glow Platform.

Hildebrand Template API

The template of the message that is being sent; it can be passed through as HTML or JSON. Each template has an alert type, is specific to a single channel of communication and a...

Hildebrand User API

The User API from Hildebrand — 6 operation(s) for user.

Hildebrand Virtual Entity API

A Virtual Entity is an instance of the Virtual Entity Type and is tied to an owner as well as an applicationId. In order to create a Virtual Entity a user must have all the requ...

Hildebrand Virtual Entity's Metadata API

A Virtual Entity's metadata can be used to save information that will facilitate the virtual representation of the entity. This is typically attribute data that does not change ...

Hildebrand Virtual Entity Statistics API

APIs that return an overview of the Virtual Entities an application has (administrative API).

Hildebrand Virtual Entity Type API

Entity that belongs and is managed by an application and contains the definition and combination of the Resource Types that are required to create a Virtual Entity.

Scroll for all 22

Open Collections 5

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Device Management System

OPEN COLLECTION

Notification System

OPEN COLLECTION

Resource System

OPEN COLLECTION

Glowmarkt User System

OPEN COLLECTION

Virtual Entity System

OPEN COLLECTION

Pricing Plans 1

Published pricing tiers and plan structures.

Hildebrand Plans

3 plans

PLANS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Hildebrand Event Surface

ASYNCAPI

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Hildebrand Authentication

apiKey/http · 5 schemes

SECURITY

Hildebrand Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Hildebrand Agentic Access

106 operations · 45 acting · 4 human-in-the-loop

106 operations · 45 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

LLMsTxt

AgentSkill

AgenticAccess

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conformance

Conventions

ErrorCatalog

Lifecycle

DataModel

Webhooks

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 3

Authentication, authorization, and security posture

Compliance

Compliance

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

Support

Support

Forum

Forum

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

Pricing

Pricing

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Blog

Blog

Website

Website

LinkedIn

Other 7

Properties that don't map to a standard resource type

CapabilityMap

Overlay

Overlay

Overlay

Overlay

Overlay

Review

Scroll for all 7

Source (apis.yml)

aid: hildebrand
url: https://raw.githubusercontent.com/api-evangelist/hildebrand/refs/heads/main/apis.yml
name: Hildebrand
kind: company
description: 'Hildebrand Technology Limited is a London-based energy data company and, since 2019, the United Kingdom''s first
  independent DCC Other User with a direct connection to the Smart Data Communications Company network. It sits between Britain''s
  mandated smart-metering infrastructure and the applications built on top of it: it makes Glow hardware (CADs, in-home displays,
  sub-meters, temperature sensors), ingests and stores smart-meter reads at scale, and republishes them through the Glowmarkt
  Platform APIs, the consumer Bright app, and the commercial Glow Data Service. Its API posture is an honest reflection of
  the British market seam — Britain mandated the metering INFRASTRUCTURE, not a consumer data right, so there is no Consumer
  Data Right or Green Button obligation on Hildebrand and no standards-conformant data-sharing surface to point at. What exists
  instead is a proprietary but genuinely well-documented platform: five public Swagger 2.0 definitions are served anonymously
  from api.glowmarkt.com/api-docs, and any individual who installs Bright, creates an account and passes meter-point verification
  can call the same production API for their own household data with a published applicationId. Third-party organisational
  access to other people''s data is the closed half — it runs through Glow Data Service on a signed contract from GBP 595/month
  per MPxN, with consumer verification and consent captured per meter point. Hildebrand publishes no open grid or market data
  of any kind: every documented endpoint returns HTTP 400 without an applicationId header, so this is a closed-market-data,
  consent-gated-consumer-data provider.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: request
  trial: false
  try_now: false
  public: false
  label: Paid · Contract required for organisational access; free self-serve for your own meter data via Bright
  confidence: high
  source:
  - https://data.glowforindustry.com/
  - https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  generated: '2026-07-27'
  method: manual
image: https://www.hildebrand.co.uk/images/favicon.ico
tags:
- Energy
- United Kingdom
- Utilities
- Electricity
- Gas
- Smart Metering
- Energy Data
- Demand Response
- IoT
- Metering
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
apis:
- aid: hildebrand:hildebrand-account-api
  name: Hildebrand Account API
  description: The Account API from Hildebrand — 8 operation(s) for account.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Account
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-account-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-account-profile-api
  name: Hildebrand Account Profile API
  description: The Account Profile API from Hildebrand — 2 operation(s) for account profile.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Account Profile
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-account-profile-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-account-session-api
  name: Hildebrand Account Session API
  description: The Account Session API from Hildebrand — 1 operation(s) for account session.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Account Session
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-account-session-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-accountsession-api
  name: Hildebrand Accountsession API
  description: The accountsession API from Hildebrand — 1 operation(s) for accountsession.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Account Session
  tags_raw:
  - accountsession
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-accountsession-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-alert-api
  name: Hildebrand Alert API
  description: An application can send an alert to a customer across multiple channels (email, push, inbox) which will convey
    some type of specific message (defined by the alert type).
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Alert
  tags_raw:
  - alert
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-alert-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-alerttype-api
  name: Hildebrand Alerttype API
  description: The definition of an alert, what functionality the alert represents. It is an identifier which amongst other
    elements will point us to the correct template. An alert type belongs to an application.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - alerttype
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-alerttype-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-auth-api
  name: Hildebrand Auth API
  description: The Auth API from Hildebrand — 5 operation(s) for auth.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Authentication
  tags_raw:
  - Auth
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-auth-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-device-api
  name: Hildebrand Device API
  description: The Device API from Hildebrand — 5 operation(s) for device.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Device
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-device-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-device-meter-point-dcc-inventory-api
  name: Hildebrand Device Meter Point DCC inventory API
  description: The Device Meter Point DCC inventory API from Hildebrand — 3 operation(s) for device meter point dcc inventory.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Device Meter Point DCC inventory
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-device-meter-point-dcc-inventory-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-devicetype-api
  name: Hildebrand Device Type API
  description: The DeviceType API from Hildebrand — 2 operation(s) for devicetype.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - DeviceType
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-devicetype-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-discover-api
  name: Hildebrand Discover API
  description: The discover API from Hildebrand — 1 operation(s) for discover.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Discover
  tags_raw:
  - discover
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-discover-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-meter-point-consent-verification-api
  name: Hildebrand Meter Point Consent & Verification API
  description: The Meter Point Consent & Verification API from Hildebrand — 5 operation(s) for meter point consent & verification.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Meter Point Consent & Verification
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-meter-point-consent-verification-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-notification-api
  name: Hildebrand Notification API
  description: When an application triggeers an alert, for each channel of communication a notification is created. This enables
    the system to monitor seperately whant happens in each channel.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Notification
  tags_raw:
  - notification
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-notification-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-oauth-api
  name: Hildebrand O Auth API
  description: The OAuth API from Hildebrand — 2 operation(s) for oauth.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Authentication
  tags_raw:
  - OAuth
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-oauth-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-resource-api
  name: Hildebrand Resource API
  description: A Resource is a representation of data collected from a physical device, like sensor readings, or changes in
    an actuating device state etc.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Resource
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-resource-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-resource-type-api
  name: Hildebrand Resource Type API
  description: A Resource Type defines the storage structure of the resources supported by the Glow Platform.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - ResourceType
  tags_raw:
  - Resource Type
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-resource-type-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-template-api
  name: Hildebrand Template API
  description: The template of the message that is being sent; it can be passed through as HTML or JSON. Each template has
    an alert type, is specific to a single channel of communication and a culrture code.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Template
  tags_raw:
  - template
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-template-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-user-api
  name: Hildebrand User API
  description: The User API from Hildebrand — 6 operation(s) for user.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - User
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-user-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-virtual-entity-api
  name: Hildebrand Virtual Entity API
  description: A Virtual Entity is an instance of the Virtual Entity Type and is tied to an owner as well as an applicationId.
    In order to create a Virtual Entity a user must have all the required resources.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Virtual Entity
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-virtual-entity-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-virtual-entity-s-metadata-api
  name: Hildebrand Virtual Entity's Metadata API
  description: A Virtual Entity's metadata can be used to save information that will facilitate the virtual representation
    of the entity. This is typically attribute data that does not change in time.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Virtual Entity's Metadata
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-virtual-entity-s-metadata-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-virtual-entity-statistics-api
  name: Hildebrand Virtual Entity Statistics API
  description: APIs that return an overview of the Virtual Entities an application has (administrative API).
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Virtual Entity Statistics
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-virtual-entity-statistics-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
- aid: hildebrand:hildebrand-virtual-entity-type-api
  name: Hildebrand Virtual Entity Type API
  description: Entity that belongs and is managed by an application and contains the definition and combination of the Resource
    Types that are required to create a Virtual Entity.
  humanURL: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  baseURL: https://api.glowmarkt.com/api/v0-1
  tags:
  - Virtual Entity Type
  properties:
  - type: OpenAPI
    url: openapi/hildebrand-virtual-entity-type-api-openapi.yml
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
  - type: Documentation
    url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/vesys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/dmssys/
  - type: APIReference
    url: https://api.glowmarkt.com/api-docs/v0-1/notificationsys/
common:
- type: CapabilityMap
  url: capabilities/hildebrand-capability-edges.yml
  name: Hildebrand Business Capability Map
- type: Overlay
  url: overlays/hildebrand-glowmarkt-user-system-overlay.yaml
- type: Overlay
  url: overlays/hildebrand-glowmarkt-resource-system-overlay.yaml
- type: Overlay
  url: overlays/hildebrand-glowmarkt-virtual-entity-system-overlay.yaml
- type: Overlay
  url: overlays/hildebrand-glowmarkt-device-management-system-overlay.yaml
- type: Overlay
  url: overlays/hildebrand-glowmarkt-notification-system-overlay.yaml
- type: GettingStarted
  url: https://docs.glowmarkt.com/GlowmarktAPIDataRetrievalDocumentationIndividualUserForBright.pdf
- type: Blog
  url: https://data.glowforindustry.com/articles
- type: GitHubOrganization
  url: https://github.com/HildebrandTechnology
- type: Compliance
  url: https://www.hildebrand.co.uk/about
- type: Conformance
  url: conformance/hildebrand-conformance.yml
- type: Conventions
  url: conventions/hildebrand-conventions.yml
- type: ErrorCatalog
  url: errors/hildebrand-problem-types.yml
- type: Lifecycle
  url: lifecycle/hildebrand-lifecycle.yml
- type: DataModel
  url: data-model/hildebrand-data-model.yml
- type: Packages
  url: packages/hildebrand-packages.yml
- type: Plans
  url: plans/hildebrand-plans.yml
- type: X-MCPServerCandidate
  url: mcp/hildebrand-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/hildebrand-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: Webhooks
  url: asyncapi/hildebrand-event-surface.yml
- type: AgenticAccess
  url: agentic-access/hildebrand-agentic-access.yml
- type: DomainSecurity
  url: security/hildebrand-domain-security.yml
- type: Authentication
  url: authentication/hildebrand-authentication.yml
- type: Website
  url: https://www.hildebrand.co.uk/
- type: Documentation
  url: https://api.glowmarkt.com/api-docs/v0-1/resourcesys/
- type: APIReference
  url: https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/
- type: SignUp
  url: https://data.glowforindustry.com/signup
- type: Pricing
  url: https://data.glowforindustry.com/#pricing
- type: Support
  url: https://www.hildebrand.co.uk/contact-us
- type: Forum
  url: https://forum.glowmarkt.com/
- type: LinkedIn
  url: https://www.linkedin.com/company/hildebrand/
- type: PrivacyPolicy
  url: https://www.hildebrand.co.uk/privacy-policy
- type: Review
  url: review.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/hildebrand"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/hildebrand/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/hildebrand/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.