emerging · -1.4 persona persona

Revenue Operations

Score 21.2 / 100 76 providers +1 via APIs 7 APIs Search apis.io →
Variants seen in the corpus: RevOpsRevenue Operations

Providers using this tag (76)

Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.

Exemplar 3 Complete, well-documented, and agent-ready
Strong 13 Solid coverage with minor gaps
Developing 20 Usable, with meaningful gaps to close
Thin 14 Limited public surface area
Emerging 15 Early or largely undocumented
Minimal 11 Almost no public developer surface

APIs with this tag (7)

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 1 Solid coverage with minor gaps
Developing 4 Usable, with meaningful gaps to close
Thin 2 Limited public surface area

Companies reaching this through an API (1)

These companies publish an API, specification or operation carrying “Revenue Operations” 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.

Noded AI

Score breakdown

Frequency
48.9
log-scaled weighted occurrences
Breadth
1.0
spread across providers
Quality lift
36.1
mean composite of providers using it
Cohesion
10.3
strength of nearest seed neighbor

Related tags

Sales Engagement 15 co-occurrences Go-To-Market 14 co-occurrences Customer Success 10 co-occurrences Sales 30 co-occurrences Sales Enablement 12 co-occurrences Revenue Intelligence 7 co-occurrences Salesforce 12 co-occurrences Conversation Intelligence 8 co-occurrences

Where this tag comes from

Provider tag76
Api tag7

Cohort brief

Auto-generated

The 72 providers in the APIs.io catalog tagged Revenue Operations, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.

Providers
72
of 76 in the catalog
Mean Kin Score
36.6
+12.5 vs catalog 24.1
Mean Agent Readiness
23.3
+9.2 vs catalog 14.1
Spread
0–78.7
median 37.2 · σ 19.5
How the 72 split by band
Exemplar 3Strong 13Developing 18Thin 14Emerging 14Minimal 10
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Access Clarity 56.3 30 +26.3 72
Developer Ergonomics 35.2 24.5 +10.7 72
Operational Transparency 23.5 13.2 +10.3 72
Contract Governance 16.7 9.7 +7 72
Contract Quality 21.9 18.6 +3.3 72
Discoverability 61.4 59.1 +2.3 72

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.

What this cohort publishes
ArtifactThis cohortCatalogDifference
MCP server (any) 43% 18% +25
MCP server (first-party) 44% 16% +28
Agent Skills 0% 0% 0
OAuth scopes 33% 13% +20
Security 99% 99% 0
Arazzo workflows 1% 1% 0
Governance rules 35% 36% -1

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.

Top by Kin Score
  1. 1 Outreach 78.7
  2. 2 UserGems 69.8
  3. 3 Chili Piper 68.1
  4. 4 Stack Moxie 65.4
  5. 5 Nooks 64.1
  6. 6 CaptivateIQ 63.8
  7. 7 DealHub 60.5
  8. 8 LeanData 60.2
  9. 9 Clari 59.7
  10. 10 Knownwell 59.1
Top by Agent Readiness
  1. 1 Monaco 61.4
  2. 2 UserGems 60.7
  3. 3 Caretta 60.3
  4. 4 Nooks 58.7
  5. 5 Equals 57
  6. 6 Clari 56.9
  7. 7 Reevo 56.5
  8. 8 Chili Piper 56.3
  9. 9 LeadIQ 56.3
  10. 10 Fullcast 54.8
All 76 members of this roster resolve to a provider in the catalog; 72 carry a score (95%). The figures above describe the scored members only.
Coverage caveat. 63 of 72 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 14 November 2026, across 41591 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.

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.
All 92 tools →

Call it yourself

curl for this page
This tag
curl "https://apis.io/api/v1/tags/revenue-operations"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort (paid plan)
The distribution (Pro)

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.