Define the schema
Zod v4 is the source for runtime validation, TypeScript types, and the generated OpenAPI 3.1 contract.
FENICE starts where repeated backend setup usually ends: typed contracts, authentication, agent discovery, observability, adapters, validation, and a guarded AI builder already working together.
Schema
Zod v4
Contract
OpenAPI 3.1
Agents
MCP discovery
Trace
OpenTelemetry
Position / 01
AI-native should not mean a chat layer added after launch. In FENICE, schemas, documentation, agent discovery, observability, and guarded generation are part of the system contract from the beginning.
Foundation / 02
Zod v4 is the source for runtime validation, TypeScript types, and the generated OpenAPI 3.1 contract.
JWT access and refresh flows, role checks, rate limits, timeouts, redaction, and adapter boundaries are built into the baseline.
MCP discovery and LLM-readable documentation let agents understand the API without a second, drifting integration layer.
OpenTelemetry traces the system; AI-generated changes pass through planning, approval, scope checks, validation, and pull requests.
Platform / 03
Hono, Zod v4, MongoDB, Mongoose, OpenAPI, and Scalar documentation share a deliberate contract.
MCP discovery and Markdown API documentation make capabilities legible to both developers and agents.
Structured logs, request correlation, OpenTelemetry, health endpoints, and WebSocket projection are present from day one.
Natural-language changes are planned, approved, limited by scope policy, validated, repaired once, and proposed through a PR.
Current state / 04
“Production-ready” describes the engineering baseline and validation discipline. FENICE is an open foundation to deploy and adapt, not a Formray-hosted SaaS service.
Clone the platform, inspect the decisions, and adapt the parts that belong in your own system.