v1

Create Batch

Import up to 500 memories in one call.

Every row is checked as a single write is (its content, metadata, timestamp, user_id, agent_id and run_id) before anything is queued: a bad row is refused with its index in the message, and nothing is imported. Then the job is queued and the call answers 202 with its job_ id. The worker writes the rows, which get their facts as any write does; GET /v1/batch/{job_id} says how far it is. If the key is revoked, expires or is moved to another project before the worker is done, the rows not yet imported are not: each is a failed row with its reason in errors, and the job completes.

post/v1/batch

Request

  • Base URL: https://api.korely.ai
  • URL: https://api.korely.ai/v1/batch
  • Auth: HTTP bearer

Headers

X-Korely-Clientstring nullable

The tool importing: kept on every imported memory as client.

Request body

Response

Successful Response

idstring required
status'pending' | 'processing' | 'completed' | 'failed' required

pending (queued, no worker on it yet), processing (being imported now), completed (every item tried: imported and failed are final) or failed (stopped on an error of the worker, tried again from where it stopped until its attempts are used, so it may still become completed). The POST answers the stored value, as the GET does.

receivedinteger required

Changes

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