Assets
Assetsassets
Providers using this tag (228)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 11 Complete, well-documented, and agent-ready
Strong 45 Solid coverage with minor gaps
Developing 91 Usable, with meaningful gaps to close
Thin 59 Limited public surface area
Emerging 19 Early or largely undocumented
Minimal 3 Almost no public developer surface
APIs with this tag (251)
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 18 Complete, well-documented, and agent-ready
Strong 52 Solid coverage with minor gaps
Developing 96 Usable, with meaningful gaps to close
Thin 62 Limited public surface area
Emerging 20 Early or largely undocumented
Minimal 3 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 228 providers in the APIs.io catalog tagged Assets, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Quality | 54 | 17.5 | +36.5 | 228 |
| Developer Ergonomics | 44.7 | 17.9 | +26.8 | 228 |
| Access Clarity | 42 | 22.3 | +19.7 | 228 |
| Operational Transparency | 30.3 | 11.3 | +19 | 228 |
| Discoverability | 74 | 60.4 | +13.6 | 228 |
| Contract Governance | 17.5 | 6.4 | +11.1 | 228 |
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) | 45% | 16% | +29 |
| MCP server (first-party) | 18% | 7% | +11 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 30% | 9% | +21 |
| Security | 99% | 88% | +11 |
| Arazzo workflows | 11% | 2% | +9 |
| Governance rules | 38% | 13% | +25 |
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 Salesforce Marketing Cloud 83.5
- 2 Salesforce 83.3
- 3 Adobe 80.4
- 4 SendPulse 75.7
- 5 Mux 75.4
- 6 Optimizely 75.1
- 7 Adobe Suite 71.2
- 8 Uphold 69.1
- 9 Canva 69
- 10 Facebook Business Manager 68.6
- 1 DoiT 74.4
- 2 Appcharge 62.5
- 3 FLORA 62.4
- 4 Adobe Suite 61.5
- 5 Talkable 59.5
- 6 Knak 58.8
- 7 Salesforce Marketing Cloud 56.2
- 8 SendPulse 55.8
- 9 Lean Technologies 53.2
- 10 Factset 52.8
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for tags
7 MCP tools reach this
find_tagsBrowse and filter every tag in the catalog.get_cohortThis tag as a scored cohort — every provider carrying it, with scores.cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/assets"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/assets"
curl "https://apis.io/api/v1/cohorts/tag/assets/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.