decisions

Graduate a pending memory via explicit confirmation

Records the authenticated caller's project-credential context against one scoped pending memory and updates its confirmation state. API and MCP authentication identify the project credential, not the end user named by user_id; the customer host authenticates that person and retains any end-user attestation. Call recall_for_action again after confirmation because policy still determines act, ask, or abstain. Confirmation does not prove objective truth. Partition ownership is enforced at the store layer: a memory ID outside the caller's org/project/user scope returns 404, indistinguishable from a missing one.

post/v1/confirm

Request

  • Base URL: https://api.contextdb.ai
  • URL: https://api.contextdb.ai/v1/confirm
  • Auth: HTTP bearer

Headers

Idempotency-Keystring

Project-scoped retry key (8-128 URL-safe characters). The same key and canonical payload replay the encrypted stored response. Reusing a key with a different route or payload returns 409. On extract_memories this applies only when mode is commit.

Request body

user_idstring required

End-user memory partition key. Not an identity assertion.

memory_idstring required

Response

The confirmed memory

memory_versioninteger required

Monotonic consistency version within one organization/project.

primary_wal_lsnstring nullable required

Primary PostgreSQL WAL position observed after commit.

Changes

No recorded changes to this operation across all 1 revision of this API.