Sequel
Sequel is a webinar and virtual-event platform for data-driven marketing teams. It runs live, simulive, and on-demand event experiences directly on a company's own domain, capturing unified first-party engagement data (watch time, polls, questions, CTA clicks) and syncing it to CRMs like Salesforce, HubSpot, Marketo, and Pardot. Sequel exposes a REST API (the Introvoke API) for managing companies, events, presenters, organizers, registrants, networking hubs, customization/theming, analytics, simulive video, MediaHub assets, and webhooks, plus pre-built embeddable video/networking components, a JavaScript SDK, and an official hosted MCP server that gives AI agents read access to webinar transcripts for content repurposing.
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 Sequel the way a machine reads it — 16 machine-readable artifacts across 12 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 — Sequel scores 52.5/100 (developing), with a separate agent-readiness read of 61/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 Sequel
Each block below is one kind of artifact we hold for Sequel. 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 12
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.
Sequel Analytics API
The Analytics API from Sequel — 2 operation(s) for analytics.
Sequel Client API
The Client API from Sequel — 2 operation(s) for client.
Sequel company API
Calls to managing companies
Sequel company theme API
The company theme API from Sequel — 1 operation(s) for company theme.
Sequel company theme fonts API
The company theme fonts API from Sequel — 2 operation(s) for company theme fonts.
Sequel company theme overrides API
The company theme overrides API from Sequel — 1 operation(s) for company theme overrides.
Sequel event API
Calls to managing events
Sequel event theme API
The event theme API from Sequel — 1 operation(s) for event theme.
Sequel event theme overrides API
The event theme overrides API from Sequel — 1 operation(s) for event theme overrides.
Sequel Media API
The Media API from Sequel — 2 operation(s) for media.
Sequel networking API
Calls to managing networking hubs
Sequel platform API
The platform API from Sequel — 2 operation(s) for platform.
Scroll within the panel for all 12 ·
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.
sequel-mcp.yml
MCP SERVEREvent 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.
Sequel Webhooks
ASYNCAPISecurity 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.
Resources
Every other property we hold for Sequel — 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 2
Reference material describing how the API behaves
Agent Surfaces 5
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 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/sequel · machine-readable index on apis.io