# DayPilot UI Builder Public API

> Anonymous discovery, validation, and stateless project generation for the subset that DayPilot UI Builder can configure and generate.

This catalog is not a complete taxonomy of DayPilot product capabilities. Absence from Builder discovery does not mean that a feature is unsupported by DayPilot.

## Canonical resources

- Service index: https://builder.daypilot.org/api/v1
- OpenAPI contract: https://builder.daypilot.org/openapi.json
- Arazzo discovery workflow: https://builder.daypilot.org/arazzo.json
- Canonical settings schema: https://builder.daypilot.org/schema/builder-settings-v1.json
- Strict project schema: https://builder.daypilot.org/schema/builder-project-v1.json
- API catalog: https://builder.daypilot.org/.well-known/api-catalog
- Service health: https://builder.daypilot.org/healthz
- Human documentation: https://builder.daypilot.org/

## Agent workflow

Discover a component, edition, target, and canonical option IDs. POST the strict project specification to https://builder.daypilot.org/api/v1/configurations/validate, retain its projectDigest, then POST the same specification plus expectedProjectDigest to https://builder.daypilot.org/api/v1/project-archives for the direct ZIP response.

A validation response with `valid: true` means configuration resolution and immutable generation-tree preflight succeeded. It does not certify dependency installation, dependency security, build, lint, tests, or browser runtime for the generated project.

The workflow is anonymous and creates no saved configuration or project resource. The two POST resources deliberately grant no browser CORS permission and can be disabled by the service index operation flags. Generated artifacts retain their Lite or Pro license and notice material; generation does not grant a DayPilot Pro production license.

Use the OpenAPI document and JSON Schemas as the machine contracts. This file is only a supplemental discovery pointer and does not define executable behavior.