# Get an engram

Its claims are a list of their own: [List an engram's claims](https://augenta.pages.dev/docs/api-reference/list-engram-claims.md).

## GET `/v1/engrams/{id}`

Its claims are a list of their own: GET /v1/engrams/{id}/claims.

## Authentication

Use an API key with the AugentaKey authorization scheme. See [Authentication](https://augenta.pages.dev/docs/authentication.md).

## Request example

```bash
curl --fail-with-body --get "https://api.augenta.ai/v1/engrams/$AUGENTA_ENGRAM_ID" \
  -H "Authorization: AugentaKey $AUGENTA_API_KEY" \
  --data-urlencode "workspace=$AUGENTA_WORKSPACE_ID"
```

## Parameters

<a id="request-parameters-id"></a>

### `request.parameters.id`

`string` · required

path parameter.

<a id="request-parameters-workspace"></a>

### `request.parameters.workspace`

`string` · optional

query parameter. One assigned Workspace. Required for keys with multiple assignments; inferred for one.

## Response 200

The shared Engram resource emitted by Consolidate and resource lists; Recall context blocks have a separate renderer contract.

Content-Type: `application/json`

```json
{
  "object": "engram",
  "id": "eng_000000000000000000000001",
  "summary": "Production releases require owner approval.",
  "label": "production · approval",
  "labelSupport": 1,
  "memoryClass": "semantic",
  "status": "active",
  "strength": 1.5,
  "heatShare": 0.25,
  "claimCount": 1,
  "claimTokenCount": 7,
  "bornAt": "2026-10-28T12:00:00.000Z",
  "updatedAt": "2026-10-28T12:00:00.000Z",
  "claims": {
    "object": "list",
    "data": [
      {
        "object": "claim",
        "id": "clm_000000000000000000000001",
        "text": "Production releases require owner approval.",
        "experience": "exp_000000000000000000000001",
        "at": "2026-10-28T12:00:00.000Z"
      }
    ],
    "nextPageUrl": null
  }
}
```

<a id="response-200-object"></a>

### `response.200.object`

`string` · always present

The resource type. Always engram. Use this field to recognize Engram objects in API results.

Allowed values: `"engram"`.

<a id="response-200-id"></a>

### `response.200.id`

`string` · always present

The ID Augenta assigns to this Engram, starting with `eng_`. In a Workspace, put this value in `GET /v1/engrams/{id}` to retrieve it. A one-shot Engram exists only in that result and has no standalone lookup URL. See [Engram IDs](https://augenta.pages.dev/docs/engrams.md#engram-ids) for examples and how IDs behave as memory changes.

<a id="response-200-summary"></a>

### `response.200.summary`

`string | null` · conditional

A readable summary of the Claims grouped in this Engram. Use it to display what the Engram is about. It can change as Claims or summary text change. Null when no summary is available; omitted when summaries:false is requested.

<a id="response-200-label"></a>

### `response.200.label`

`string | null` · conditional

A short topic label, such as releases · rollback, for display in lists. Augenta chooses terms that distinguish this Engram from others in the same Workspace or one-shot result. An empty string means no terms qualified; null means a label is unavailable. Omitted with summaries:false.

<a id="response-200-labelsupport"></a>

### `response.200.labelSupport`

`number | null` · conditional

How widely the label's terms appear in this Engram's Claims. For each term, Augenta calculates the share of Claims containing it, then averages those shares. Ranges from 0 to 1: at 1, every label term appears in every Claim. It is not confidence in the label's accuracy. Null when unavailable; omitted with summaries:false.

Minimum: `0`. Maximum: `1`.

<a id="response-200-memoryclass"></a>

### `response.200.memoryClass`

`string | null` · always present

The kind of content Augenta identified. Common values are `semantic` for facts, `episodic` for past events, `procedural` for how-to knowledge and `prospective` for commitments or future tasks. This does not select one-shot or Workspace mode. Null when unavailable.

<a id="response-200-status"></a>

### `response.200.status`

`string | null` · always present

The Engram's recorded state. `weakened` means its strength fell below half its recorded peak; it can return to `active` when its strength recovers. This describes retained memory, not Experience processing progress. Null when unavailable.

Allowed values: `"active"`, `"weakened"`, `null`.

<a id="response-200-strength"></a>

### `response.200.strength`

`number | null` · always present

A score describing the structural support for this Engram's group of Claims. Larger values indicate a stronger grouping under the memory process's scoring rules; this is not a probability or a measure of factual correctness. One-shot scores describe its last rebuild; Workspace scores come from its persisted memory history. Compare within the same memory, not across modes. Null when unavailable.

<a id="response-200-heatshare"></a>

### `response.200.heatShare`

`number | null` · always present

A relative activity measure: this Engram's share of the memory's recorded activity signal, called heat. Ranges from 0 to 1; 0.25 means one quarter of that memory's heat at the last evaluation. Workspace heat reflects incoming Claims and recorded recall activity; one-shot heat has no recorded recall activity. This is not confidence or billing usage. Null when unavailable.

Minimum: `0`. Maximum: `1`.

<a id="response-200-claimcount"></a>

### `response.200.claimCount`

`integer` · always present

The total number of Claims currently in this Engram. Use it to show the size of the group. It can exceed claims.data.length because only one page may be loaded; Claims that have left the Engram are excluded.

Minimum: `0`.

<a id="response-200-claimtokencount"></a>

### `response.200.claimTokenCount`

`integer | null` · always present

The total number of text tokens in this Engram's current Claims, excluding its summary. It describes content size, not tokens billed for a request or the size of your eventual model prompt. Null when unavailable.

Minimum: `0`.

<a id="response-200-bornat"></a>

### `response.200.bornAt`

`string | null` · always present

When this Engram ID was first published, as an ISO-8601 timestamp. It is not the date of the oldest source Claim. Null when the publication time is unknown for older memory.

<a id="response-200-updatedat"></a>

### `response.200.updatedAt`

`string | null` · always present

When the Engram's Claim membership or summary text last changed, as an ISO-8601 timestamp. A summary written after consolidation can advance it. Reads and changes only to scores, status or labels do not. It is not a version for the entire object. Null when the content-change time is unknown.

<a id="response-200-claims"></a>

### `response.200.claims`

`object` · conditional

A page of Claims currently in this Engram. Read claims.data for the statements and follow claims.nextPageUrl for more. Workspace detail and completed-memory results load an initial page by default; list requests need include=claims. An omitted field means Claims were not loaded, not that the Engram is empty.

<a id="response-200-claims-object"></a>

### `response.200.claims.object`

`string` · always present

The collection type. Always list.

Allowed values: `"list"`.

<a id="response-200-claims-data"></a>

### `response.200.claims.data`

`array<value>` · always present

Claims loaded on this page. A short or empty page can still have a continuation.

<a id="response-200-claims-data-object"></a>

### `response.200.claims.data.object`

`string` · always present

The resource type. Always claim.

Allowed values: `"claim"`.

<a id="response-200-claims-data-id"></a>

### `response.200.claims.data.id`

`string` · always present

The ID Augenta assigns to this statement, starting with clm\_. Use it to match a Claim in extractedClaims.data with the same Claim in an Engram's claims.data. It belongs to the Workspace or one-shot result that returned it.

<a id="response-200-claims-data-text"></a>

### `response.200.claims.data.text`

`string` · always present

The statement extracted from your source, such as Production releases require owner approval. Read this field for the Claim's content. Claims do not have labels.

<a id="response-200-claims-data-experience"></a>

### `response.200.claims.data.experience`

`string | null` · always present

The id of the Experience this Claim came from. In Workspace mode, use it with GET /v1/experiences/{id} to check processing status. Null means the source could not be identified for an older Claim.

<a id="response-200-claims-data-at"></a>

### `response.200.claims.data.at`

`string` · always present

When this statement was observed in its source, as an ISO-8601 timestamp. This is not the time you fetched the Claim.

<a id="response-200-claims-data-source"></a>

### `response.200.claims.data.source`

`object` · conditional

Additional source details, such as a conversation session or document path, when available. The fields depend on how the source was submitted. Omitted when no source details are available.

<a id="response-200-claims-nextpageurl"></a>

### `response.200.claims.nextPageUrl`

`string | null` · always present

Follow this relative URL unchanged. Null means there is no next page. One-shot output can still omit items when truncated is true.

<a id="response-200-claims-url"></a>

### `response.200.claims.url`

`string` · conditional

The collection's resource path, when available. Use nextPageUrl, rather than this path, to load the next page.

<a id="response-200-claims-truncated"></a>

### `response.200.claims.truncated`

`boolean` · conditional

True when a bounded one-shot result omitted items. One-shot results have no browsing continuation; use Workspace-backed memory when you need subsequent retrieval. False means all selected items were returned. Workspace lists use nextPageUrl instead.

<a id="response-200-claims-billing"></a>

### `response.200.claims.billing`

`object` · conditional

Present when billing is enabled. USD amount is exact. Receipt references settle only on successful server delivery; retries reuse the original debit.

<a id="response-200-claims-billing-operationid"></a>

### `response.200.claims.billing.operationId`

`string` · always present

<a id="response-200-claims-billing-priceversion"></a>

### `response.200.claims.billing.priceVersion`

`string` · always present

<a id="response-200-claims-billing-sourcetokens"></a>

### `response.200.claims.billing.sourceTokens`

`integer` · always present

Minimum: `0`.

<a id="response-200-claims-billing-memorytokens"></a>

### `response.200.claims.billing.memoryTokens`

`integer` · always present

Minimum: `0`.

<a id="response-200-claims-billing-measuredmemorytokens"></a>

### `response.200.claims.billing.measuredMemoryTokens`

`integer` · always present

Minimum: `0`.

<a id="response-200-claims-billing-replayed"></a>

### `response.200.claims.billing.replayed`

`boolean` · always present

<a id="response-200-claims-billing-complimentary"></a>

### `response.200.claims.billing.complimentary`

`boolean` · conditional

<a id="response-200-claims-billing-ratedamount"></a>

### `response.200.claims.billing.ratedAmount`

`string` · conditional

<a id="response-200-claims-billing-amount"></a>

### `response.200.claims.billing.amount`

`string` · always present

<a id="response-200-claims-billing-receiptids"></a>

### `response.200.claims.billing.receiptIds`

`array<string>` · always present

<a id="response-200-billing"></a>

### `response.200.billing`

`object` · conditional

Present when billing is enabled. USD amount is exact. Receipt references settle only on successful server delivery; retries reuse the original debit.

<a id="response-200-billing-operationid"></a>

### `response.200.billing.operationId`

`string` · always present

<a id="response-200-billing-priceversion"></a>

### `response.200.billing.priceVersion`

`string` · always present

<a id="response-200-billing-sourcetokens"></a>

### `response.200.billing.sourceTokens`

`integer` · always present

Minimum: `0`.

<a id="response-200-billing-memorytokens"></a>

### `response.200.billing.memoryTokens`

`integer` · always present

Minimum: `0`.

<a id="response-200-billing-measuredmemorytokens"></a>

### `response.200.billing.measuredMemoryTokens`

`integer` · always present

Minimum: `0`.

<a id="response-200-billing-replayed"></a>

### `response.200.billing.replayed`

`boolean` · always present

<a id="response-200-billing-complimentary"></a>

### `response.200.billing.complimentary`

`boolean` · conditional

<a id="response-200-billing-ratedamount"></a>

### `response.200.billing.ratedAmount`

`string` · conditional

<a id="response-200-billing-amount"></a>

### `response.200.billing.amount`

`string` · always present

<a id="response-200-billing-receiptids"></a>

### `response.200.billing.receiptIds`

`array<string>` · always present

## Response 400

Invalid cursor, filter, limit or missing Workspace for a person or a key with multiple assignments.

Content-Type: `application/json`

<a id="response-400-error"></a>

### `response.400.error`

`object` · always present

<a id="response-400-error-code"></a>

### `response.400.error.code`

`string` · always present

Stable. The Errors page lists every code.

<a id="response-400-error-message"></a>

### `response.400.error.message`

`string` · always present

Human-readable. May change; don't parse it.

<a id="response-400-error-retryable"></a>

### `response.400.error.retryable`

`boolean` · always present

<a id="response-400-error-retryafterseconds"></a>

### `response.400.error.retryAfterSeconds`

`integer` · conditional

Capacity retry interval, also present as Retry-After before stream headers commit. SSE error events retain this field after HTTP 200 is committed.

Minimum: `1`.

<a id="response-400-error-billingurl"></a>

### `response.400.error.billingUrl`

`string` · conditional

Top-up action when error.code is insufficient_balance (HTTP 402).

<a id="response-400-requestid"></a>

### `response.400.requestId`

`string` · always present

The request's id, as in the `X-Request-Id` response header.

## Response 401

Authentication required; revoked credentials are refused.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 402

insufficient_balance: add credits before reading billable memory.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 403

Workspace access denied or Connector disabled.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 404

Workspace or engram not found.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 409

Workspace archived, or cursor_stale: a new fold changed the list snapshot; restart without a cursor.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 429

rate_limited: retry after the Retry-After header.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 500

An internal failure; quote the requestId.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 502

Cognition failed or returned an invalid response.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 503

Cognition is unavailable or unconfigured.

Content-Type: `application/json`

Response fields use the same schema as Response 400.
