The GraphQL tag is one of the network’s genuine cross-cuts. It sits at composite 35.2 in the emerging band, but that number understates its reach: the tag links 247 providers and 337 APIs, drawn from provider tags (169), API tags (225), and OpenAPI operation and document tags (132 and 48). Its frequency scores 84.6 — GraphQL shows up almost everywhere — while its breadth is a much narrower 19.7. GraphQL is common but clustered.
Who carries the tag
The 247 providers span several distinct worlds:
- GraphQL-first products. Linear (Linear GraphQL API), Shopify Storefront API, Hasura, Fauna, and Directus expose GraphQL as the primary contract, not a bolt-on.
- Headless CMS. Hygraph, DatoCMS, Craft CMS, Prismic, Contentful-style stacks, and WPGraphQL — content platforms lean on GraphQL heavily, which is why “Content Management” is one of the tag’s nearest neighbors.
- Web3 and DeFi subgraphs. Aave, PancakeSwap, Balancer, Compound Finance, and The Graph itself carry the tag, and “Subgraph,” “Ethereum,” “Web3,” and “DeFi” all rank among GraphQL’s closest neighboring tags.
- The tooling ecosystem. Apollo GraphQL, GraphQL Hive, GraphQL Mesh, gqlgen, Strawberry, Pothos, and WunderGraph populate the tag with the machinery that builds and governs GraphQL itself.
One observation
The neighbor data tells the real story. GraphQL’s strongest tag adjacencies are REST (Jaccard 0.0823) and Subgraph (0.0729), followed by Content Management, Ethereum, and Web3. That pairing with REST matters: GraphQL rarely arrives alone. Providers like Salesforce, Adobe Commerce, and Twenty expose GraphQL alongside REST rather than instead of it. And the Subgraph adjacency reflects an entire sub-category — the PancakeSwap, Aave, and Notional subgraphs — where GraphQL is simply the native query language of on-chain indexing.
The GraphQL-first names are the ones worth studying if you are designing a new surface. Linear and the Shopify Storefront API demonstrate what it looks like when GraphQL is the contract, not an alternative endpoint: the schema is the product, and clients shape their own responses. The tag also carries a heavy gateway and runtime layer — Apollo Router, Apollo Federation, Schema Stitching, GraphQL Mesh, and WunderGraph — which is where teams stitch many GraphQL and REST services into a single federated graph.
Takeaway
The tag’s trend is flat, with a delta of -2.2 from a previous composite of 37.4 — GraphQL is neither surging nor fading on the network, it is settling in as infrastructure. It clusters in three durable places: developer-first SaaS, headless content, and Web3 indexing. If you want to see the full 247 providers and 337 APIs, and which of them treat GraphQL as primary versus complementary, browse apis.io/tags/graphql.