API referenceInstance API
GUIDE & REFERENCE

Lineage

Every registered lineage instance operation, with source-derived inputs, outputs, access policy, and errors.

This reference covers 5 HTTP operations registered by the Akasha daemon. Call these paths on your instance base URL. See authentication, errors, and coverage before integrating.

MethodPathOperation
POST/v1/lineage/graphLineage graph
GET/v1/lineage/nodes/:idLineage node get
POST/v1/lineage/impactLineage impact
POST/v1/lineage/verifyLineage verify
GET/v1/lineage/statsLineage stats

POST /v1/lineage/graph

Query the graph for a lineage subgraph starting from an optional root node. POST /v1/lineage/graph

AvailabilitySource contract
Registrationconfig.enable_graph
Runtime serviceNo prefix-level service check; handler dependencies still apply.
Handler dependenciesSee handler source and return expressions.

Access: Daemon authentication and capability namespace authority; memory-domain permissions apply where mapped.

Request

JsonLineageGraphReq

FieldRust typeRequired on inputNotes
root_idOption<String>No; optional or defaulted
depthOption<u32>No; optional or defaulted
struct LineageGraphReq {
    root_id: Option<String>,
    depth: Option<u32>,
}

JSON field accesses in handler: id, label, lineage_type, relationship, source, target. Nested lookups are included; this list alone does not establish requiredness.

Response

Declared return: Result<impl IntoResponse, DaemonError>

The following are the exact JSON construction expressions in the handler. Values such as rows, result, and delegated types are runtime values, not literal example payloads.

serde_json::json!(resp)

Errors and validation

Directly referenced error variants: InvalidRequest. Middleware and delegated services can return additional errors described in the shared error reference.

Source: akasha-daemon/src/lineage.rs:100. Registration: akasha-daemon/src/lineage.rs:367.

GET /v1/lineage/nodes/:id

Get a single lineage node by its ID. GET /v1/lineage/nodes/:id

AvailabilitySource contract
Registrationconfig.enable_graph
Runtime serviceNo prefix-level service check; handler dependencies still apply.
Handler dependenciesSee handler source and return expressions.

Access: Daemon authentication and capability namespace authority; memory-domain permissions apply where mapped.

Request

PathString

{
  "type": "string"
}

JSON field accesses in handler: id, label, lineage_type. Nested lookups are included; this list alone does not establish requiredness.

Response

Declared return: Result<impl IntoResponse, DaemonError>

The following are the exact JSON construction expressions in the handler. Values such as rows, result, and delegated types are runtime values, not literal example payloads.

serde_json::json!({"node": node})

Errors and validation

Directly referenced error variants: InvalidRequest. Middleware and delegated services can return additional errors described in the shared error reference.

Source: akasha-daemon/src/lineage.rs:172. Registration: akasha-daemon/src/lineage.rs:368.

POST /v1/lineage/impact

Count downstream nodes affected by a given lineage node via graph traversal. POST /v1/lineage/impact

AvailabilitySource contract
Registrationconfig.enable_graph
Runtime serviceNo prefix-level service check; handler dependencies still apply.
Handler dependenciesSee handler source and return expressions.

Access: Daemon authentication and capability namespace authority; memory-domain permissions apply where mapped.

Request

JsonLineageImpactReq

FieldRust typeRequired on inputNotes
node_idStringYes
struct LineageImpactReq {
    node_id: String,
}

JSON field accesses in handler: id. Nested lookups are included; this list alone does not establish requiredness.

Response

Declared return: Result<impl IntoResponse, DaemonError>

The following are the exact JSON construction expressions in the handler. Values such as rows, result, and delegated types are runtime values, not literal example payloads.

serde_json::json!(resp)

Errors and validation

Directly referenced error variants: InvalidRequest. Middleware and delegated services can return additional errors described in the shared error reference.

Source: akasha-daemon/src/lineage.rs:223. Registration: akasha-daemon/src/lineage.rs:369.

POST /v1/lineage/verify

Compute a SHA-256 hash of a lineage node's content for integrity verification. POST /v1/lineage/verify

AvailabilitySource contract
Registrationconfig.enable_graph
Runtime serviceNo prefix-level service check; handler dependencies still apply.
Handler dependenciesSee handler source and return expressions.

Access: Daemon authentication and capability namespace authority; memory-domain permissions apply where mapped.

Request

JsonLineageVerifyReq

FieldRust typeRequired on inputNotes
node_idStringYes
struct LineageVerifyReq {
    node_id: String,
}

JSON field accesses in handler: integrity_hash. Nested lookups are included; this list alone does not establish requiredness.

Response

Declared return: Result<impl IntoResponse, DaemonError>

The following are the exact JSON construction expressions in the handler. Values such as rows, result, and delegated types are runtime values, not literal example payloads.

serde_json::json!(resp)

Errors and validation

Directly referenced error variants: Internal, InvalidRequest. Middleware and delegated services can return additional errors described in the shared error reference.

Source: akasha-daemon/src/lineage.rs:264. Registration: akasha-daemon/src/lineage.rs:370.

GET /v1/lineage/stats

Aggregate counts of lineage nodes and edges from the graph. GET /v1/lineage/stats

AvailabilitySource contract
Registrationconfig.enable_graph
Runtime serviceNo prefix-level service check; handler dependencies still apply.
Handler dependenciesSee handler source and return expressions.

Access: Daemon authentication and capability namespace authority; memory-domain permissions apply where mapped.

Request

No typed JSON, query, or path extractor is declared in the handler signature. Headers or request objects may still be consumed; the signature below is authoritative. JSON field accesses in handler: relationship, type. Nested lookups are included; this list alone does not establish requiredness.

Response

Declared return: Result<impl IntoResponse, DaemonError>

The following are the exact JSON construction expressions in the handler. Values such as rows, result, and delegated types are runtime values, not literal example payloads.

serde_json::json!(resp)

Errors and validation

Directly referenced error variants: InvalidRequest. Middleware and delegated services can return additional errors described in the shared error reference.

Source: akasha-daemon/src/lineage.rs:321. Registration: akasha-daemon/src/lineage.rs:371.

On this page