Turborepo

Turborepo is a high-performance build system for JavaScript and TypeScript codebases, built by Vercel and written in Rust. It accelerates monorepo development by orchestrating task pipelines with explicit dependency graphs, hashing task inputs to skip redundant work, and caching task outputs locally and remotely so the same build/lint/test never runs twice across developers and CI. The project ships the turbo CLI (turbo run, prune, watch, boundaries, ls, query, generate, login, link, telemetry) plus an open Remote Cache HTTP API specification that any server can implement — Vercel's Remote Cache is the reference, and community implementations enable fully self-hosted caching. Turborepo is MIT-licensed open source at github.com/vercel/turborepo.

Turborepo publishes 2 API contracts indexed on the APIs.io network: Analytics API and Artifacts API. Tagged areas include Build Systems, Monorepo, JavaScript, TypeScript, and Caching.

The Turborepo catalog on APIs.io includes 1 Spectral governance ruleset.

Turborepo’s developer surface includes authentication, developer portal, documentation, getting-started guide, engineering blog, changelog, code examples, and 28 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

36.0/100 thin ▬ flat Agent 20/100 agent aware Heartbeat 98/100 alive saas · MIT License Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 21 Features

Build Systems Monorepo JavaScript TypeScript Caching Open Source Rust Vercel Developer Tools CI/CD

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Software Release & Deployment Management

BC-4210

Artifacts

GET /artifacts/{hash} PUT /artifacts/{hash}

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 36.0/100 · thin

Contract Quality 10.2 / 19

Developer Ergonomics 7.5 / 15

Access Clarity 1.6 / 15

Operational Transparency 3.1 / 10

Contract Governance 1.2 / 9

Discoverability 4.3 / 8

Regulatory Posture 1.8 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 20/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/turborepo/"><img src="https://apis.io/badge/turborepo/card.svg" alt="Turborepo on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 10.5 — up to +17.9 composite points
Contract Quality scores 54.5 — up to +11.4 composite points
Contract Governance scores 13.6 — up to +10.4 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/turborepo/apis.yml: open an issue on github.com/api-evangelist/turborepo to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Turborepo Analytics API

Operations for recording cache usage analytics

Turborepo Artifacts API

Operations for managing cache artifacts

Open Collections 3

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Turborepo Remote Cache analytics API

OPEN COLLECTION

Turborepo Remote Cache analytics artifacts API

OPEN COLLECTION

Turborepo Remote Cache API

OPEN COLLECTION

Features 21

Notable capabilities this provider offers.

High-performance build system for JavaScript and TypeScript monorepos, written in Rust

Task pipeline orchestration with dependsOn graphs (turbo run build, lint, test)

Content-addressable local caching of task outputs

Remote Caching with shared artifact store across teammates and CI

Open Remote Cache API specification — any HTTP server can implement it

Vercel Remote Cache as the reference implementation (api.vercel.com)

Self-hosted remote cache compatible (ducktors/turborepo-remote-cache, brunojppb/turbo-cache-server)

Package manager support — npm, pnpm, Yarn, Bun

turbo prune for shipping minimal monorepo subsets to Docker/production

turbo watch for single-process dependency-aware task watching

turbo boundaries for enforcing architectural rules between packages

turbo query — GraphQL queries over monorepo structure

turbo ls for listing packages and dependencies

turbo gen scaffolding for new apps and packages

turbo-ignore helper for CI skip-build decisions based on affected packages

Codemods via turbo-codemod for upgrading between major versions

VS Code extension (turbo-vsc) and ESLint plugin/config

Telemetry CLI (turbo telemetry enable/disable/status) with anonymous opt-out

Login flow (turbo login, turbo link, turbo unlink) for Remote Cache provider auth

turbo bin and turbo docs helper commands

MIT licensed, open source on GitHub (vercel/turborepo)

Scroll for all 21

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Turborepo API Rules

67 rules · 62 errors 1 warnings 4 info

SPECTRAL

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Turborepo Authentication

http · 1 scheme

SECURITY

Turborepo Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Turborepo Agentic Access

6 operations · 2 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

Portal

Portal

GettingStarted

GettingStarted

Documentation 10

Reference material describing how the API behaves

Documentation

Documentation

Documentation

Documentation

Documentation

Documentation

Documentation

Documentation

Documentation

Documentation

Scroll for all 10

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Build 9

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

SourceCode

CodeOfConduct

Package

Package

Package

Package

Package

CodeExamples

Scroll for all 9

Access & Security 4

Authentication, authorization, and security posture

DomainSecurity

Authentication

SecurityPolicy

Authentication

Operate 2

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

Forums

Forums

Commercial 2

Pricing, plans, and the legal terms of use

License

License

Pricing

Pricing

Company 3

The organization behind the API

Website

Website

Blog

Blog

BlueSky

BlueSky

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: turborepo
url: https://raw.githubusercontent.com/api-evangelist/turborepo/refs/heads/main/apis.yml
apis:
- aid: turborepo:turborepo-analytics-api
  name: Turborepo Analytics API
  description: Operations for recording cache usage analytics
  humanURL: https://turborepo.dev/docs/core-concepts/remote-caching
  tags:
  - Analytics
  tags_raw:
  - analytics
  properties:
  - type: OpenAPI
    url: openapi/turborepo-analytics-api-openapi.yml
  - type: Documentation
    url: https://turborepo.dev/docs/core-concepts/remote-caching
  - type: Documentation
    url: https://turborepo.dev/docs/openapi
- aid: turborepo:turborepo-artifacts-api
  name: Turborepo Artifacts API
  description: Operations for managing cache artifacts
  humanURL: https://turborepo.dev/docs/core-concepts/remote-caching
  tags:
  - Artifacts
  tags_raw:
  - artifacts
  properties:
  - type: OpenAPI
    url: openapi/turborepo-artifacts-api-openapi.yml
  - type: Documentation
    url: https://turborepo.dev/docs/core-concepts/remote-caching
  - type: Documentation
    url: https://turborepo.dev/docs/openapi
name: Turborepo
tags:
- Build Systems
- Monorepo
- JavaScript
- TypeScript
- Caching
- Open Source
- Rust
- Vercel
- Developer Tools
- CI/CD
tags_raw:
- Build System
- Monorepo
- JavaScript
- TypeScript
- Caching
- Open Source
- Rust
- Vercel
- Developer Tools
- CI/CD
- Open-Source
kind: contract
deliveryModel:
  model: saas
  license: MIT License
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - license
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/turborepo.png
access: 3rd-Party
common:
- type: CapabilityMap
  url: capabilities/turborepo-capability-edges.yml
  name: Turborepo Business Capability Map
- type: Website
  url: https://www.turborepo.dev/
- type: AgenticAccess
  url: agentic-access/turborepo-agentic-access.yml
- type: DomainSecurity
  url: security/turborepo-domain-security.yml
- type: Authentication
  url: authentication/turborepo-authentication.yml
- url: https://turborepo.dev
  type: Portal
- url: https://turborepo.dev/docs
  type: Documentation
- url: https://turborepo.dev/docs/getting-started/installation
  type: GettingStarted
- url: https://turborepo.dev/docs/reference/configuration
  name: turbo.json Configuration Reference
  type: Documentation
- url: https://turborepo.dev/docs/reference
  name: CLI Reference
  type: Documentation
- url: https://turborepo.dev/docs/core-concepts/remote-caching
  name: Remote Caching
  type: Documentation
- url: https://turborepo.dev/docs/crafting-your-repository
  name: Crafting Your Repository
  type: Documentation
- url: https://turborepo.dev/docs/telemetry
  name: Telemetry
  type: Documentation
- url: https://turborepo.dev/blog
  type: Blog
- url: https://turborepo.dev/showcase
  name: Showcase
  type: Documentation
- url: https://github.com/vercel/turborepo
  type: GitHubOrganization
- url: https://github.com/vercel/turborepo
  name: Turborepo (vercel/turborepo)
  type: SourceCode
- url: https://github.com/vercel/turborepo/releases
  type: ChangeLog
- url: https://github.com/vercel/turborepo/blob/main/LICENSE
  name: MIT License
  type: License
- url: https://github.com/vercel/turborepo/blob/main/SECURITY.md
  type: SecurityPolicy
- url: https://github.com/vercel/turborepo/blob/main/CODE_OF_CONDUCT.md
  type: CodeOfConduct
- url: https://github.com/vercel/turborepo/blob/main/CONTRIBUTING.md
  name: Contributing Guide
  type: Documentation
- url: https://www.npmjs.com/package/turbo
  name: turbo on npm
  type: Package
- url: https://www.npmjs.com/package/create-turbo
  name: create-turbo on npm
  type: Package
- url: https://www.npmjs.com/package/eslint-config-turbo
  name: eslint-config-turbo
  type: Package
- url: https://www.npmjs.com/package/eslint-plugin-turbo
  name: eslint-plugin-turbo
  type: Package
- url: https://www.npmjs.com/package/turbo-ignore
  name: turbo-ignore
  type: Package
- url: https://github.com/vercel/turborepo/tree/main/examples
  name: Examples
  type: CodeExamples
- url: https://vercel.com/docs/monorepos/turborepo
  name: Turborepo on Vercel
  type: Documentation
- url: https://vercel.com/docs/monorepos/remote-caching
  name: Remote Caching on Vercel
  type: Documentation
- url: https://vercel.com/pricing
  name: Vercel Pricing (Remote Cache)
  type: Pricing
- url: https://vercel.com/account/tokens
  name: Vercel Tokens
  type: Authentication
- url: https://github.com/vercel/turborepo/discussions
  type: Forums
- url: https://x.com/turborepo
  type: X
- url: https://bsky.app/profile/turborepo.com
  type: BlueSky
- type: Features
  data:
  - High-performance build system for JavaScript and TypeScript monorepos, written in Rust
  - Task pipeline orchestration with dependsOn graphs (turbo run build, lint, test)
  - Content-addressable local caching of task outputs
  - Remote Caching with shared artifact store across teammates and CI
  - Open Remote Cache API specification — any HTTP server can implement it
  - Vercel Remote Cache as the reference implementation (api.vercel.com)
  - Self-hosted remote cache compatible (ducktors/turborepo-remote-cache, brunojppb/turbo-cache-server)
  - Package manager support — npm, pnpm, Yarn, Bun
  - turbo prune for shipping minimal monorepo subsets to Docker/production
  - turbo watch for single-process dependency-aware task watching
  - turbo boundaries for enforcing architectural rules between packages
  - turbo query — GraphQL queries over monorepo structure
  - turbo ls for listing packages and dependencies
  - turbo gen scaffolding for new apps and packages
  - turbo-ignore helper for CI skip-build decisions based on affected packages
  - Codemods via turbo-codemod for upgrading between major versions
  - VS Code extension (turbo-vsc) and ESLint plugin/config
  - Telemetry CLI (turbo telemetry enable/disable/status) with anonymous opt-out
  - Login flow (turbo login, turbo link, turbo unlink) for Remote Cache provider auth
  - turbo bin and turbo docs helper commands
  - MIT licensed, open source on GitHub (vercel/turborepo)
  sources:
  - https://turborepo.dev/
  - https://turborepo.dev/docs
  - https://turborepo.dev/docs/core-concepts/remote-caching
  - https://github.com/vercel/turborepo
  - https://turborepo.dev/api/remote-cache-spec
  updated: '2026-05-25'
created: '2026-05-25T00:00:00.000Z'
modified: '2026-05-25'
position: Consuming
description: Turborepo is a high-performance build system for JavaScript and TypeScript codebases, built by Vercel and written
  in Rust. It accelerates monorepo development by orchestrating task pipelines with explicit dependency graphs, hashing task
  inputs to skip redundant work, and caching task outputs locally and remotely so the same build/lint/test never runs twice
  across developers and CI. The project ships the turbo CLI (turbo run, prune, watch, boundaries, ls, query, generate, login,
  link, telemetry) plus an open Remote Cache HTTP API specification that any server can implement — Vercel's Remote Cache
  is the reference, and community implementations enable fully self-hosted caching. Turborepo is MIT-licensed open source
  at github.com/vercel/turborepo.
maintainers:
- FN: Kin Lane
  email: info@apievangelist.com
  X: apievangelist
  url: https://apievangelist.com
specificationVersion: '0.23'

Turborepo API — frequently asked questions

Does Turborepo have an API?

Yes. APIs.io lists 2 APIs from Turborepo, including Turborepo Analytics API and Turborepo Artifacts API.

Is there an OpenAPI specification for the Turborepo API?

Yes. APIs.io indexes 2 OpenAPI specifications for Turborepo, each linked for download from this page.

How do I authenticate with the Turborepo API?

Turborepo uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Turborepo Authentication.

Is the Turborepo API ready for AI agents?

Turborepo has a Kin Score of 36.0 out of 100 (thin) and an Agent Readiness score of 20.2 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/turborepo"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/turborepo/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/turborepo/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.