emerging · -1.1 marketcapability domainschemaresource

NoSQL

Score 21.7 / 100 33 providers +10 via APIs 18 APIs Search apis.io →
Business capabilities this tag reaches
Information Technology Management 1

Providers using this tag (33)

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

Exemplar 7 Complete, well-documented, and agent-ready
Strong 4 Solid coverage with minor gaps
Developing 8 Usable, with meaningful gaps to close
Thin 5 Limited public surface area
Emerging 4 Early or largely undocumented
Minimal 4 Almost no public developer surface
Unrated 1 Not yet scored

APIs with this tag (18)

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 4 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 4 Usable, with meaningful gaps to close
Thin 4 Limited public surface area
Minimal 1 Almost no public developer surface

Companies reaching this through an API (10)

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

Amazon Web Services Cloudera IBM JD.com (Jingdong) MySQL Oracle Oracle Database SAKURA internet SAP HANA Spring Data

Score breakdown

Frequency
42.9
log-scaled weighted occurrences
Breadth
0.4
spread across providers
Quality lift
44.1
mean composite of providers using it
Cohesion
13.4
strength of nearest seed neighbor

Where this tag sits

Database broader

Related tags

Document Database 9 co-occurrences Key-Value Store 10 co-occurrences MongoDB 6 co-occurrences Database 38 co-occurrences Cluster 17 co-occurrences Replication 6 co-occurrences Vector Search 7 co-occurrences Serverless 10 co-occurrences

Where this tag comes from

Provider tag33
Api tag18

Cohort brief

Auto-generated

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

Providers
28
of 33 in the catalog
Mean Kin Score
49.4
+25.3 vs catalog 24.1
Mean Agent Readiness
29.2
+15.1 vs catalog 14.1
Spread
10.3–84
median 45.8 · σ 20.4
How the 28 split by band
Exemplar 7Strong 4Developing 8Thin 5Emerging 3Minimal 1
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Contract Quality 51.2 18.6 +32.6 28
Developer Ergonomics 54.3 24.5 +29.8 28
Operational Transparency 40 13.2 +26.8 28
Access Clarity 45.4 30 +15.4 28
Contract Governance 21.3 9.7 +11.6 28
Discoverability 69.1 59.1 +10 28

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) 38% 18% +20
MCP server (first-party) 38% 16% +22
Agent Skills 0% 0% 0
OAuth scopes 21% 13% +8
Security 97% 99% -2
Arazzo workflows 14% 1% +13
Governance rules 86% 36% +50

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 CData 84
  2. 2 Amazon DynamoDB 82.4
  3. 3 MongoDB 79.9
  4. 4 Amazon DocumentDB 72.9
  5. 5 Azure Cosmos DB 69.4
  6. 6 Amazon SimpleDB 68.8
  7. 7 Amazon Keyspaces 68.5
  8. 8 Google Cloud Bigtable 65.5
  9. 9 Couchbase 65.1
  10. 10 Google Cloud Firestore 64.4
Top by Agent Readiness
  1. 1 CData 67.3
  2. 2 MongoDB 60
  3. 3 Amazon DynamoDB 41.9
  4. 4 Redis 41.3
  5. 5 Amazon Keyspaces 40.3
  6. 6 Google Cloud Bigtable 37.6
  7. 7 Google Cloud Datastore 36.9
  8. 8 Google Cloud Firestore 36.7
  9. 9 Amazon SimpleDB 35.2
  10. 10 Amazon DocumentDB 33.6
All 33 members of this roster resolve to a provider in the catalog; 28 carry a score (85%). The figures above describe the scored members only.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/nosql"
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.