Python SDK

Mesh Storage

Limits

Boundaries for SDK uploads, reads, hosted SQL, and processing status

The SDK keeps Mesh Storage operations explicit: upload files into SDK paths, read Mesh objects by prefix or key, and query ingested data through hosted SQL.

Upload limits

High-level upload helpers support .mcap, .json, .yml, and .yaml files under:

uploads/sdk-uploads/

The SDK does not expose delete, move, rename or overwrite, direct storage credentials, or direct mission creation.

Each object key can be at most 1024 bytes of UTF-8. The SDK checks every target key before upload and raises AlloyStorageTransferError if a key is too long.

If your organisation has reached its storage limit, upload helpers raise AlloyStorageHttpError with status_code 402 and the error storage_limit_reached. No files upload.

overwrite=True raises immediately. Delete or replace files through Mesh Storage workflows before uploading a replacement.

Read limits

Read helpers list and download objects under uploads/ by SDK path, raw prefix, or exact key. They do not provide file-id mapping or cross-org access.

SQL limits

Hosted SQL is read-only and is available through the SDK and SQL Workbench. The SDK does not expose write SQL or table creation.

Processing limits

Uploading a file is not the same as processing it. After upload:

  • Replay and Inspect work once the MCAP lands.
  • SQL requires the file to show Ingested.
  • Files that show Ingest failed need investigation from the Mesh Storage file row.

The SDK does not poll processing status. Use Mesh Storage, SQL Workbench, or MCP tools to inspect readiness.

Dependencies

The SDK needs Python 3.12 (>=3.12,<3.13). It does not install on Python 3.11 or 3.13.

The base SDK includes the transfer clients required by Mesh Storage. Optional extras are still used for some local result conversions:

FeatureDependency path
Mesh sync transfersincluded
Mesh async transfersincluded
pandas conversioninstall alloy-sdk[pandas]
Polars conversioninstall alloy-sdk[polars]
DuckDB conversioninstall alloy-sdk[duckdb]

If Polars or DuckDB is missing, the SDK raises AlloySqlDependencyError. If pandas is missing, the SDK raises a plain ImportError. Neither case falls back silently.

On this page