Fluid Schema Modeling

How to define structured schemas that are stored and validated via high-speed persistence segments.

Field Type	JSON Value	Use Case
text	\"text\	Short strings, labels, slugs
Richtext	\"Richtext\	HTML content blocks
Markdown	\"Markdown\	Markdown-formatted content
Number	\"Number\	Integers and floats
Boolean	\"Boolean\	True/false flags
Date	\"Date\	ISO 8601 timestamps
Image	\"Image\	Asset URLs
Url	\"Url\	External links
Json	\"Json\	Nested objects or arrays

Technical Specification Matrix

Scroll for overflow context →

Schema Field Rules

Field names must be alphanumeric with underscores only. System-reserved names (id, slug, data, status) cannot be used as field names.

Industrial Validation

All incoming content is validated against your schema on every write. Invalid payloads are rejected with a 422 response and a field-specific error path.

Automatic Validation Engine

The platform uses Zod under the hood to validate every schema definition and every content entry. You get type-safety guarantees without writing any validation logic yourself.

Refreshed: 2026-04-06T12:27

Logic Architect: Vishwanath Hatti

Improve this documentation

Live Examples Pending

We are currently synchronizing the live edge delivery nodes. Soon you can test these APIs in real-time.