Cross-Chain
Providers using this tag (35)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Developing 9 Usable, with meaningful gaps to close
Thin 12 Limited public surface area
Emerging 7 Early or largely undocumented
Minimal 3 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (16)
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 →
Strong 2 Solid coverage with minor gaps
Developing 2 Usable, with meaningful gaps to close
Thin 10 Limited public surface area
Companies reaching this through an API (8)
These companies publish an API, specification or operation carrying “Cross-Chain” 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 34 providers in the APIs.io catalog tagged Cross-Chain, 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 | 47.1 | 23.4 | +23.7 | 34 |
| Contract Quality | 32.3 | 20.1 | +12.2 | 34 |
| Operational Transparency | 22.8 | 14 | +8.8 | 34 |
| Discoverability | 68.8 | 61 | +7.8 | 34 |
| Contract Governance | 6 | 6.5 | -0.5 | 34 |
| Access Clarity | 22.8 | 26.5 | -3.7 | 34 |
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) | 26% | 10% | +16 |
| MCP server (first-party) | 37% | 13% | +24 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 0% | 11% | -11 |
| Security | 100% | 96% | +4 |
| Arazzo workflows | 6% | 2% | +4 |
| Governance rules | 17% | 13% | +4 |
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.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.