WunderGraph
Full Lifecycle API Management for (Federated) GraphQL. Schema Registry, composition checks, analytics, metrics, tracing and routing. Deploy 100% on-prem or use our Managed Service. Apache 2.0 licensed, no vendor-lock.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles WunderGraph the way a machine reads it — 60 machine-readable artifacts across 10 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — WunderGraph scores 65.1/100 (strong), with a separate agent-readiness read of 64/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile WunderGraph
Each block below is one kind of artifact we hold for WunderGraph. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 10
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
WunderGraph Analytics API
Access graph analytics, metrics, and performance data.
WunderGraph API Keys API
Manage API keys for platform authentication.
WunderGraph Feature Flags API
Manage feature flags for gradual rollout of graph changes.
WunderGraph Feature Subgraphs API
Manage feature subgraphs for experimental feature development.
WunderGraph Federated Graphs API
Manage federated graphs composed from multiple subgraphs using label matchers.
WunderGraph Monographs API
Manage monographs - non-federated graphs limited to a single subgraph.
WunderGraph Namespaces API
Manage namespaces for organizing graphs and subgraphs.
WunderGraph Router API
Manage router configuration and authentication tokens.
WunderGraph Schema Contracts API
Manage schema contracts for providing filtered graph views to different consumers.
WunderGraph Subgraphs API
Manage subgraphs - isolated GraphQL schemas that compose into federated graphs.
Scroll within the panel for all 10 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
WunderGraph Cosmo Platform API
OPEN COLLECTIONMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
MCP Server
MCP SERVERAgent Skills 1
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
graphql-federation
AGENT SKILLGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
WunderGraph GraphQL API
The WunderGraph Cosmo Platform API provides programmatic access to manage federated GraphQL architectures at scale. It powers the Cosmo CLI (wgc) and Cosmo Studio, enabling mana...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Wundergraph Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Wundergraph Finops
FINOPSFeatures 27
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Advanced Request Tracing
Analytics, Metrics & Tracing
API Gateway
Audit Log
Authentication & Authorization
AWS Lambda Router
Breaking Change Detection
Cache Warmer
Composition Checks
Compositions
Event Driven Federated Subscriptions (Edfs)
Feature Flags
Graph Access Control
Graphql Federation V1 & V2
Graphql Router / Gateway
Graphql Subscriptions for Federation
Managed Service
Mcp Gateway
Oidc
Opentelemetry & Distributed Tracing
Persisted Operations
Pull-Request-Based Schema Workflows
Rbac
Schema Change Notifications
Schema Contracts
Schema Registry
Schema Usage Reporting
Scroll within the panel for all 27 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Wundergraph Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
WunderGraph API Rules
SPECTRALJSON Schema 10
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
WunderGraph Cosmo API Key
JSON SCHEMAWunderGraph Cosmo Changelog Entry
JSON SCHEMAWunderGraph Cosmo Feature Flag
JSON SCHEMAWunderGraph Cosmo Federated Graph
JSON SCHEMAWunderGraph Cosmo Monograph
JSON SCHEMAWunderGraph Cosmo Namespace
JSON SCHEMAWunderGraph Cosmo Operation Response
JSON SCHEMAWunderGraph Cosmo Router Token
JSON SCHEMAWunderGraph Cosmo Schema Contract
JSON SCHEMAWunderGraph Cosmo Subgraph
JSON SCHEMAScroll within the panel for all 10 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 1
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
GraphQL Federation
Resources
Every other property we hold for WunderGraph — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Learn 2
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/wundergraph · machine-readable index on apis.io