Verdigris Technologies

Verdigris Technologies builds AI-powered building energy intelligence, pairing proprietary current-sensor hardware clamped onto a building's electrical panels with cloud software that monitors every circuit in real time. The Verdigris API exposes that telemetry through OAuth2-secured REST endpoints (the Data API v4): energy, power, voltage, current, power factor, total harmonic distortion, weather, energy forecasts, building controls, and high-resolution Pro Capture waveforms, all queryable at building, panel, circuit, and breaker granularity with batch variants for pulling many entities in a single request. Developers use it to power enterprise data lakes, internal power-monitoring dashboards, and sustainability and energy-optimization applications for smart buildings.

Verdigris Technologies publishes 10 APIs on the APIs.io network, including Control API, Current API, Energy API, and 7 more. Tagged areas include Company, Energy, Energy Management, Building Automation, and Smart Buildings.

Verdigris Technologies’ developer surface includes documentation, API reference, getting-started guide, authentication, support, engineering blog, and 20 more developer resources.

🌐 Visit website 📡 Source on GitHub

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

AccessSelf serve

1 APIs

Company Energy Energy Management Building Automation Smart Buildings IoT SustainabilityPower MonitoringTime Series Analytics Electricity

Kin Score

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

Composite quality — 40.4/100 · developing

Contract Quality 12.0 / 21

Developer Ergonomics 6.8 / 17

Access Clarity 4.3 / 17

Operational Transparency 0.3 / 11

Contract Governance 0.5 / 10

Discoverability 6.5 / 9

Regulatory Posture 7.7 / 15

Agent readiness — 37/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 6 / 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 does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

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/.

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/verdigris-technologies: 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 10

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

Verdigris Technologies Control API

Endpoints that return control data from building management systems (BMS)

Verdigris Technologies Current API

Endpoints that return current data

Verdigris Technologies Energy API

Endpoints that return energy data

Verdigris Technologies Events API

The Events API from Verdigris Technologies — 3 operation(s) for events.

Verdigris Technologies Forecast API

The Forecast API from Verdigris Technologies — 1 operation(s) for forecast.

Verdigris Technologies Power API

Endpoints that return power data

Verdigris Technologies Power Factor API

Endpoints that return power factor data

Verdigris Technologies Total Harmonic Distortion API

Endpoints that return total harmonic distortion data

Verdigris Technologies Voltage API

Endpoints that return voltage data

Verdigris Technologies Weather API

Endpoints that return weather data

Scroll for all 10

Open Collections 11

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

API Collection

OPEN COLLECTION

Data Control API

OPEN COLLECTION

Data Control Current API

OPEN COLLECTION

Data Control Energy API

OPEN COLLECTION

Data Control Events API

OPEN COLLECTION

Data Control Forecast API

OPEN COLLECTION

Data Control Power API

OPEN COLLECTION

Data Control Power Factor API

OPEN COLLECTION

Data Control Total Harmonic Distortion API

OPEN COLLECTION

Data Control Voltage API

OPEN COLLECTION

Data Control Weather API

OPEN COLLECTION

Scroll for all 11

Security Posture 3

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

Verdigris Technologies Authentication

oauth2 · 1 scheme

SECURITY

Verdigris Technologies Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Verdigris Technologies Trust Center

SOC 2

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Verdigris Technologies Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 5

Authentication, authorization, and security posture

TrustCenter

DomainSecurity

OAuthScopes

Authentication

Compliance

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 1

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: verdigris-technologies
name: Verdigris Technologies
description: 'Verdigris Technologies builds AI-powered building energy intelligence, pairing proprietary current-sensor hardware
  clamped onto a building''s electrical panels with cloud software that monitors every circuit in real time. The Verdigris
  API exposes that telemetry through OAuth2-secured REST endpoints (the Data API v4): energy, power, voltage, current, power
  factor, total harmonic distortion, weather, energy forecasts, building controls, and high-resolution Pro Capture waveforms,
  all queryable at building, panel, circuit, and breaker granularity with batch variants for pulling many entities in a single
  request. Developers use it to power enterprise data lakes, internal power-monitoring dashboards, and sustainability and
  energy-optimization applications for smart buildings.'
url: https://raw.githubusercontent.com/api-evangelist/verdigris-technologies/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- dcvc
x-tier: stub
x-tier-reason: portfolio-lead
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: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
image: https://verdigris.co/favicon.ico
tags:
- Company
- Energy
- Energy Management
- Building Automation
- Smart Buildings
- IoT
- Sustainability
- Power Monitoring
- Time Series
- Analytics
- Electricity
apis:
- aid: verdigris-technologies:verdigris-technologies-control-api
  name: Verdigris Technologies Control API
  description: Endpoints that return control data from building management systems (BMS)
  humanURL: https://docs.verdigris.co/reference/getting-started-with-your-api
  baseURL: https://api.verdigris.co/data/v4
  tags:
  - Control
  properties:
  - type: OpenAPI
    url: openapi/verdigris-technologies-control-api-openapi.yml
  - type: Documentation
    url: https://docs.verdigris.co/reference/getting-started-with-your-api
- aid: verdigris-technologies:verdigris-technologies-current-api
  name: Verdigris Technologies Current API
  description: Endpoints that return current data
  humanURL: https://docs.verdigris.co/reference/getting-started-with-your-api
  baseURL: https://api.verdigris.co/data/v4
  tags:
  - Current
  properties:
  - type: OpenAPI
    url: openapi/verdigris-technologies-current-api-openapi.yml
  - type: Documentation
    url: https://docs.verdigris.co/reference/getting-started-with-your-api
- aid: verdigris-technologies:verdigris-technologies-energy-api
  name: Verdigris Technologies Energy API
  description: Endpoints that return energy data
  humanURL: https://docs.verdigris.co/reference/getting-started-with-your-api
  baseURL: https://api.verdigris.co/data/v4
  tags:
  - Energy
  properties:
  - type: OpenAPI
    url: openapi/verdigris-technologies-energy-api-openapi.yml
  - type: Documentation
    url: https://docs.verdigris.co/reference/getting-started-with-your-api
- aid: verdigris-technologies:verdigris-technologies-events-api
  name: Verdigris Technologies Events API
  description: The Events API from Verdigris Technologies — 3 operation(s) for events.
  humanURL: https://docs.verdigris.co/reference/getting-started-with-your-api
  baseURL: https://api.verdigris.co/data/v4
  tags:
  - Event
  tags_raw:
  - Events
  properties:
  - type: OpenAPI
    url: openapi/verdigris-technologies-events-api-openapi.yml
  - type: Documentation
    url: https://docs.verdigris.co/reference/getting-started-with-your-api
- aid: verdigris-technologies:verdigris-technologies-forecast-api
  name: Verdigris Technologies Forecast API
  description: The Forecast API from Verdigris Technologies — 1 operation(s) for forecast.
  humanURL: https://docs.verdigris.co/reference/getting-started-with-your-api
  baseURL: https://api.verdigris.co/data/v4
  tags:
  - Forecast
  properties:
  - type: OpenAPI
    url: openapi/verdigris-technologies-forecast-api-openapi.yml
  - type: Documentation
    url: https://docs.verdigris.co/reference/getting-started-with-your-api
- aid: verdigris-technologies:verdigris-technologies-power-api
  name: Verdigris Technologies Power API
  description: Endpoints that return power data
  humanURL: https://docs.verdigris.co/reference/getting-started-with-your-api
  baseURL: https://api.verdigris.co/data/v4
  tags:
  - Power
  properties:
  - type: OpenAPI
    url: openapi/verdigris-technologies-power-api-openapi.yml
  - type: Documentation
    url: https://docs.verdigris.co/reference/getting-started-with-your-api
- aid: verdigris-technologies:verdigris-technologies-power-factor-api
  name: Verdigris Technologies Power Factor API
  description: Endpoints that return power factor data
  humanURL: https://docs.verdigris.co/reference/getting-started-with-your-api
  baseURL: https://api.verdigris.co/data/v4
  tags:
  - Power Factor
  properties:
  - type: OpenAPI
    url: openapi/verdigris-technologies-power-factor-api-openapi.yml
  - type: Documentation
    url: https://docs.verdigris.co/reference/getting-started-with-your-api
- aid: verdigris-technologies:verdigris-technologies-total-harmonic-distortion-api
  name: Verdigris Technologies Total Harmonic Distortion API
  description: Endpoints that return total harmonic distortion data
  humanURL: https://docs.verdigris.co/reference/getting-started-with-your-api
  baseURL: https://api.verdigris.co/data/v4
  tags:
  - Total Harmonic Distortion
  properties:
  - type: OpenAPI
    url: openapi/verdigris-technologies-total-harmonic-distortion-api-openapi.yml
  - type: Documentation
    url: https://docs.verdigris.co/reference/getting-started-with-your-api
- aid: verdigris-technologies:verdigris-technologies-voltage-api
  name: Verdigris Technologies Voltage API
  description: Endpoints that return voltage data
  humanURL: https://docs.verdigris.co/reference/getting-started-with-your-api
  baseURL: https://api.verdigris.co/data/v4
  tags:
  - Voltage
  properties:
  - type: OpenAPI
    url: openapi/verdigris-technologies-voltage-api-openapi.yml
  - type: Documentation
    url: https://docs.verdigris.co/reference/getting-started-with-your-api
- aid: verdigris-technologies:verdigris-technologies-weather-api
  name: Verdigris Technologies Weather API
  description: Endpoints that return weather data
  humanURL: https://docs.verdigris.co/reference/getting-started-with-your-api
  baseURL: https://api.verdigris.co/data/v4
  tags:
  - Weather
  properties:
  - type: OpenAPI
    url: openapi/verdigris-technologies-weather-api-openapi.yml
  - type: Documentation
    url: https://docs.verdigris.co/reference/getting-started-with-your-api
common:
- type: Website
  url: https://www.verdigris.co/
- type: CapabilityMap
  url: capabilities/verdigris-technologies-capability-edges.yml
  name: Verdigris Technologies Business Capability Map
- type: TrustCenter
  url: security/verdigris-technologies-trust-center.yml
- type: DomainSecurity
  url: security/verdigris-technologies-domain-security.yml
- type: OAuthScopes
  url: scopes/verdigris-technologies-scopes.yml
- type: DeveloperPortal
  url: https://docs.verdigris.co
- type: Documentation
  url: https://docs.verdigris.co/docs/vedigris-api-overview
- type: APIReference
  url: https://docs.verdigris.co/reference
- type: GettingStarted
  url: https://docs.verdigris.co/reference/getting-started-with-your-api
- type: Authentication
  url: authentication/verdigris-technologies-authentication.yml
- type: Support
  url: https://support.verdigris.co
- type: Blog
  url: https://verdigris.co/blog
- type: GitHubOrganization
  url: https://github.com/VerdigrisTech
- type: TermsOfService
  url: https://verdigris.co/terms
- type: Login
  url: https://admin.verdigris.co
- type: LLMsTxt
  url: llms/verdigris-technologies-llms.txt
- type: WellKnown
  url: well-known/verdigris-technologies-well-known.yml
- type: X-MCPServerCandidate
  url: mcp/verdigris-technologies-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: Overlay
  url: overlays/verdigris-technologies-data-v4-overlay.yaml
- type: Conformance
  url: conformance/verdigris-technologies-conformance.yml
- type: Compliance
  url: https://trust.verdigris.co/
- type: ErrorCatalog
  url: errors/verdigris-technologies-problem-types.yml
- type: Lifecycle
  url: lifecycle/verdigris-technologies-lifecycle.yml
- type: Conventions
  url: conventions/verdigris-technologies-conventions.yml
- type: DataModel
  url: data-model/verdigris-technologies-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 20
  pass: local-v1

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/verdigris-technologies"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/verdigris-technologies/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.