Fusio
Fusio is Apache-2.0, self-hosted API management from apioo (Christoph Kappestein, Germany). An operator installs it and builds APIs inside it: an operation binds an HTTP method and path to an action (SQL, HTTP, MongoDB, Elasticsearch, an LLM agent, or code running in a JavaScript, Python, Java or PHP worker) and a TypeSchema-defined request and response shape. Every instance then generates its own machine-readable contract live - OpenAPI 3.0.3, OpenRPC 1.3.0 and TypeAPI - and serves an RFC 9727 api-catalog, RFC 8414 and RFC 9728 OAuth metadata, OpenID Connect discovery and an RFC 9116 security.txt out of the box. It ships its own OAuth2 authorization server, an Angular developer portal, a rate-limiting and monetization layer, a webhook and trigger system, and an MCP server that turns every published operation into an agent tool. There is no vendor-hosted tier and no pricing: the software is the product.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Fusio the way a machine reads it — 31 machine-readable artifacts across 5 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 — Fusio scores 54.2/100 (developing), with a separate agent-readiness read of 47/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Fusio's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fusio/"
title="Fusio on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fusio.svg"
alt="Fusio Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/fusio/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fusio/"
title="Fusio on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fusio/card.svg"
alt="Fusio Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Fusio
Each block below is one kind of artifact we hold for Fusio. 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 5
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.
Fusio Backend API
The Fusio Backend API provides a REST interface to configure and manage all aspects of a Fusio API management instance. It covers operations, routes, schemas, actions, connectio...
Fusio Consumer API
The Fusio Consumer API is used by the developer portal application and enables third-party developers to request access tokens, manage their apps, and interact with protected AP...
Fusio Worker API
The Fusio Worker API enables executing API action logic in multiple programming languages by forwarding requests to external worker processes. Workers are implemented in the tar...
Fusio System API
The Fusio System API is the meta surface every Fusio instance exposes without configuration. It carries the discovery document at the root, the health check, the route table, an...
Fusio Authorization API
The Fusio Authorization API is the OAuth2 authorization server Fusio ships in the product. It issues and refreshes access tokens across the authorization_code, client_credential...
MCP 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.
Fusio MCP Server
Fusio ships a first-party Model Context Protocol server inside the product itself. It is not a separate package or a hosted vendor endpoint: every Fusio instance can expose its ...
MCP SERVERPricing 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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Fusio Plans Pricing
PLANSRate 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.
Fusio 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.
Fusio Finops
FINOPSFeatures 8
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.
API Gateway
Route and manage incoming API requests with built-in rate limiting and authentication.
Developer Portal
Self-service developer portal for API consumers to register, browse APIs, and manage access tokens.
Multi-Language Workers
Execute API action logic in JavaScript, Python, Java, PHP, and other languages through worker processes.
Marketplace
Browse and install pre-built API actions and adapters from the Fusio marketplace.
Schema Management
Define and manage API request and response schemas using TypeSchema format.
OAuth2 Authentication
Built-in OAuth2 server for securing APIs with token-based authentication.
Rate Limiting
Configure per-app and per-user rate limits to protect API resources.
Webhook Support
Define webhook subscriptions to notify consumers of events.
Scroll within the panel for all 8 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Fusio Webhooks
ASYNCAPISecurity Posture 3
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Use Cases 4
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.
API Product Building
Build and publish API products with documentation, authentication, and developer onboarding.
Microservices Gateway
Use Fusio as an API gateway in front of microservices for unified access control.
Data Integration
Connect to databases and external APIs to build data integration endpoints.
Serverless API Backend
Build API backends that execute logic in multiple languages without managing servers.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
MySQL and PostgreSQL
Connect to MySQL and PostgreSQL databases as data sources for API endpoints.
MongoDB
Use MongoDB as a NoSQL data source for API endpoints.
Elasticsearch
Integrate with Elasticsearch for search-powered API endpoints.
RabbitMQ
Use RabbitMQ for asynchronous message processing in API workflows.
Docker
Deploy Fusio and worker containers using Docker and Docker Compose.
Resources
Every other property we hold for Fusio — 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 4
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 8
Status, limits, changes, and where to get help
Scroll within the panel for all 8 ·
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/fusio · machine-readable index on apis.io
This is an independent, third-party profile of Fusio, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.