Bloom
Bloom was a decentralized identity, credit-attestation and verifiable-credentials company backed by Pantera Capital, built on Ethereum and IPFS around three products: BloomID (identity attestation), BloomIQ (a credit registry) and BloomScore (credit risk scoring). Its stated aim was to let traditional and digital-currency lenders serve people who cannot obtain a bank account or a credit score, and it announced a TransUnion partnership in 2020 for consumer credit monitoring. Bloom is wound down. Its integration SDKs were archived on GitHub in 2021, its API, documentation and status hosts no longer resolve, bloom.co now redirects to a domain-broker sale listing, and Bloom HoldCo LLC filed a Form 15-12G on 2025-08-14 terminating Exchange Act registration of its BLT token with holders of record stated as "none". What survives is open source: 40 public repositories under github.com/hellobloom and 19 unmaintained but installable npm packages under the @bloomprotocol scope implementing the W3C and DIF decentralized-identity stack (Verifiable Credentials, DIDs, Presentation Exchange, Credential Manifest, WACI).
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.
API Evangelist profiles Bloom 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 — Bloom scores 8.7/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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Bloom
Each block below is one kind of artifact we hold for Bloom. 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.
Resources
Every other property we hold for Bloom — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/bloom · machine-readable index on apis.io