Nixpacks

Nixpacks Build Plan

The Nixpacks build plan is the JSON representation of how a source directory will be turned into a container image. A plan declares the list of providers used, top-level `variables`, `staticAssets`, `buildImage`, and an ordered set of phases (`setup`, `install`, `build`, plus any provider- or user-defined phases) along with a `start` phase. Each phase carries `cmds`, `nixPkgs`, `nixLibs`, `nixOverlays`, `nixpkgsArchive`, `aptPkgs`, `dependsOn`, `cacheDirectories`, `onlyIncludeFiles`, and `paths`. Plans can be saved and replayed via `nixpacks build --plan plan.json` to guarantee reproducible image builds.

GitHub

Documentation

📖
Documentation
https://nixpacks.com/docs/how-it-works

Other Resources

🔗
Reference
https://nixpacks.com/docs/configuration/file

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API 
curl "https://apis.io/api/v1/apis/build-plan"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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

API entry from apis.yml

apis.yml Raw ↑ 
aid: nixpacks:build-plan
name: Nixpacks Build Plan
description: The Nixpacks build plan is the JSON representation of how a source directory will be turned
  into a container image. A plan declares the list of providers used, top-level `variables`, `staticAssets`,
  `buildImage`, and an ordered set of phases (`setup`, `install`, `build`, plus any provider- or user-defined
  phases) along with a `start` phase. Each phase carries `cmds`, `nixPkgs`, `nixLibs`, `nixOverlays`,
  `nixpkgsArchive`, `aptPkgs`, `dependsOn`, `cacheDirectories`, `onlyIncludeFiles`, and `paths`. Plans
  can be saved and replayed via `nixpacks build --plan plan.json` to guarantee reproducible image builds.
humanURL: https://nixpacks.com/docs/how-it-works
tags:
- Build Plan
- JSON
- Phases
- Reproducible Builds
properties:
- type: Documentation
  url: https://nixpacks.com/docs/how-it-works
- type: Reference
  url: https://nixpacks.com/docs/configuration/file