Markdown is the source
Models, methods, APIs, pipelines and providers are all written as natural-language Markdown. Optional frontmatter such as method: POST is allowed, never required.
Features
Everything the spec guarantees.
Every capability below comes straight from the spec.
Folder-based routing
Entry points live at api/{definition}/{version}/{feature}/{feature}.md and route to /{definition}/{version}/{feature}. Versions are path-only (v1, v2…). v1 supports HTTP GET, POST, PUT and DELETE.
Reviewed lock files
Every source compiles to a structured .lock.md. Locks that touch security items always need human confirmation, bound to the commit hash; high-risk changes need two non-author approvers.
Signed manifest, serverless runtime
Confirmed locks are merged into one signed manifest. Requests run with a cold start (p95 target under 1 second), and the runtime never reads source Markdown.
Deterministic validation
An independent validator checks lock integrity, routing, pipelines and auth, providers, RLS and public access. The compiler has no network or tool access, and its model snapshot is pinned via a compiler hash.
Account security built in
Refresh tokens rotate on every use and reuse revokes the whole family. Access tokens last at most 1 hour. Passwords need 12+ characters and a breached-password check. Five failures in 15 minutes lock an account.
Tenant isolation
PostgreSQL providers by default with row-level security. DDL and TRUNCATE are forbidden in locks, and public writes are limited by quotas, field allow-lists and audit logs.
Operations
RFC 9110 status codes, a single error body format, structured logs, and an emergency kill switch that disables an endpoint within 30 seconds (p99) without redeploying.