HTTP API · version 1
Inspect exact specifications from code.
The API resolves the canonical registry to an immutable commit, exposes searchable specification metadata and source bytes, and returns explicit yes, no, or execution-error check results.
curl https://build.hara-lang.org/api/v1/specs?executable=true&limit=20 Discovery
Start without prior configuration.
- Service
GET /api- Current version
GET /api/v1- Health
GET /api/v1/health- Capabilities
GET /api/v1/capabilities- Schema
GET /api/openapi.json
Specifications
Search, inspect, and retrieve exact bytes.
- List
GET /api/v1/specs- Inspect
GET /api/v1/specs/:identifier- Normative source
GET /api/v1/specs/:identifier/source- Documentation
GET /api/v1/specs/:identifier/documentation
Use the URL-safe slug when possible. Every resource reports the registry repository, exact commit, and path used to produce it.
Conformance
Use the same result contract as the browser.
- Document check
POST /api/v1/checks- Project validation
POST /api/v1/packages/validate- Project request type
application/edn- Project payload limit
- 256 KB
Authority boundary
Specifications do not mint identities.
hara-build validates publication material, but publisher enrollment, namespace grants, key possession, and revocation belong to the external Hara identity authority at id.hara-lang.org.
Canonical registry writes remain disabled until that authority supplies verified, path-scoped authorization.
Compatibility
Read and check integrations continue to work.
The original registry and document-check aliases remain available and return a successor-version link. New integrations and all project validation should use the version-one resources.