Skip to main content
Knowledge is free-text context the agent reads before every run. Writing it down once means a run doesn’t have to rediscover — or ask your customer about — something you already know. There are two scopes, and the distinction matters: Source knowledge is shared by every migration from that source, so a quirk you document once pays off on every customer after it. Customer knowledge applies only to that migration.

Authentication

Requires an x-api-key header. See Authentication.

Read

200 OK. knowledge is null when nothing has been written yet.
The customer-scoped read is the same shape with migration_id in place of source:

Write

string
required
Replaces the whole document. Send an empty string to clear it.
string
The updated_at you last read. Supply it and a concurrent change is refused with 412 instead of being silently overwritten.
knowledge is a whole-document replace, not an append. To add a line, read the current value, append to it, and write the result back. Sending just your new line discards everything already there.

Writing safely

The agent rewrites this same field as it learns during a run, so a naive read-modify-write can clobber what it just recorded. Pass if_unmodified_since with the updated_at you read; if it moved underneath you the write is refused with 412 and you can re-read and merge:
A 409 means a run is holding the document while it writes — retry shortly.

Errors

Naming a source

{source} is the source’s name as returned by List sources — URL-encode names with spaces. If the name is ambiguous across your integrations you’ll get 409; use the exact name from the list.

Next