gRPC
GRPCgRPCgrpc
Providers using this tag (147)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 2 Complete, well-documented, and agent-ready
Strong 12 Solid coverage with minor gaps
Developing 39 Usable, with meaningful gaps to close
Thin 55 Limited public surface area
Emerging 35 Early or largely undocumented
Minimal 4 Almost no public developer surface
APIs with this tag (155)
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 27 Solid coverage with minor gaps
Developing 31 Usable, with meaningful gaps to close
Thin 59 Limited public surface area
Emerging 33 Early or largely undocumented
Minimal 3 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 147 providers in the APIs.io catalog tagged gRPC, 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 | 41.8 | 17.9 | +23.9 | 147 |
| Contract Quality | 36.6 | 17.5 | +19.1 | 147 |
| Operational Transparency | 26.5 | 11.3 | +15.2 | 147 |
| Discoverability | 71.2 | 60.4 | +10.8 | 147 |
| Contract Governance | 12.9 | 6.4 | +6.5 | 147 |
| Access Clarity | 28.5 | 22.3 | +6.2 | 147 |
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) | 39% | 16% | +23 |
| MCP server (first-party) | 11% | 7% | +4 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 12% | 9% | +3 |
| Security | 96% | 88% | +8 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 34% | 13% | +21 |
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 83.3
- 2 Heroic Labs 70.4
- 3 Postman 64.5
- 4 Vendasta 63.3
- 5 Viam 61.6
- 6 Stack Moxie 60.8
- 7 Temporal 59.5
- 8 Decart 57.6
- 9 Kaiko 57.5
- 10 Rigetti Computing 57.2
- 1 Antimetal 55.8
- 2 Salesforce 52.2
- 3 Tigera 50.2
- 4 Telia Company 48.1
- 5 Nord Security 45.7
- 6 Kurrent 45.5
- 7 AgiBot 43.2
- 8 OpenX 40.5
- 9 Starlink 40.5
- 10 Polar Signals 37.6
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/grpc"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/grpc"
curl "https://apis.io/api/v1/cohorts/tag/grpc/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.