Assert one relation between a blob and another anchor

POST

/api/blobs/{id}/relations

Maintainer:Not configured

OperationId:relate_blob

The edge homes on the BLOB's home anchor — the blob-scoped surface answers to the
blob's standing — and the peer must be readable by the caller (

endpoint_readable_
by_profile

), so a relation can never point at an anchor the caller cannot see. Gate
train, in order: blob readable → 404; home authorable → 403; peer readable → 404.
Retraction rides the incumbent fold endpoint; relations come and go individually.

Request

Authorization

JWT Bearer

Add the parameter

Authorization

to Headers

Example:

Authorization: ********************

Path Params

Header Params

Body Params application/jsonRequired

Examples

Responses

🟢200OK

application/json

Relation asserted (idempotent — re-asserting the same edge returns its handle)

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Record Not Found

Request Example

Shell

JavaScript

Java

Swift

curl --location '/api/blobs//relations' \
--header 'X-Temper-Surface;' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "confidence": null,
    "correlation_id": null,
    "invocation_id": null,
    "model": "string",
    "persona": "string",
    "rationale": "string",
    "reasoning": "string",
    "direction": "blob_as_source",
    "edge_kind": "express",
    "label": "string",
    "peer_id": "118d4485-cd94-4ecd-b71e-80f79647bc58",
    "peer_table": "string",
    "polarity": "forward",
    "weight": 0
}'

Response Example

200 - Example 1

{
    "edge_handle": "bb448575-c4c7-45c7-a1a2-a9946535e7cb"
}

Modified at 2026-09-16 12:46:48

List the edges incident to a blob — "what relates to this blob" (D3)

Slice a neighborhood within a cognitive map