Platform
ScaiWave ScaiGrid ScaiCore ScaiBot ScaiDrive ScaiKey Models Tools & Services
Solutions
Organisations Developers Internet Service Providers Managed Service Providers AI-in-a-Box
Resources
Support Documentation Blog Downloads
Company
About Research Careers Investment Opportunities Contact
Log in

Changelog

User-visible changes to ScaiAtlas and the Python SDK.

Registry#

2026-10-18#

A security review of the public API. Several endpoints were authenticated but not authorized — a token was enough where a permission should have been required. If you hold a namespace-scoped or worker key, the changes marked ↯ may turn calls that used to work into 403.

Peers now have owners

  • ↯ A node_id belongs to whoever first announced it. Only that caller can change a peer's address, port or chunk list afterwards; anyone else gets 403. Previously any authenticated caller could announce someone else's node_id and move it, and since clients resolve peers through /p2p/peers/by-version, that redirected a swarm. Revoking the owning key releases its peers, so a rebuilt machine reclaims its node id on the next announce; an administrator can also take one over. Peers registered before this change are unowned and are claimed by their next announce.
  • DELETE /p2p/peers/{node_id} accepts the peer's owner as well as an administrator, so a node can retire itself. It previously accepted anyone.
  • ↯ GET /p2p/peers and GET /p2p/stats are administrator views. Together they list every node's address and port. GET /p2p/peers/by-version is unchanged and still open — that is the call a downloading peer makes.

Authorization

  • ↯ Reading the API key inventory needs admin. GET /admin/api-keys and GET /admin/api-keys/{id} were scoped to the caller's tenant but required no elevated permission, so any key could list every key in the tenant with its permissions, namespaces and linked user. Creating one already required admin.
  • ↯ POST …/manifest answers 501 Not Implemented and writes nothing. It used to answer 201 with a row whose checksum was the literal placeholder and whose file list was empty, and since a version holds at most one manifest that stub was permanent. It also checked no permission, so any caller could fix one onto any version in any namespace. Chunk manifest generation has not been built; the endpoint now says so.
  • ↯ GET …/manifest requires view on the namespace. It had no check, and a manifest describes the bytes of the version it belongs to.
  • ↯ GET …/versions/{version} requires view on the namespace. It had no check at all and returned the file list, sizes and checksums of any version in any namespace.
  • ↯ /search/models and /search/namespaces honour a key's namespace restrictions, as GET /namespaces already did. A key scoped to one namespace could previously enumerate every private namespace in the tenant by searching instead of listing.
  • GET /api/metrics/summary requires a caller.

Audit log

  • The recorded client address can no longer be chosen by the client. X-Forwarded-For is a request header anyone may send, and it was read first-entry-first. It is now believed only from a configured reverse proxy, and then the hop that proxy added is taken. Deployments behind a proxy should set SCAIATLAS_TRUSTED_PROXIES; with it unset the socket peer is recorded, which is the proxy's address rather than the caller's.

Credentials

  • Device-flow tokens are no longer kept. A CLI auth session stored the bearer token it handed over and nothing ever deleted it. Tokens are now cleared once collected, and finished or long-expired sessions are purged.
  • The verification link from POST /auth/cli/init only points at known hosts. It was built from a client-supplied base_url, and it carries a live user code.
  • Filesystem-storage downloads refuse unsigned requests. The HMAC used to fall back to a fixed built-in secret when none was configured. A path that escapes the storage root is now rejected rather than cleaned up with a string replace that could be stepped around.

Rate limiting

  • rate_limit_enabled now defaults to false and means what it says. The middleware was never mounted, so the setting described a control that did not run. It is mounted now; three faults were fixed before turning it on, the worst of which keyed every JWT caller into a single shared bucket. Limits are off until they are agreed with the clients that publish and pull.

2026-10-17 (later)#

  • The upload routes check permission, not just the upload id. upload_part, the part listing, complete and abort resolved a file by upload_id alone, with no permission check, and ignored the namespace, model and version in the path. They now require upload_version on the namespace named, and the upload must belong to the version named; a mismatch is a 404.

  • /admin/stats requires an administrator. It reports registry-wide counts and total bytes stored, and was readable by any authenticated caller.

  • Downloads are recorded. They were not logged at all. Each entry names the key that pulled the file (api_key_id, api_key_name) along with the model, version, file, address and user agent, and is readable at GET /api/v1/access-logs?action=download. A namespace-scoped key sees only its own namespaces' history, which it previously could not be given at all.

  • ?redirect=true on a file download answers 307 with a short-lived pre-signed storage URL, so the bytes do not pass through the API. Range works on it. Off by default, since it needs the client to reach storage directly. The download is logged at the redirect.

  • Namespace storage quotas. A namespace can carry a limit in bytes, visible as quota_bytes and used_bytes on the namespace. Uploads in flight count, charged at upload/init before any bytes are sent, so a file that will not fit is refused up front and the limit cannot be stepped past by opening several uploads at once. Over the limit returns 507 with a machine-readable body. Only a tenant administrator can set a quota.

  • Scoped worker keys. A key holding manage_worker_keys can mint download-only keys in its own namespaces, list them and revoke them, without going through the registry team. A minted key cannot exceed its minter, cannot reach further, and cannot mint in turn.

  • Range reads no longer start at byte 0. The API read every object from the beginning and discarded the bytes before the requested offset, so a read got slower the further into a file it started and, past about 1.5 GB, died before sending anything — resuming a large file near its end was impossible. The range is now passed to storage and the cost is flat.

  • Suffix ranges return the right bytes. bytes=-500 means the last 500 bytes; it was returning the first 501.

  • An end past the file is clamped, not refused (RFC 7233), and a syntactically invalid Range now returns 400 instead of being ignored and quietly sending the whole object.

  • POST /namespaces returns 403, not 500. It had no permission check at all; creating a namespace now requires a tenant administrator.

  • Namespace listings honour an API key's namespace scope. A key limited to some namespaces could list the names of others, which the detail route correctly refused.

  • Error messages name statuses the way responses do. They printed an internal enum, so a client was told VersionStatus.AVAILABLE where the API everywhere else says ready.

  • Deleting a version now deletes its files. Deletes removed only the database record and left the bytes in object storage, where nothing named them any more. Deleting a version, a variant or a whole model now removes the stored objects too, and abandons any multipart upload still in flight. Storage is emptied first: if it cannot be reached the delete returns 502 and nothing is removed, so retrying completes it.

  • Timestamps are UTC, with an explicit offset. They were served as the host's local time with no offset, so anything reading them as UTC was out by the host's offset — and ambiguous for one repeated hour when daylight saving ends. Worse, a single row could mix the two: fields written by the database used local time while fields written by the application used UTC. Everything is now stored and served as UTC, written …T23:37:07Z, and existing rows have been converted. Clients that parse the offset need no change.

  • Deprecated versions keep downloading. deprecated now means discouraged, not switched off: anything already pinned to that version keeps working, and latest stops offering it. Only deletion stops it serving. (Briefly earlier today the docs said the opposite; that was the behaviour at the time.)

  • The single-file download route now checks version status. It streamed bytes from versions the listing route refused, including versions still uploading.

  • latest no longer follows an unfinished upload. It resolved to the highest semver version whatever its status, so creating a new version pointed latest at it immediately and downloads returned 400 Version is not available (current: uploading) until the version was published. Publishing a release took your own latest down for the length of the upload. latest now means the highest published version, on both GET …/versions/{version} and the download routes, which previously disagreed. A model with no published version returns 404 with a message that says so.

2026-10-17#

Fixes to the model and version endpoints, and to the permission model.

  • Model detail, model update and version create no longer return 500. Building a full response read a lazily-loaded relationship, which fails under the async stack. GET …/models/{model}, PATCH …/models/{model}, POST …/models/{model}/versions, PATCH …/versions/{v} and GET …/versions/{v}/variants were all affected. List endpoints were not, which is why the problem looked narrower than it was.
  • PATCH a version with the status you just read. Responses rename the stored available to ready; writes now accept ready too, so the read-then-write loop works. failed is rejected with 422 instead of failing mid-write.
  • The variant endpoints enforce permissions. List, get, create and delete previously resolved a version by name across every namespace with no check, so any authenticated caller could read and delete variants in a private namespace. They now require view / upload_version / delete_any_model.
  • Namespace-scoped API keys grant from their own permission list. The namespace list used to be only a restriction, so a service key with no linked user was refused everything. See Authentication.
  • GET …/namespaces/{name}/my-permissions reports what is actually enforced. It previously reported nothing for a namespace-scoped key that worked, and would have reported read access on a public namespace the key was refused. Reporting and enforcement now share one resolver.
  • GET /api/v1/namespaces/{name} no longer returns 500 for every caller.
  • POST /api/v1/p2p/announce validates its payload instead of returning 500: unknown or malformed version_id values are refused by name, and a rejected announcement no longer wipes the peer's existing entries.
  • Concurrent requests on one API key no longer fail. Every authenticated request rewrote the key's last_used_at, so callers sharing a key — a client uploading parts in parallel, say — collided on that row and the loser's request returned 500. The stamp is now written at most once every five minutes, on its own connection, and a failure to write it can no longer affect the request.
  • Added the vm_image model type and the ext4 and oci_archive formats.

Python SDK#

0.1.3#

Upload and download now work against the registry. Before this release neither did, and no call authenticated.

  • Authentication fixed. The client sent X-API-Key; the API only reads Authorization: Bearer. Every request was unauthenticated.
  • Upload rewritten against the real API. It targeted /api/v1/uploads/…, which does not exist. It now uses the versioned upload routes, sends parts as raw bodies at the server's part_size, and marks the version ready on complete() — without that last step a version stays uploading and cannot be downloaded.
  • add_file now stages and hashes; the transfer happens in complete(), because the registry needs the full file list when the version is created. Added staged_files to inspect what is queued. A session that raises before complete() aborts in-flight uploads and removes the version it created.
  • Download fixed. It requested …/versions/{v}/files/{path}; the route is …/versions/{v}/download/files/{path}.
  • Added vm_image to ModelType.
  • User-Agent now reports the real package version instead of 0.1.0.

0.1.2#

Pagination & filter alignment with the registry API.

  • Pagination now works. List and search calls send page_size (the server's parameter) and parse the server's {data, page, page_size, total, total_pages} envelope. Previously the client sent per_page and looked for items/pagination, so paginated calls silently returned empty pages against the real API.
  • search.models(...) takes a single tag filter plus sort (updated|created|name|downloads, default updated) and order (asc|desc, default desc).
  • Removed the unused status filter from versions.list(...) (the API doesn't support it).
  • The Python surface is unchanged — per_page kwargs, PaginatedResponse.items, and .pagination (has_next/has_prev) all behave as before; only the wire protocol and response parsing were corrected.

0.1.1#

Schema-alignment release — brings the SDK in line with the live registry API. This is a breaking change relative to 0.1.0 for the affected calls.

Namespaces

  • Namespace now exposes visibility (public|tenant|private) and owner_tenant_id; the old type and owner_id fields are gone.
  • namespaces.create(...) takes visibility= instead of type=.
  • NamespaceMember restructured to {id, user, group, role, granted_by, granted_at} with UserSummary/GroupSummary.
  • search.namespaces(...) no longer takes a type filter.

Models

  • type is now a required keyword on models.create(...) and spans the full 11-value model-type vocabulary (llm, embedding, image_generation, stt, tts, multimodal, vision_language, audio_language, video_language, image_to_image, audio_to_audio).
  • Added license, capabilities, modalities, and metadata; download counter is now download_count.
  • Models no longer carry a visibility field (visibility lives on the namespace); models.list/search.models dropped the visibility filter.

Versions

  • versions.create(...) / versions.update(...) now use release_notes and requirements (plus quantization, files) instead of description/metadata.
  • Version exposes model_id, semver parts, checksum_sha256, and published_at; VersionFile gained name/sha256 aliases.

Variants

  • variants.create(...) now takes variant_name= and a constrained format (safetensors|pytorch|gguf|onnx|other); description/metadata removed.
  • Variant exposes version_id, is_primary, and status.

Uploads

  • upload.version(...) accepts release_notes / requirements in place of description / metadata.

Download the artifacts from the ScaiLabs downloads page.

0.1.0#

Initial release: sync + async clients, namespace/model/version/variant resources, resumable upload/download, search, and admin operations.

Updated 2026-10-18 01:55:51 View source (.md) rev 13