Jellyfish
Jellyfish is a software engineering intelligence (SEI) platform that turns data from developer tools — issue trackers (Jira, Linear, Azure Boards), source control and CI/CD (GitHub, Azure DevOps), and AI coding assistants (Claude Code, Cursor, GitHub Copilot, Amazon Q, Gemini Code Assist) — into productivity and business-impact insights for R&D leaders. The platform measures AI adoption, engineering allocation, and delivery across the software development lifecycle through a Data Hub, extensible dashboards, and AI-assisted custom queries. Jellyfish is an enterprise, demo-gated product with no public self-service API; data access is delivered through the product and its integrations rather than a documented developer API. Backed by Accel, Insight Partners, and Wing Venture Capital.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Jellyfish the way a machine reads it — 3 machine-readable artifacts, 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 — Jellyfish scores 19.4/100 (emerging), with a separate agent-readiness read of 0/100 (human only). 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 Jellyfish
Each block below is one kind of artifact we hold for Jellyfish. 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.
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.
Jellyfish Trust Center
SOC 1 Type II, SOC 2 Type II, ISO 27001, CSA STAR, GDPR, NIST Cybersecurity Framework
SECURITYResources
Every other property we hold for Jellyfish — 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
Access & Security 5
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/jellyfish · machine-readable index on apis.io