Ingestion Pipeline
Ingest Episode
Store a conversation episode as remembered turns (tex.episodes.store).
The messages go through the SAME path as POST /ingestion/memory (conversations.remember): each message is a turn in the active tier (recallable at once) and a durable turn node, in one active-memory episode that is later consolidated into an EPISODE_SUMMARY — which is what GET /episodes lists. It used to be forwarded to the ingestion service's /ingest/episode, which stored it as a document: not recallable until that job ran, never an episode, never listed.
Request shape unchanged. Mapping onto turns:
- content (or text) -> turn text; role user/human -> user, assistant/ai/agent/bot/model -> assistant, any other role -> an assistant turn prefixed with the role ("[system] ...");
- timestamp -> the turn's capture time (same contract as remember, natural language read in timezone, default UTC); omitted -> the arrival time, +1 ms per message, so order and identity are kept;
- the episode is episode_id, else the session id sent, else a new id (returned as episode_id);
- scope: legacy tenant dict or "<kind>:<value>", checked exactly as /ingestion/memory checks it. metadata and options (preference extraction etc.) belonged to the document pipeline and are accepted but not used.
post/ingestion/episode
Request
- Base URLhttps://api.getmetacognition.com (the document declares no server; this is the origin it was published from)
- AuthHTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Request body
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.