ENYAL by Greenland AI

Get one entity's STRUCTURE by name_hash (SHA-256 of the normalised name). No content.

Get one entity's DECRYPTED content by name_hash (SHA-256 of the normalised name). Content scope required (403 otherwise).

Get a node's DECRYPTED content by name_hash PLUS its connected nodes' content (neighbour depth, default 1; 0–5). Same plan schema as the structure tools. Content scope required (403).

Temporally-ordered STRUCTURE view, optionally filtered by node_type and an ISO8601 date range. No content.

Temporally-ordered DECRYPTED content view, optionally filtered by node_type + an ISO8601 date range. Same plan schema as get_timeline. Content scope required (403 otherwise).

Execute a structured query plan over your encrypted knowledge graph. Returns STRUCTURE ONLY (node_type, name_hash, relationships, chunk_ids, timestamps) — never content. Plan schema: { "entity_filters": [{"node_type": <type>} | {"name_hash": <sha256-hex>}], "edge_filters": [{"relationship": <rel>, "direction": "out"|"in"|"both"}], "temporal_bounds":{"valid_from_after": <ISO8601>, "valid_to_before": <ISO8601>}, "limit": <int <= 200>, "include_neighbours_depth": <0-5> } node_type in {entity, concept, decision, person, organisation, event, source, synthesis}. relationship in {references, contradicts, supports, supersedes, caused_by, related_to, part_of, informed_by, led_to, verifies}. Account scope is enforced server-side; it cannot be set from the plan.

Execute a structured query plan and return DECRYPTED memory CONTENT (node names, summaries, properties; edge evidence + endpoint names) alongside structure. SAME plan schema as query_memory. REQUIRES a memory:read:content-scoped token — a structure-only token is rejected (403) by ENYAL. Account scope is enforced server-side; it cannot be set from the plan.

Render a structured query as a STRUCTURE-ONLY result set (β = structure; identical shape to query_memory). Reserved for richer rendering when content access (γ) lands.

Look up one identifier in ENYAL's PUBLIC verification index (relays GET /api/v1/verify/lookup/{id}; no decryption). ENYAL's answer is returned unchanged: `found`, and for a chunk or proof its `anchor_status` with `bsv_tx_id`; for a txid, `chain_status`. `degraded:true` means a source could not be checked (inconclusive, not an absence). ENYAL's route needs no key; calling it through this server still needs your eyl_ bearer, like every tool call. An id that is not a UUID or hex is refused (invalid_id) and nothing is sent.