Obol
Obol builds distributed validator infrastructure for Ethereum, letting a validator be run across multiple independent operators and machines (a Distributed Validator, or DV) instead of a single node, which removes single points of failure in proof-of-stake staking. Its core software is Charon, a Go middleware client that coordinates the operators, plus the DV Launchpad dapp, the Obol Splits smart contracts, and the Obol API (api.obol.tech) with a TypeScript SDK for creating and managing clusters. The Obol API exposes cluster definitions, cluster locks, validator states, exits, deposits, fee recipients, effectiveness, peer scores, Techne credentials, and network staking metrics.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Obol the way a machine reads it — 39 machine-readable artifacts across 1 API, 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 — Obol scores 44.2/100 (developing), with a separate agent-readiness read of 24/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Obol's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/obol/"
title="Obol on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/obol.svg"
alt="Obol Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/obol/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/obol/"
title="Obol on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/obol/card.svg"
alt="Obol Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Obol
Each block below is one kind of artifact we hold for Obol. 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 17
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.
Obol Address API
The Address API from Obol — 7 operation(s) for address.
Obol Cluster Definition API
The Cluster Definition API from Obol — 4 operation(s) for cluster definition.
Obol Cluster Effectiveness API
The Cluster Effectiveness API from Obol — 1 operation(s) for cluster effectiveness.
Obol Cluster Lock API
The Cluster Lock API from Obol — 22 operation(s) for cluster lock.
Obol Deposit Data API
The Deposit Data API from Obol — 4 operation(s) for deposit data.
Obol DV Exit API
The DV Exit API from Obol — 8 operation(s) for dv exit.
Obol DV Migrate API
The DV Migrate API from Obol — 1 operation(s) for dv migrate.
Obol Fee Recipient API
The Fee Recipient API from Obol — 4 operation(s) for fee recipient.
Obol Metrics API
The Metrics API from Obol — 1 operation(s) for metrics.
Obol OWR Information API
The OWR Information API from Obol — 1 operation(s) for owr information.
Obol Positions API
The Positions API from Obol — 2 operation(s) for positions.
Obol State API
The State API from Obol — 1 operation(s) for state.
Obol System API
System related endpoints.
Obol Techne Credentials API
The Techne Credentials API from Obol — 4 operation(s) for techne credentials.
Obol Terms And Conditions API
The Terms And Conditions API from Obol — 2 operation(s) for terms and conditions.
Obol Test API
The Test API from Obol — 2 operation(s) for test.
Obol tvs API
The tvs API from Obol — 2 operation(s) for tvs.
Scroll within the panel for all 17 ·
Open Collections 18
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONObol Address API
OPEN COLLECTIONObol Address Cluster Definition API
OPEN COLLECTIONObol Address Cluster Effectiveness API
OPEN COLLECTIONObol Address Cluster Lock API
OPEN COLLECTIONObol Address Deposit Data API
OPEN COLLECTIONObol Address DV Exit API
OPEN COLLECTIONObol Address DV Migrate API
OPEN COLLECTIONObol Address Fee Recipient API
OPEN COLLECTIONObol Address Metrics API
OPEN COLLECTIONObol Address OWR Information API
OPEN COLLECTIONObol Address Positions API
OPEN COLLECTIONObol Address State API
OPEN COLLECTIONObol Address System API
OPEN COLLECTIONObol Address Techne Credentials API
OPEN COLLECTIONObol Address Terms And Conditions API
OPEN COLLECTIONObol Address Test API
OPEN COLLECTIONObol Address tvs API
OPEN COLLECTIONScroll within the panel for all 18 ·
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Obol — 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 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 3
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
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/obol · machine-readable index on apis.io
This is an independent, third-party profile of Obol, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.