$HEADLESS SYSTEMS
03 / Scorecard / Communications

Loops

F
Headless Index
25/100
denominator 60
JAIRF
N/A
Verified
MAY 21, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

Editorial verdict
Loops is not built for machine consumption today. The Headless Index thesis-fit score of 25/100 fails the floor checks of the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier are not built for machine consumption today: agents can poke at them, but the dashboard remains the source of truth, and the rest of this verdict explains where Loops lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Loops is founder-focused transactional and marketing email with a clean REST API for contacts, transactional emails, events, and mailing lists. SDKs in Node and Python plus an embedded SDK for in-app notifications. The product positioning is explicit: every dashboard action is API-equivalent because the dashboard is for marketers and the API is for engineers.[1] Schema observability is the related test: can an agent introspect the contract from cold, or does it have to read prose documentation to do so? REST documented at loops.so/docs. A public OpenAPI URL is not prominently exposed; the SDK code generation pattern implies an internal spec.[2] Driving this product through an agent is not realistic with the current surface: the API exists, but it is not the contract the vendor optimises for. On headless operability: On headless operability, the docs crawl did not produce topic coverage sufficient to score programmatic setup, billing, teams, schema, or CLI workflows. A targeted AI review pass should visit the vendor's docs index and confirm what programmatic surfaces actually exist.[3] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No first-party Loops MCP server. The product is email infrastructure; agent integration is community-led. The Loops API would slot into MCP-driven product analytics workflows readily.[4] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. On webhooks and events, the docs crawler did not locate a webhooks reference page or events catalog. Editorial review should confirm whether the vendor publishes events at all, and if so whether signing and replay are documented. Net assessment: Loops fails the floor checks of the methodology, with MCP posture[5] as the most acute gap. Any agent integration here will be brittle and short-lived until the vendor invests in machine-readable surfaces. Not currently suitable for agent consumption.
Verdict by Headless Index pipeline (auto)
// AI-drafted from the evidence layer. Editorial review pending.
Scores

Scorecard detail

Headless Index · 5 sub-criteria
API-first design intent10/20
scored

Loops is founder-focused transactional and marketing email with a clean REST API for contacts, transactional emails, events, and mailing lists. SDKs in Node and Python plus an embedded SDK for in-app notifications. The product positioning is explicit: every dashboard action is API-equivalent because the dashboard is for marketers and the API is for engineers.

signals (6)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −OpenAPI specNot found across 18 probe paths
  • −GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
  • ·SDKs maintained2 (go, javascript); top by stars: loops-so/loops-js (7 stars)
  • +SDK recency2 of 2 SDK repos pushed within 30 days (most recent SDK commit: 2026-05-19)
  • ·npm weekly downloads1 across published packages; top: loops-js @ 1/week
cite (5)
  • openapi.probes_tried@2026-05-20
  • graphql.probes_tried@2026-05-20
  • github.sdks@2026-05-20
  • freshness.most_recent_sdk_commit@2026-05-20
  • github.sdks@2026-05-20
Headless operationUnknown
Unknown

Contacts, properties, custom events, transactional templates, and audience management are all programmable. The Loops dashboard handles content authoring and segmentation; the API handles delivery and identity. Documentation explicitly addresses programmatic operation.

signals (9)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −API operations exposedNo OpenAPI spec; operations count unknown
  • ·Docs pages crawled0 pages (crawler: none)
  • ·Auth schemes documentedAuth documentation page not reached by crawler
  • ·Setup / quickstart docsNot reached by crawler
  • ·Billing docsNot reached by crawler
  • ·Teams / org docsNot reached by crawler
  • ·CLI docsNot reached by crawler
  • ·Schema / data model docsNot reached by crawler
cite (8)
  • openapi.operations_count@2026-05-20
  • docs.pages_crawled@2026-05-20
  • docs.pages_crawled@2026-05-20
  • docs.topics_found.setup@2026-05-20
  • docs.topics_found.billing@2026-05-20
  • docs.topics_found.teams@2026-05-20
  • docs.topics_found.cli@2026-05-20
  • docs.topics_found.schema@2026-05-20
MCP & agent posture0/20
scored

No first-party Loops MCP server. The product is email infrastructure; agent integration is community-led. The Loops API would slot into MCP-driven product analytics workflows readily.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −Official MCP serverNone found in vendor's GitHub org or the official MCP registry
  • −Community MCP serversNone found
  • +Agent-friendly SDKs1 TS/JS SDKs available; top: loops-js (1/week downloads)
cite (3)
  • mcp.registry_query@2026-05-20
  • mcp.github_search_query@2026-05-20
  • github.sdks@2026-05-20
Schema observability5/20
scored

REST documented at loops.so/docs. A public OpenAPI URL is not prominently exposed; the SDK code generation pattern implies an internal spec.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • −OpenAPINot discovered across 18 standard probe paths
  • −GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)
cite (2)
  • openapi.probes_tried@2026-05-20
  • graphql.probes_tried@2026-05-20
Webhooks & eventsUnknown
Unknown

Loops webhooks deliver email events (sent, delivered, opened, clicked, bounced, complained) with HMAC signing. Catalog is appropriate for the transactional email use case.

signals (2)
  • +AI review appliedReviewer: Editorial review on 2026-05-20
  • ·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.
cite (1)
  • docs.pages_crawled@2026-05-20
JAIRF · 6 dimensions
JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Powered by JAIRF v1.0.0 by Jentic

Band rationale:F band triggered: HeadlessIndex=25

04 / Embed

Show Loops's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Loops mini badge preview
Get embed code
Peers in Communications
ZendeskF
Headless Index 25/100
BrevoF
Headless Index 13/100
MessageBird (Bird)C
Headless Index 43/100
See full Communications ranking →