List agent knowledge sources
What the merchant has taught the assistant: FAQ dumps and policy documents, newest first. THE SOURCE TEXT IS NOT PUBLISHED, here or anywhere. The stored row keeps a title and a chunk count; what the assistant answers from is the embedded chunks, and no copy of the original is kept to serve. Keep your own copy of anything you send. chunk_count is how many embedded pieces a source produced, which is the honest measure of how much the assistant learned from it. Zero means the ingest found nothing usable. This list covers only what the MERCHANT added. The store’s own catalogue, pages and blog posts are indexed by a separate sweep and are not resources here.
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Query Parameters
faq is chunked as question and answer pairs, doc as prose under its title. Omit it for both. A value outside this set is a 400 rather than an ignored filter.
faq, doc Rows per page. Out of range is a 400 rather than a silent clamp, so a client asking for more than 100 learns it did not get it.
1 <= x <= 100The next_cursor from the previous page. Opaque: decode nothing from it and construct nothing by hand, since its encoding is not part of this contract. Omit it to read the first page.
