# Get an experience

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

Where one experience stands: `accepted` → `processed` → `consolidated`, or `failed`.

## 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 -X GET "https://api.augenta.ai/v1/experiences/$AUGENTA_EXPERIENCE_ID" \
  -H "Authorization: AugentaKey $AUGENTA_API_KEY"
```

## Parameters

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

### `request.parameters.id`

`string` · required

path parameter.

## Response 200

The experience's status.

Content-Type: `application/json`

```json
{
  "id": "exp_9b2f6c1e4d7a0b3c5e8f1a2d",
  "type": "doc",
  "workspace": "ws-platform",
  "status": "processed",
  "acceptedAt": "2026-10-14T09:30:00.000Z",
  "processedAt": "2026-10-14T09:30:41.000Z",
  "experienceId": "handbook-deploys:doc:handbook_deploys.md-1a2b3c4d:p0@9f2c5b7e1d0a4c3b",
  "claimCount": 3
}
```

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

### `response.200.object`

`string` · always present

Allowed values: `"experience"`.

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

### `response.200.id`

`string` · always present

The ID Augenta assigns to this submitted source. In Workspace mode, use it with GET /v1/experiences/{id} to check processing status. One-shot source references have no stored status URL.

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

### `response.200.status`

`string` · always present

accepted: the source is stored and waiting for processing. processed: its Claims have been extracted and stored; Recall can search them even before they form an Engram. consolidated: a Workspace consolidation has covered those Claims. failed: processing could not complete; read error. Acceptance or a bounded wait does not promise immediate consolidation.

Allowed values: `"accepted"`, `"processed"`, `"consolidated"`, `"failed"`.

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

### `response.200.billingOperationId`

`string` · conditional

Reference to this source's billing operation, when billing is enabled.

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

### `response.200.claimIds`

`array<string>` · conditional

IDs of Claims extracted from this source, when returned. Read extractedClaims.data or an Engram's claims.data for their text.

<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

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

### `response.200.type`

`string` · always present

The kind of source submitted: for example, trajectory for a conversation or agent run, or doc for a document.

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

### `response.200.workspace`

`string` · always present

The ID of the Workspace storing this Experience.

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

### `response.200.acceptedAt`

`string` · always present

When Augenta accepted and stored this source.

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

### `response.200.processedAt`

`string` · conditional

When processing completed, if it has finished.

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

### `response.200.consolidatedAt`

`string` · conditional

When consolidation covered this Experience, if it has been consolidated.

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

### `response.200.experienceId`

`string` · conditional

An additional processing reference, when available. Use id, the exp\_ identifier, in public resource URLs.

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

### `response.200.claimCount`

`integer` · conditional

How many claims were extracted, once processed.

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

### `response.200.error`

`object` · conditional

Why it failed. Present only when `status` is `failed`.

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

### `response.200.error.code`

`string` · always present

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

### `response.200.error.message`

`string` · always present

## Response 401

`unauthenticated`: missing, invalid or revoked credential.

Content-Type: `application/json`

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

### `response.401.error`

`object` · always present

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

### `response.401.error.code`

`string` · always present

Stable. The Errors page lists every code.

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

### `response.401.error.message`

`string` · always present

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

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

### `response.401.error.retryable`

`boolean` · always present

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

### `response.401.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-401-error-billingurl"></a>

### `response.401.error.billingUrl`

`string` · conditional

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

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

### `response.401.requestId`

`string` · always present

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

## Response 403

`connector_inactive`: the key's Connector is disabled.

Content-Type: `application/json`

Response fields use the same schema as Response 401.

## Response 404

`experience_not_found`: no experience with this id that your credential can see.

Content-Type: `application/json`

```json
{
  "error": {
    "code": "experience_not_found",
    "message": "no such experience",
    "retryable": false
  },
  "requestId": "req_7f9c2b1e-6d0a-4b7e-9a51-2f0c8e7d4a10"
}
```

Response fields use the same schema as Response 401.

## Response 429

`rate_limited` (retryable): wait the number of seconds in `Retry-After`. `at_capacity` (retryable): the service is temporarily full; wait the same way.

Content-Type: `application/json`

```json
{
  "error": {
    "code": "rate_limited",
    "message": "rate limit exceeded",
    "retryable": true
  },
  "requestId": "req_7f9c2b1e-6d0a-4b7e-9a51-2f0c8e7d4a10"
}
```

Response fields use the same schema as Response 401.

## Response 500

`internal_error`: an unexpected failure; quote the `requestId`.

Content-Type: `application/json`

Response fields use the same schema as Response 401.

## Response 503

`workos_unavailable` (retryable).

Content-Type: `application/json`

Response fields use the same schema as Response 401.
