STATUS

API Entries is a native Chronoscript intake surface. External ingress is disabled by default and requires explicit configuration plus an API key. Control displays API Entries whether ingress is enabled or disabled.

ENDPOINT

POST /api/v1/chronoscript/submissions
Headers: X-API-Key; Idempotency-Key recommended. Content-Type: application/json. The request schema is /schemas/chronoscript-submission.schema.json.

BOUNDARY

An API request creates a NON-CANONICAL API Entry only. It cannot assign Registry Sequence, Record ID, canonical finality, registration coordinates or canonical hashes. LXKeys review and the normal Chronoscript workflow remain mandatory.

WORKFLOW

API Entry -> schema validation -> pending LXKeys review -> accept as mutable draft or reject -> normal Chronoscript validation -> explicit canonical finalization. The API Entry identity remains traceable to the draft and, after finalization, to the resulting CS-n record.

SEMANTICS

A client submits a fundamental record type and structured record data. Semantic profiles are resolved and validated by LXKeys. Versioned record relations may be supplied using the published relation registry at /api/v1/chronoscript/relations.

IDEMPOTENCY, STATUS AND ERRORS

Clients SHOULD provide an Idempotency-Key for retries. Accepted requests return a Submission/API Entry ID and payload SHA-256. Representative responses: 202 accepted; 400 invalid payload; 401 invalid/missing API key; 429 rate limit; 503 API disabled. Deployment limits are published by the active service configuration.

AUTHORITY

API compatibility never confers canonical issuance authority. A third-party site cannot create a CS-n directly. Relation names record declared relationships and do not by themselves determine legal effect.