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.
Gradle publishes 9 APIs on the APIs.io network, including Auth API, BuildCache API, Builds API, and 6 more. Tagged areas include Company, Developer Tools, Build Automation, Developer Productivity, and CI/CD.
Gradle’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, signup flow, authentication, and 27 more developer resources.
Kin Score
APIs 9
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 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 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 for all 9
Open Collections 12
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONDevelocity Auth API
OPEN COLLECTIONDevelocity Auth BuildCache API
OPEN COLLECTIONDevelocity Auth Builds API
OPEN COLLECTIONDevelocity Auth Comparison API
OPEN COLLECTIONAuth Develocity API
OPEN COLLECTIONDevelocity Auth Failures API
OPEN COLLECTIONDevelocity Auth GradleEnterprise API
OPEN COLLECTIONDevelocity Auth Meta API
OPEN COLLECTIONDevelocity Auth Projects API
OPEN COLLECTIONDevelocity Auth TestDistribution API
OPEN COLLECTIONDevelocity Auth Tests API
OPEN COLLECTIONScroll for all 12
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Gradle MCP Server
Develocity ships official Model Context Protocol servers that give AI agents access to Develocity build data and analytics. Because Develocity is self-hosted, the MCP server is ...
MCP SERVERSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
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
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll for all 7
Operate 4
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
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.