API
REST interface design · Examples only · No live server
These endpoints describe the intended API surface. No backend is implemented on hextai.com.
REST Endpoints
GET /api/v1/objects/{id}
Retrieve a HEXT object by identity.
GET /api/v1/objects/rfc-nvp18
Accept: application/hext+xml
200 OK
Content-Type: application/hext+xml GET /api/v1/objects/{id}?format=json
JSON transport projection.
{
"spec_version": "2.2.0",
"object": {
"id": "rfc-nvp18",
"type": "document.rfc",
"registry_ref": "gmm://rfc/NVP18"
},
"provenance": { "agency": { "human_touch": 0.81 } },
"ledger": [ { "t": 1750291200, "type": "HUMAN", "hash": "sha256:..." } ],
"final_seal": { "sealed_at": "2026-06-19T15:00:00Z", "state_hash": "sha256:..." },
"evidence": { "format": "text/markdown", "body": "# RFC..." }
} POST /api/v1/validate
POST /api/v1/validate
Content-Type: application/hext+xml
→ { "status": "ok", "state_hash": "sha256:...", "step_count": 2 } POST /api/v1/crystallize
POST /api/v1/crystallize
Content-Type: application/json
{
"evidence": { "format": "text/markdown", "body": "# Draft" },
"provenance": { "agency": { "primary_generator": "human" } }
}
→ application/hext+xml Content Types
| Type | Role |
|---|---|
application/hext+xml | Canonical |
application/hext+json | Transport projection |
text/markdown | Authoring import |