This release is a pre-release and may not be stable for production use.
Synth SDK 0.23 development branch
Local SDK-first Index implementation. Package version 0.23.0.dev2026101501 is a development candidate; release qualification and publication remain pending.
The new client targets the closed index.v1 contract on /api/v1; it refuses
legacy responses and does not fall back. Backend adoption and native/cached/live
acceptance are pending. This worktree also implements the first Swarms core,
output/file delivery and unified MCP adapter. The initial caller model override
accepts only gpt-5.6-luna, with openai as the supported provider override.
Omitted overrides preserve backend project defaults; resolved metadata is not
an override allowlist. Hosted MCP requires the backend authorization/service
adapter; its native OAuth/API-key journeys remain unqualified.
from synth_ai import SynthClient
from synth_ai.sdk.index import PublicSearchOptions
with SynthClient.anonymous() as client:
result = client.index.search("reproducible retrieval evidence", options=PublicSearchOptions())
print(result.response)
This requires an index.v1 backend. Keyed calls require KeyedSearchOptions with an exact Money charge ceiling. Durable search and mutation recovery are keyed. Use typed content refs for current-rights retrieval; citations grant no access. Synchronous clients own a cancellable HTTP pool; synchronous client injection is not supported. Async clients use native async HTTP and may borrow an AsyncClient. Local observer timeouts and close never cancel durable remote work.
The retired source remains on legacy/sdk-pre-0230-20261013; no broad compatibility
aliases, old CLI or split MCP are shipped.
- Implementation and contract choices
- Backend delta map
- Testing expectations
- Unified MCP implementation and auth integration
Tests live in the dedicated testing repository and install the selected wheel in an owned isolated environment. SDK unit/contract passes are not backend or end-to-end qualification. No backend services/data/deployment are changed here.
Metadata
Release files for synth-ai 0.23.0.dev2026101501
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| synth_ai-0.23.0.dev2026101501.tar.gz | 119.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| synth_ai-0.23.0.dev2026101501-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 279.2 kB
Release files / synth_ai-0.23.0.dev2026101501.tar.gz
| Download URL | synth_ai-0.23.0.dev2026101501.tar.gz |
|---|---|
| Size | 119.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d1facd7aa71e0efcc012ddaf062a120dc3e77729ef17cf513d5edb15d0a9b4b8
|
|
BLAKE2b-256 checksum How to use checksums |
51f5cdd4703dcee35050ea754d92d5cce1dbafb6f186ed8c9466d1c77aaa1b59
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency logRelease files / synth_ai-0.23.0.dev2026101501-py3-none-any.whl
| Download URL | synth_ai-0.23.0.dev2026101501-py3-none-any.whl |
|---|---|
| Size | 159.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2897d744994c50c1275ea188fc0fdb34800531514fd17d5ccd6b730ec41b3af6
|
|
BLAKE2b-256 checksum How to use checksums |
035d3fb012440fd045170c2ad81e97aa4a6eb5b8844adb1fafd0ee5f8bba4907
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency log