Reliable Domain Modeling for Applications

Describe your data

Object types with typed fields, and relations between them. Every write is validated against its type, and the types describe your API. Over the built-in MCP server, an AI agent can build the model and its content for you.

article Object type

title text · required
body markdown
cover file
author → person

GET /api/objects/article

Decide who sees what

Give a group or an app a role on a type. To share a single object, name a person in one of its fields, and the field gives them their role. What a reader can't reach doesn't exist for them — in the admin, the API and MCP alike. An AI agent sees no more than the person it acts for.

Editorial team article editor
Website article viewer
Freelance writer named in writer editor

GET /api/objects/person → 404

Publishing is sharing

A new object starts out seen only by your team. To publish it, add the public to who sees it — the same edit that shares a draft with a client or keeps an article for members.

Hafenrundfahrt article

audience Client Public

Connect any app

An app signs in as itself with an API key, or as the person using it over OAuth and OpenID Connect — or both. Either way, it reads and writes only what it or that person has been granted.

curl -H "Authorization: Bearer rds_live_…" \
  "https://roadstead.eu/api/objects/article?locale=de"

{
  "data": [{
    "id": "0b4f…",
    "object_type": "article",
    "attributes": {
      "title": "Hafenrundfahrt",
      "data": { "title": "Hafenrundfahrt", "body": "…" }
    }
  }],
  "meta": { "count": 1, "next_cursor": null }
}

Change the schema without breaking apps

Rename or remove a field, and a pinned app keeps reading the names it was built against while new fields still reach it. Until you move it to the current names, its responses carry a Deprecation header, and any single request can try them first.

Pinned

title
author
summary

Current names

title
byline
summary

Website, pinned, still reads author

Roadstead-Contract: current

Reliable Domain Modelingfor Applications

How it works

Describe your data

Decide who sees what

Publishing is sharing

Connect any app

Change the schema without breaking apps