Create a memory rule
POST/v1/projects/:project_id/memory-rules
Creates an ingestion rule on a memory store. With neither agent_id nor tool_id the built-in extractor runs, configurable through prompt, ai_provider_id and model.
Request
Responses
- 201
- 400
- 401
- 403
- 404
- 413
- 429
- 500
- 502
- 4XX
Memory rule created
Validation failed (e.g. agent_id and tool_id both set, or an extractor override combined with a handler)
Unauthorized
Forbidden
Memory store not found
REQUEST_REJECTED — the request body is over the size the body parser accepts
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Internal server error
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there