[api-sync 2026-07-22] gradientlabs-python: sync to OpenAPI spec#135
Open
jafrog wants to merge 2 commits into
Open
[api-sync 2026-07-22] gradientlabs-python: sync to OpenAPI spec#135jafrog wants to merge 2 commits into
jafrog wants to merge 2 commits into
Conversation
Adds POST /conversations/{id}/memories to upload a batch of memories
scoped to a conversation for the agent to search over on demand.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Syncs the Python client to the current public OpenAPI spec. The only drift was a single new endpoint:
POST /conversations/{id}/memories(bulk_upload_conversation_memories) — bulk-upload a batch of memories scoped to a conversation for the AI agent to search over on demand._conversation_memories_upload.pywithBulkUploadMemoriesParams(idempotency_key: str,memories: List[Dict[str, Any]], optionalcreated_at_keys: List[str]) andBulkUploadMemoriesResponse(upload_id: str,memories_inserted: int).Clientnext to the other conversation methods; params/response re-exported via the existingfrom .client import *.tests/test_conversation_memories_upload.py) and a runnable example (examples/memories/run.py), both mirroring existing style.Version bumped
0.12.1→0.13.0(MINOR — additive new endpoint) in a separate commit.How verified
uv run --frozen pytest tests→ the 2 new memories tests pass; overall17 passed, 4 failed. The 4 failures are pre-existing, time-based webhook signature-expiry tests (hardcoded fixture timestamps now past the leeway window) that fail identically on the untouched base branch — unrelated to this change.uv run --frozen ruff check→All checks passed!ruff formatapplied to all changed files.No internal names leaked; no new dependencies;
GET /specnot exposed.