Feedback
Feedbackfeedback
Providers using this tag (96)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 7 Complete, well-documented, and agent-ready
Strong 15 Solid coverage with minor gaps
Developing 33 Usable, with meaningful gaps to close
Thin 31 Limited public surface area
Emerging 7 Early or largely undocumented
APIs with this tag (85)
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 7 Complete, well-documented, and agent-ready
Strong 15 Solid coverage with minor gaps
Developing 31 Usable, with meaningful gaps to close
Thin 25 Limited public surface area
Emerging 6 Early or largely undocumented
Minimal 1 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 96 providers in the APIs.io catalog tagged Feedback, 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 | 49.6 | 17.5 | +32.1 | 96 |
| Access Clarity | 45.6 | 22.3 | +23.3 | 96 |
| Developer Ergonomics | 39.2 | 17.9 | +21.3 | 96 |
| Operational Transparency | 29.8 | 11.3 | +18.5 | 96 |
| Discoverability | 73.2 | 60.4 | +12.8 | 96 |
| Contract Governance | 15.6 | 6.4 | +9.2 | 96 |
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) | 42% | 16% | +26 |
| MCP server (first-party) | 22% | 7% | +15 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 23% | 9% | +14 |
| Security | 98% | 88% | +10 |
| Arazzo workflows | 6% | 2% | +4 |
| Governance rules | 28% | 13% | +15 |
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 HubSpot 82.4
- 3 Mailchimp 81.5
- 4 Leadping 72.2
- 5 Punchh 67.6
- 6 AskNicely 67.3
- 7 Matomo 67.3
- 8 FLORA 65.9
- 9 Olo 64.9
- 10 Bazaarvoice 62.4
- 1 FLORA 62.4
- 2 Automattic 62.3
- 3 Usersnap 55.2
- 4 HubSpot 54.4
- 5 Clarifeye 53.8
- 6 AskNicely 52.7
- 7 Salesforce 52.2
- 8 LinqAlpha 50.9
- 9 Mailchimp 44.8
- 10 Rapidata 41.7
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/feedback"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/feedback"
curl "https://apis.io/api/v1/cohorts/tag/feedback/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.