Apifuse
Apifuse is a native integration platform that enables SaaS companies to build and embed integrations directly into their products. It provides a white-label integration solution with pre-built connectors across 20+ categories, an embeddable UI, workflow automation, and analytics tools that help developers add native integrations without building from scratch.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Apifuse the way a machine reads it — 51 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 — Apifuse scores 38.8/100 (thin), with a separate agent-readiness read of 37/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.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Apifuse'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/apifuse/"
title="Apifuse on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/apifuse.svg"
alt="Apifuse Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/apifuse/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/apifuse/"
title="Apifuse on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/apifuse/card.svg"
alt="Apifuse 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 Apifuse
Each block below is one kind of artifact we hold for Apifuse. 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.
Apifuse Analytics API
Integration usage analytics and monitoring.
Apifuse Connectors API
Available connectors and their configurations.
Apifuse Integrations API
Manage and configure embedded integrations.
Apifuse Users API
User authentication and management.
Apifuse Workflows API
Create and manage integration workflows.
Postman Collections 5
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Apifuse Analytics API
POSTMANApifuse Analytics Users API
POSTMANOpen Collections 6
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).
API Collection
OPEN COLLECTIONApifuse Analytics API
OPEN COLLECTIONApifuse Analytics Connectors API
OPEN COLLECTIONApifuse Analytics Integrations API
OPEN COLLECTIONApifuse Analytics Users API
OPEN COLLECTIONApifuse Analytics Workflows API
OPEN COLLECTIONPricing 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.
Apifuse 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.
Apifuse Finops
FINOPSFeatures 7
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.
Embedded Integration Marketplace
Build a branded integration marketplace within your SaaS product, allowing customers to connect their preferred business tools.
Pre-Built Connectors
150+ pre-built connectors across 20+ categories including CRM, Accounting, Email, Project Management, and more.
Workflow Builder
Visual workflow builder with triggers (polling, realtime, scheduled, webhook) and steps (actions, conditionals, loops, delays, scripts).
White-Label Solution
Fully white-labeled integration UI that embeds seamlessly into your product's look and feel.
Custom Connector SDK
Build custom connectors for proprietary or internal systems using the Apifuse SDK.
Analytics and Monitoring
Track integration usage, task counts, active users, and monitor workflow health in real time.
User Authentication
Manage user OAuth connections, API keys, and integration authentication within your platform.
Scroll within the panel for all 7 ·
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.
Apifuse Context
JSON-LDSpectral Rules 2
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.
Apifuse API Rules
SPECTRALApifuse API Rules
SPECTRALJSON Schema 4
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.
JSON Structure 4
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Apifuse Analytics Structure
JSON STRUCTUREApifuse Connector Structure
JSON STRUCTUREApifuse Integration Structure
JSON STRUCTUREApifuse Workflow Structure
JSON STRUCTUREExamples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Apifuse Analytics Example
EXAMPLEApifuse Connector Example
EXAMPLEApifuse Integration Example
EXAMPLEApifuse Workflow Example
EXAMPLESecurity 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 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.
SaaS Integration Marketplace
Embed a branded integration marketplace into your SaaS product to let customers connect Salesforce, Mailchimp, DocuSign, and 150+ other tools.
Workflow Automation
Allow customers to build no-code automation workflows between their connected apps and your platform.
Platform Expansion
Transform a product into a comprehensive platform by adding native integration capabilities without building each connector from scratch.
Customer Data Sync
Keep customer data synchronized across CRM, marketing automation, and your platform in real time.
Solutions 3
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Growth Plan
Up to 500,000 tasks/month with 6 pre-built connectors for companies starting with embedded integrations.
Platform Plan
Up to 5,000,000 tasks/month with unlimited pre-built connectors for established SaaS companies.
Enterprise Plan
Custom task volume, fully managed integrations, and dedicated support for enterprise SaaS platforms.
Resources
Every other property we hold for Apifuse — 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 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/apifuse · machine-readable index on apis.io
This is an independent, third-party profile of Apifuse, 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.