Digital Assets
Providers using this tag (123)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 11 Solid coverage with minor gaps
Developing 26 Usable, with meaningful gaps to close
Thin 23 Limited public surface area
Emerging 28 Early or largely undocumented
Minimal 34 Almost no public developer surface
APIs with this tag (36)
Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →
Exemplar 2 Complete, well-documented, and agent-ready
Strong 12 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
Thin 10 Limited public surface area
Emerging 6 Early or largely undocumented
Companies reaching this through an API (10)
These companies publish an API, specification or operation carrying “Digital Assets” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 114 providers in the APIs.io catalog tagged Digital Assets, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 34.5 | 23.2 | +11.3 | 114 |
| Operational Transparency | 20.6 | 13.7 | +6.9 | 114 |
| Contract Quality | 23 | 17.6 | +5.4 | 114 |
| Discoverability | 61.8 | 58.1 | +3.7 | 114 |
| Access Clarity | 28.4 | 26.5 | +1.9 | 114 |
| Contract Governance | 6.9 | 6.3 | +0.6 | 114 |
A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 15% | 14% | +1 |
| MCP server (first-party) | 15% | 12% | +3 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 11% | 11% | 0 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 3% | 14% | -11 |
mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.
- 1 Uphold 70.6
- 2 Solidus Labs 65.5
- 3 Crypto.com 65
- 4 Fireblocks 64.5
- 5 Bullish 60.8
- 6 Ledger 58.4
- 7 MaiCoin 58.2
- 8 ZenLedger 56.2
- 9 Ripple Labs 55.6
- 10 CipherOwl 54.8
- 1 Lukka 55
- 2 Ripple Labs 51.8
- 3 BVNK 50
- 4 Western Alliance Bancorporation 49.8
- 5 Anchorage Digital 47.5
- 6 Paxos 46.5
- 7 Crypto.com 45.1
- 8 Korbit 43.6
- 9 Uphold 42.1
- 10 Ledger 42
Coverage caveat. 106 of 114 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 5 October 2026, across 29093 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.