Ampersand
Ampersand is a developer-first platform for building native SaaS integrations. It provides an embeddable UI component and managed infrastructure that lets developers add product integrations quickly, handling OAuth, data sync, webhooks, and field mapping out of the box. The platform supports hundreds of SaaS connectors including Salesforce, HubSpot, Marketo, Microsoft Dynamics 365, Zendesk, and Gong with bi-directional sync and declarative configuration.
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 Ampersand the way a machine reads it — 189 machine-readable artifacts across 18 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 — Ampersand scores 58.7/100 (developing), with a separate agent-readiness read of 48/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.
How we profile Ampersand
Each block below is one kind of artifact we hold for Ampersand. 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 18
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.
Ampersand API Key API
The API Key API from Ampersand — 2 operation(s) for api key.
Ampersand Billing Account API
The Billing Account API from Ampersand — 2 operation(s) for billing account.
Ampersand Connection API
The Connection API from Ampersand — 3 operation(s) for connection.
Ampersand Destination API
The Destination API from Ampersand — 6 operation(s) for destination.
Ampersand Installation API
The Installation API from Ampersand — 4 operation(s) for installation.
Ampersand Integration API
The Integration API from Ampersand — 4 operation(s) for integration.
Ampersand JWT Key API
The JWT Key API from Ampersand — 2 operation(s) for jwt key.
Ampersand Notification API
The Notification API from Ampersand — 2 operation(s) for notification.
Ampersand OAuth API
The OAuth API from Ampersand — 2 operation(s) for oauth.
Ampersand Objects & Fields API
The Objects & Fields API from Ampersand — 4 operation(s) for objects & fields.
Ampersand Operation API
The Operation API from Ampersand — 4 operation(s) for operation.
Ampersand Org API
The Org API from Ampersand — 8 operation(s) for org.
Ampersand Project API
The Project API from Ampersand — 2 operation(s) for project.
Ampersand Provider API
The Provider API from Ampersand — 2 operation(s) for provider.
Ampersand Provider App API
The Provider App API from Ampersand — 2 operation(s) for provider app.
Ampersand Revision API
The Revision API from Ampersand — 2 operation(s) for revision.
Ampersand Upload URL API
The Upload URL API from Ampersand — 1 operation(s) for upload url.
Ampersand User API
The User API from Ampersand — 2 operation(s) for user.
Scroll within the panel for all 18 ·
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.
Ampersand 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.
Ampersand Finops
FINOPSFeatures 9
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.
Declarative Integration Framework
Code-based, composable integration building that is version-controllable and CI/CD compatible for professional engineering workflows.
Managed OAuth Authentication
Free auth token management with auto-refresh for all supported SaaS providers, eliminating OAuth complexity from product teams.
Bi-directional Data Sync
On-demand read/write operations, scheduled reads, and bulk write capabilities for synchronizing data between SaaS applications.
Proxy API
Authenticated passthrough requests to customer systems enabling direct API calls without managing OAuth tokens.
Backfill Support
Historical data retrieval during customer onboarding to populate integrations with existing customer data.
DevOps Infrastructure
Automated retries, error handling, quota management, detailed logging, and alerting for production-grade integration reliability.
Custom Objects and Fields
Support for custom objects and fields allowing customers to configure integrations without being constrained by inflexible unified APIs.
Embeddable UI Components
React UI library with pre-built integration setup flows enabling customers to configure their own SaaS connections within your product.
AI SDK
Official AI SDK enabling AI agents to read from and write to SaaS applications through natural language via Ampersand integrations.
Scroll within the panel for all 9 ·
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.
Ampersand Api 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.
Ampersand API Rules
SPECTRALAmpersand API Rules
SPECTRALJSON Schema 50
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.
ApiKeyRequest
JSON SCHEMAApiKey
JSON SCHEMAApiKeyScopes
JSON SCHEMAAssociationDefinition
JSON SCHEMAAssociationLabels
JSON SCHEMABackfillProgress
JSON SCHEMABillingAccount
JSON SCHEMABuilderInfo
JSON SCHEMABuilder
JSON SCHEMAClaimedDomainResponse
JSON SCHEMAConfig
JSON SCHEMAConnectionRequest
JSON SCHEMACreateJWTKeyRequest
JSON SCHEMADestination
JSON SCHEMADestinationWithSecrets
JSON SCHEMAFieldDefinition
JSON SCHEMAFieldUpsertResult
JSON SCHEMAGenerateConnectionRequest
JSON SCHEMAHydratedRevision
JSON SCHEMAInstallation
JSON SCHEMAIntegration
JSON SCHEMAInvite
JSON SCHEMAJSONPatchOperation
JSON SCHEMAJWTKeyResponse
JSON SCHEMAJWTKey
JSON SCHEMANotificationEventTopicRoute
JSON SCHEMANotificationEventType
JSON SCHEMANumericFieldOptions
JSON SCHEMAOauth2AuthorizationCode
JSON SCHEMAOauth2AuthorizationCodeTokensOnly
JSON SCHEMAObjectMetadata
JSON SCHEMAOrg
JSON SCHEMAPaginationInfo
JSON SCHEMAPatchApiKeyRequest
JSON SCHEMAPatchJWTKeyRequest
JSON SCHEMAProject
JSON SCHEMAProviderAppMetadata
JSON SCHEMAProviderApp
JSON SCHEMAProviderMetadataInfo
JSON SCHEMAProviderMetadata
JSON SCHEMARevision
JSON SCHEMASignedUrl
JSON SCHEMAStringFieldOptions
JSON SCHEMATopicDestinationRoute
JSON SCHEMATopic
JSON SCHEMAUpdateConnectionRequest
JSON SCHEMAUpdateMask
JSON SCHEMAUpsertMetadataRequest
JSON SCHEMAUpsertMetadataResponse
JSON SCHEMAWebhookHeaders
JSON SCHEMAScroll within the panel for all 50 ·
JSON Structure 50
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.
Ampersand Api Api Key Request Structure
JSON STRUCTUREAmpersand Api Api Key Scopes Structure
JSON STRUCTUREAmpersand Api Api Key Structure
JSON STRUCTUREAmpersand Api Association Definition Structure
JSON STRUCTUREAmpersand Api Association Labels Structure
JSON STRUCTUREAmpersand Api Backfill Progress Structure
JSON STRUCTUREAmpersand Api Billing Account Structure
JSON STRUCTUREAmpersand Api Builder Info Structure
JSON STRUCTUREAmpersand Api Builder Structure
JSON STRUCTUREAmpersand Api Claimed Domain Response Structure
JSON STRUCTUREAmpersand Api Config Structure
JSON STRUCTUREAmpersand Api Connection Request Structure
JSON STRUCTUREAmpersand Api Create Jwt Key Request Structure
JSON STRUCTUREAmpersand Api Destination Structure
JSON STRUCTUREAmpersand Api Destination With Secrets Structure
JSON STRUCTUREAmpersand Api Field Definition Structure
JSON STRUCTUREAmpersand Api Field Upsert Result Structure
JSON STRUCTUREAmpersand Api Generate Connection Request Structure
JSON STRUCTUREAmpersand Api Hydrated Revision Structure
JSON STRUCTUREAmpersand Api Installation Structure
JSON STRUCTUREAmpersand Api Integration Structure
JSON STRUCTUREAmpersand Api Invite Structure
JSON STRUCTUREAmpersand Api Json Patch Operation Structure
JSON STRUCTUREAmpersand Api Jwt Key Response Structure
JSON STRUCTUREAmpersand Api Jwt Key Structure
JSON STRUCTUREAmpersand Api Notification Event Topic Route Structure
JSON STRUCTUREAmpersand Api Notification Event Type Structure
JSON STRUCTUREAmpersand Api Numeric Field Options Structure
JSON STRUCTUREAmpersand Api Oauth2 Authorization Code Structure
JSON STRUCTUREAmpersand Api Object Metadata Structure
JSON STRUCTUREAmpersand Api Org Structure
JSON STRUCTUREAmpersand Api Pagination Info Structure
JSON STRUCTUREAmpersand Api Patch Api Key Request Structure
JSON STRUCTUREAmpersand Api Patch Jwt Key Request Structure
JSON STRUCTUREAmpersand Api Project Structure
JSON STRUCTUREAmpersand Api Provider App Metadata Structure
JSON STRUCTUREAmpersand Api Provider App Structure
JSON STRUCTUREAmpersand Api Provider Metadata Info Structure
JSON STRUCTUREAmpersand Api Provider Metadata Structure
JSON STRUCTUREAmpersand Api Revision Structure
JSON STRUCTUREAmpersand Api Signed Url Structure
JSON STRUCTUREAmpersand Api String Field Options Structure
JSON STRUCTUREAmpersand Api Topic Destination Route Structure
JSON STRUCTUREAmpersand Api Topic Structure
JSON STRUCTUREAmpersand Api Update Connection Request Structure
JSON STRUCTUREAmpersand Api Update Mask Structure
JSON STRUCTUREAmpersand Api Upsert Metadata Request Structure
JSON STRUCTUREAmpersand Api Upsert Metadata Response Structure
JSON STRUCTUREAmpersand Api Webhook Headers Structure
JSON STRUCTUREScroll within the panel for all 50 ·
Examples 47
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.
Ampersand Api Config Example
EXAMPLEAmpersand Api Invite Example
EXAMPLEAmpersand Api Org Example
EXAMPLEAmpersand Api Topic Example
EXAMPLEScroll within the panel for all 47 ·
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 6
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.
CRM Integration
Build native Salesforce, HubSpot, and Dynamics 365 integrations to sync customer data bidirectionally with your SaaS product.
Marketing Automation Integration
Connect Marketo, HubSpot, and other marketing platforms to enable customer data flows for campaign automation and lead management.
Customer Support Integration
Integrate Zendesk and other support platforms to sync tickets, contacts, and customer data with your application.
Conversation Intelligence Integration
Connect Gong and other conversation platforms to access call recordings, transcripts, and insights within your application.
AI Agent Integration
Enable AI agents to read from and write to customer SaaS systems through the Ampersand AI SDK for autonomous workflow automation.
Developer Portal Embedding
Embed Ampersand's React UI components into your product so customers can self-service configure their own SaaS integrations.
Resources
Every other property we hold for Ampersand — 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 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/ampersand · machine-readable index on apis.io