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
Verra website screenshot

Verra

Verra is a Washington, D.C.-based nonprofit standards body that develops and manages the world's leading certification programs for climate action and sustainable development. Its flagship program, the Verified Carbon Standard (VCS), is the most widely used voluntary greenhouse gas crediting program globally, with more than 2,579 registered projects across 132+ countries and over 1.3 billion Verified Carbon Units (VCUs) issued. Verra also operates the Climate, Community & Biodiversity Standards (CCB), the Sustainable Development Verified Impact Standard (SD VISta), the Plastic Waste Reduction Standard (PWRP), the Scope 3 Standard Program, and the Jurisdictional and Nested REDD+ (JNR) framework. The Verra Registry at registry.verra.org is the system of record for projects, methodologies, issuances, retirements, and the AFOLU pooled buffer account across these programs; project documentation, public comment periods, and credit-lifecycle records are all surfaced through that registry. Verra recently launched VCS Version 5, modernizing program operations, strengthening safeguards, and clarifying credit rights. Verra does not publish a public developer API, OpenAPI specification, SDK, or GitHub organization; programmatic data access is limited to the registry's web interface and filtered report exports, and there is no open-source code or machine-readable spec catalog associated with the organization.

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

API Evangelist profiles Verra the way a machine reads it — 1 machine-readable artifact, 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 — Verra scores 7.2/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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 — 7.2/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.4 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Verra

Each block below is one kind of artifact we hold for Verra. 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.

Security Posture 1

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.

Verra Org Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

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

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Operate 1

Status, limits, changes, and where to get help

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