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
Gradle website screenshot

Gradle

Gradle Inc. (Gradle Technologies) is the company behind the open-source Gradle Build Tool, downloaded more than 25 million times a month across the Java, JVM, Android, Kotlin, C/C++, and native ecosystems, and Develocity (formerly Gradle Enterprise), its commercial Developer Productivity Engineering platform. Develocity adds Build Scan, Build Cache, Predictive Test Selection, and Test Distribution to accelerate and stabilize builds and tests. The Develocity API is a JSON REST API, described with OpenAPI, that provides programmatic access to build data, failures, tests, projects, project groups, Build Cache node configuration, Test Distribution agent pools, and short-lived access tokens on a self-hosted Develocity instance. Founded in 2009 and headquartered in San Francisco with offices in Berlin and Melbourne, Gradle raised a $27M Series C led by Triangle Peak Partners.

agent ready

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.

Kin Score

API Evangelist profiles Gradle the way a machine reads it — 16 machine-readable artifacts across 11 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 — Gradle scores 58.5/100 (developing), with a separate agent-readiness read of 58/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.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 58.5/100 · developing
Contract Quality 15.3 / 25
Developer Ergonomics 16.1 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 7.2 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 58/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 15
MCP Server 12 / 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 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 3 / 3

How we profile Gradle

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

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.

Gradle Auth API

Endpoints related to Develocity authentication and authorization. The permissions required for these endpoints vary. Consult the endpoint descriptions.

Gradle BuildCache API

Endpoints related to configuring the Build Cache nodes of the Develocity instance. To access these endpoints the user requires the `Configure Build Caching` permission.

Gradle Builds API

Endpoints related to retrieving details of a build from the Develocity instance. To access these endpoints the user requires the `Access build data via the API` permission.

Gradle Comparison API

Endpoints for comparing two builds to identify differences in work unit inputs, dependencies, and other dimensions. To access these endpoints the user requires the `Access build...

Gradle Develocity API

All endpoints of the Develocity API.

Gradle Failures API

Endpoints related to retrieving details about failures of builds from the Develocity instance. To access these endpoints the user requires the `Access build data via the API` pe...

Gradle GradleEnterprise API

**This tag is deprecated, use `Develocity` instead**. All endpoints of the Develocity API.

Gradle Meta API

Endpoints related to the Develocity installation and its state.

Gradle Projects API

Endpoints related to the management of project-level access control in Develocity. To access these endpoints the user requires the `Administer Projects` permission. **Beta...

Gradle TestDistribution API

Endpoints related to the management of Test Distribution resources. To access these endpoints the user requires the `Admin` permission.

Gradle Tests API

Endpoints related to retrieving details of tests of the Develocity instance. To access these endpoints the user requires the `Access build data via the API` permission. The Deve...

Scroll within the panel for all 11 ·

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.

gradle-mcp.yml

MCP SERVER

Security Posture 4

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.

Gradle Authentication

http · 1 scheme

SECURITY

Gradle Domain Security

TLSv1.3 · DMARC

SECURITY

Gradle Vulnerability Disclosure

security.txt · contact published

SECURITY

Gradle Trust Center

SOC 2 Type 1, SOC 2 Type 2

SECURITY

Resources

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

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Build 4

SDKs, sample code, and the tooling you integrate with

Commercial 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

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