How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Supaglue website screenshot

Supaglue

Supaglue was an open-source unified API platform for B2B SaaS product integrations: a single contract for CRM, engagement, ticketing, enrichment and marketing-automation objects projected across 30+ third-party providers (Salesforce, HubSpot, Pipedrive, Outreach, Salesloft, Zendesk, Apollo and more), plus managed OAuth to those providers, managed syncs into the customer's own warehouse (Postgres, BigQuery, Snowflake, Redshift, S3), a passthrough escape hatch to native provider APIs, and a Management API to configure customers, connections, schemas, entities and sync schedules. Nine first-party OpenAPI documents (v2, x-api-key auth) and nine typed webhook events were published. THE SERVICE IS RETIRED: the GitHub repository (github.com/supaglue-labs) was archived by its owner on 2024-03-10, api.supaglue.io and app.supaglue.io no longer resolve, and supaglue.com now redirects to a HugeDomains sale listing. The MIT-licensed code remains self-hostable, and the contract is preserved here as the historical record of a well-shaped unified API.

agent ready

Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.

Kin Score

API Evangelist profiles Supaglue the way a machine reads it — 99 machine-readable artifacts across 40 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 — Supaglue scores 59.8/100 (strong), 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.

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 59.8/100 · strong
Contract Quality 19.2 / 25
Developer Ergonomics 8.7 / 20
Commercial Clarity 8.4 / 20
Operational Transparency 5.8 / 13
Governance 9.5 / 12
Discoverability 8.2 / 10
Agent readiness — 47/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract derived 2.5 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics documented 4.0 / 8
Request/Response Examples partial 3.5 / 7
Rate-Limit Signaling documented 3.5 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Supaglue Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Supaglue'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/supaglue/"
   title="Supaglue on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/supaglue.svg"
       alt="Supaglue Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Supaglue

Each block below is one kind of artifact we hold for Supaglue. 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 40

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.

Supaglue Accounts API

The `Account` Common Object represents a "company" in CRMs.

Supaglue Associations API

The Associations API from Supaglue — 1 operation(s) for associations.

Supaglue AssociationSchemas API

An `Association Schema` is an object describing an association between two entities.

Supaglue Attachments API

The Attachment object is used to represent an attachment for a ticket.

Supaglue Collections API

The Collection object is used to represent collections of tickets. Collections may include other collections as sub collections.

Supaglue Comments API

The Comment object is used to represent a comment on a ticket.

Supaglue Connections API

A `Connection` represents a Customer's connection to a Provider.

Supaglue ConnectionSyncConfigs API

A `ConnectionSyncConfig` is a configuration for how to sync a specific Customer's data from a Provider to a Destination on a schedule.

Supaglue Contacts API

The `Contact` Common Object represents a "contact" in CRMs.

Supaglue Customers API

A `Customer` represents one of your customers.

Supaglue CustomObjects API

A `Custom Object` is an instance of a `Custom Object Schema`.

Supaglue CustomObjectSchemas API

A `Custom Object Schema` is an object schema defined by the user.

Supaglue Destinations API

A `Destination` is a data store where we write data in your infrastructure.

Supaglue Entities API

An [`Entity`](https://docs.supaglue.com/platform/entities/overview) allows you to represent your application data models in Supaglue so customers can map their different Provide...

Supaglue EntityMappings API

An [`Entity Mapping`](https://docs.supaglue.com/platform/entities/overview#entity-mapping) maps an [Entity](https://docs.supaglue.com/platform/entities/overview) to a customer's...

Supaglue Leads API

The `Lead` Common Object represents a "potential customer" in CRMs.

Supaglue Lists API

The `List` Object represents a collection of CRM records.

Supaglue Magic Links API

A `Magic Link` is a secure URL that allows your customers to connect their accounts to Supaglue.

Supaglue Mailboxes API

The `Mailbox` Common Object is used to represent email mailbox, used within the application for sending and syncing emails.

Supaglue Opportunities API

The `Opportunity` Common Object represents a "deal opportunity" in CRMs.

Supaglue Properties API

A `Property` is a field in a Provider Object.

Supaglue Providers API

A `Provider` is a third-party SaaS tool we can connect to (e.g. Salesforce).

Supaglue SchemaMappings API

A `Schema Mapping` is a mapping between a [Schema](https://docs.supaglue.com/platform/objects/overview#schemas) field and fields in your customer's Provider object.

Supaglue Schemas API

A [`Schema`](https://docs.supaglue.com/platform/objects/overview#schemas) allows you to normalize fields for customers across a single Provider object. Supaglue uses Schemas for...

Supaglue Sequence States API

The `Sequence State` Common Object represents the state of a contact in a sequence, commonly known as a "sequence membership".

Supaglue Sequences API

The `Sequence` Common Object represents a "sequence" in Engagements.

Supaglue StandardObjects API

The StandardObjects API from Supaglue — 2 operation(s) for standardobjects.

Supaglue StandardObjectSchemas API

A `Standard Object Schema` is an object schema of a standard object type supported by the provider.

Supaglue SyncConfigs API

A `SyncConfig` is a configuration for how to sync your Customers' data from a Provider to a Destination on a schedule.

Supaglue SyncRuns API

A `SyncRun` is a single execution of a Sync at a point in time.

Supaglue Syncs API

A `Sync` is a way for a Customer to sync data from a Provider to a Destination on a schedule.

Supaglue Tags API

The Tag object is used to represent a tag or label for a ticket.

Supaglue Teams API

The Team object is used to represent a team within the company receiving the ticket.

Supaglue Tickets API

The Ticket object is used to represent a ticket or a task within a system.

Supaglue Users API

The `User` Common Object represents a "user" that can log in to CRMs.

Supaglue Actions API

The Actions API is Supaglue's escape hatch: sendPassthroughRequest forwards a raw method, path, headers, query and body to the customer's native third-party provider API using t...

Supaglue Data Listing API

The Data Listing API exposes provider-native record listings — Salesforce accounts and contacts, HubSpot companies and contacts — read straight from the Managed Destination rath...

Supaglue Unified Enrichment API

The Unified Enrichment API provides a single enrichPerson operation across enrichment providers (Clearbit, 6sense, ZoomInfo), returning a normalized person record for an email a...

Supaglue Unified Marketing Automation API

The Unified Marketing Automation API lists a provider's forms, reads a form's field definitions, and submits a form on behalf of a customer — one contract across marketing-autom...

Supaglue Metadata API

The Metadata API lists a provider's standard objects, custom objects and properties. Two of its three operations are explicitly marked deprecated in favour of the equivalents on...

Scroll within the panel for all 40 ·

Open Collections 45

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 COLLECTION

Unified CRM Accounts API

OPEN COLLECTION

Actions API

OPEN COLLECTION

Unified CRM API

OPEN COLLECTION

Data Listing API

OPEN COLLECTION

Unified Engagement API

OPEN COLLECTION

Unified Enrichment API

OPEN COLLECTION

Management API

OPEN COLLECTION

Unified Enrichment API

OPEN COLLECTION

Metadata API

OPEN COLLECTION

Scroll within the panel for all 45 ·

Pricing 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.

Supaglue Rate Limits

0 limits

RATE LIMITS

FinOps 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.

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.

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.

Supaglue Context

0 classes · 22 properties

JSON-LD

Spectral 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.

Supaglue API Rules

5 rules · 4 warnings

SPECTRAL

Supaglue API Rules

10 rules · 4 warnings

SPECTRAL

JSON Schema 1

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.

Supaglue CRM Contact

15 properties

JSON SCHEMA

JSON Structure 1

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.

Supaglue Crm Structure

0 properties

JSON STRUCTURE

Examples 1

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.

Security 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.

Supaglue Authentication

apiKey · 1 scheme

SECURITY

Supaglue Domain Security

TLSv1.3

SECURITY

Supaglue Vulnerability Disclosure

security.txt · contact published

SECURITY

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.

Supaglue Agentic Access

139 operations · 65 acting

139 operations · 65 acting

AGENTIC

Resources

Every other property we hold for Supaglue — 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

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Build 3

SDKs, sample code, and the tooling you integrate with

Operate 3

Status, limits, changes, and where to get help

Company 2

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/supaglue · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Supaglue, 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.