Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Cask website screenshot

Cask

Cask Data, Inc. was the enterprise big-data startup, backed by Andreessen Horowitz, that built and open-sourced CDAP — the Cask Data Application Platform — a framework for building and running data analytic applications and data pipelines on Hadoop, Spark, Kubernetes, and the cloud. Cask was acquired by Google Cloud; CDAP continues as an Apache-2.0 open source project under the github.com/cdapio organization and powers Google Cloud Data Fusion. CDAP's programmatic surface is its HTTP RESTful "Microservices" API — 21 documented service families (Lifecycle, Artifact, Metadata, Metrics, Logging, Namespace, Pipeline, Preferences, Profile, Provisioners, Replication, Reports, Security, Service, Workflow, Monitor, Dashboard, Configuration, Transaction Service, System Workers) served under a /v3 path prefix from a self-hosted CDAP router, with Bearer access tokens issued by the CDAP authentication server. The company's own cask.co domain and developer portal are gone; the surviving surfaces are cdap.io, the CDAP documentation wiki, the cdapio GitHub organization, and the io.cdap.cdap / co.cask.cdap artifact groups on Maven Central.

agent aware

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles Cask the way a machine reads it — 14 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 — Cask scores 30.1/100 (thin), with a separate agent-readiness read of 21/100 (agent aware). 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-07-27 · rubric v0.5
Composite quality — 30.1/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 14.3 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 2.7 / 13
Governance 0.0 / 12
Discoverability 8.8 / 10
Agent readiness — 21/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3

How we profile Cask

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

CDAP Microservices API

The CDAP HTTP RESTful API, documented as "Microservices". All endpoints sit under a /v3 path prefix on a self-hosted CDAP router (default port 11015, or 10443 when SSL is enable...

CDAP Lifecycle Microservices

Deploy, start, stop, and manage the lifecycle of CDAP applications and the programs they contain within a namespace.

CDAP Artifact Microservices

Manage CDAP artifacts — the packaged application and plugin JARs that applications are created from — including deployment, versioning, and plugin inspection.

CDAP Metadata Microservices

Search, annotate, and retrieve business and technical metadata and lineage for CDAP entities such as applications, datasets, programs, and fields.

CDAP Metrics Microservices

Query the metrics CDAP collects for system and user programs, including time-series queries across metric contexts and tags.

CDAP Logging Microservices

Retrieve and download logs emitted by CDAP system services and by user applications and programs, with filtering by time range and log level.

CDAP Namespace Microservices

Create, list, and delete CDAP namespaces — the multi-tenancy boundary that isolates applications, datasets, and metadata. The cdap, default, and system namespaces are reserved.

CDAP Pipeline Microservices

Programmatically create, deploy, run, and inspect CDAP data pipelines (the Hydrator / Data Fusion pipeline application type) and their plugin configurations.

CDAP Replication Microservices

Manage CDAP replication (change data capture) jobs that stream changes from source databases into analytic targets such as BigQuery.

CDAP Security Microservices

Manage CDAP secure store keys and authorization privileges, roles, and policies for principals operating against a security-enabled CDAP cluster.

CDAP Workflow Microservices

Inspect and control CDAP workflows — multi-node program orchestration — including run records, node states, local datasets, and workflow tokens.

CDAP Preferences Microservices

Read and write preferences — the hierarchical configuration key/value pairs resolved across the instance, namespace, application, and program scopes.

Scroll within the panel for all 12 ·

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.

Cask Authentication

http · 1 scheme

SECURITY

Cask Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

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

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Build 4

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 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

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