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

Validere

Validere is an enterprise environmental operations and emissions data management platform for the energy industry. Upstream, midstream, refining, utility, and CCUS operators use it to unify operational, measurement, and emissions data for regulatory and voluntary emissions reporting, methane management, EHS compliance, asset management, and production accounting. Its public REST API at api.validere.io spans the CarbonHub App API (facilities, equipment, flows, devices, measurements, estimation methods, records, workflows, and reports) and the Data Platform Source API for pushing JSON or file data validated against registered JSON Schemas, with ingestion tracked through a Transactions API.

agent ready

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles Validere the way a machine reads it — 59 machine-readable artifacts across 55 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

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 — Validere scores 44.0/100 (thin), with a separate agent-readiness read of 55/100 (agent ready). 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 — 44.0/100 · thin
Contract Quality 11.6 / 25
Developer Ergonomics 11.7 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 55/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 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 4 / 4
Consent & Bot Identity 0 / 3

How we profile Validere

Each block below is one kind of artifact we hold for Validere. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 55

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

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

Validere company_equipment_type_groups API

Company <> Equipment Type Groups

Validere company_feature_flags API

Company Feature Flags

Validere company_unit_config API

Company Unit Configuration

Validere custom_attribute_definition API

Manage Custom Attribute Definitions

Validere data API

The data API from Validere — 2 operation(s) for data.

Validere default_record_value_configuration API

Default Record Value Configurations

Validere device_types API

Manage Device Types

Validere devices API

Manage Devices

Validere equipment API

Manage Equipment

Validere equipment_types API

Manage Equipment Types

Validere estimation_methods_default_records API

Estimation Methods Default Records

Validere events API

Emission Events

Validere facilities API

Manage Facilities

Validere flows API

Manage Flows

Validere group_categories API

Manage Group Categories

Validere job API

Bulk Job status

Validere measurement_series API

Manage Measurement series

Validere measurement_types API

Manage Measurement Types

Validere measurements API

Manage Measurements

Validere networks API

Manage Networks

Validere records API

Manage Records

Validere templated_configurations API

Templated Configurations

Validere transactions API

The transactions API from Validere — 7 operation(s) for transactions.

Validere type_metadata API

Types used across the APIs

Validere TypeMetadata API

The TypeMetadata API from Validere — 4 operation(s) for typemetadata.

Validere user_groups API

Manage User Groups

Validere user_unit_config API

User Unit Configuration

Scroll within the panel for all 55 ·

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

Model Context Protocol servers that expose these APIs to AI agents.

validere-mcp.yml

MCP SERVER

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

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

Validere Authentication

oauth2/http/apiKey · 3 schemes

SECURITY

Validere Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Validere Trust Center

SOC 2, ISO 27001, ISO 27018, GDPR

SECURITY

Resources

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

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

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