Set the global default compatibility via PUT /config with body {"compatibility": "BACKWARD"} using the Schema Registry REST API
Override per-subject compatibility via PUT /config/YOUR_SUBJECT with the desired mode (BACKWARD, FORWARD, FULL, NONE, or their _TRANSITIVE variants)
Register a new schema version via POST /subjects/YOUR_SUBJECT/versions with the Avro/JSON/Protobuf schema string
Test compatibility before registration with POST /compatibility/subjects/YOUR_SUBJECT/versions/latest
List all subjects with GET /subjects and inspect schema versions with GET /subjects/YOUR_SUBJECT/versions
Known gotchas
BACKWARD means new schema can read old data; FORWARD means old schema can read new data; FULL means both — choose based on which side you upgrade first
Deleting a schema version with DELETE /subjects/YOUR_SUBJECT/versions/VERSION only soft-deletes by default; pass ?permanent=true for hard delete, which cannot be undone
Schema IDs are globally unique integers assigned by the registry; never assume sequential IDs map to sequential schema versions
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp