Altss Python public client
Python 3.11+ readers for named anonymous resources on https://altss.com: published profile summaries, catalogs, JSON Schemas and Markdown documents. The runtime uses only the Python standard library. It has no account tokens, cookies, telemetry, automatic retries or authenticated Product access.
Install from GitHub source
python -m pip install 'git+https://github.com/Altssdata/public-client.git@python/v0.1.0#subdirectory=python'
This is a versioned GitHub source installation, distinct from a PyPI registry release. The Python package version is 0.1.0; the JavaScript package version is independent. A prepared wheel does not establish PyPI publication.
Use
from altss_public import AltssPublicClient, AltssHttpError
client = AltssPublicClient(timeout=10)
catalog = client.get_catalog("data")
profile = client.get_profile("daimler-truck-ag")
page = client.search_profiles("Daimler Truck", limit=2)
print(profile.data)
sandbox = AltssPublicClient(sandbox=True)
fixture = sandbox.get_profile("example-capital-01")
get_catalog(name), get_schema(name), get_document(name) and read(resource)
accept the exact names in the exported, immutable resources mapping.
Their optional etag argument performs a conditional GET. A 304 returns
data=None; reuse the representation belonging to that ETag. There is no hidden cache.
search_profiles(query, limit=1..5, cursor=None) follows the public pagination
contract. get_profile(slug) reads one existing published profile. Sandbox mode
changes only profile methods and reads clearly labeled fictional fixtures.
Responses provide status, data, url, etag, last_modified, cache_control,
and optional environment and rate_limit metadata. JSON is a dictionary of
unknown fields: use the current OpenAPI reference.
Canonical profile citations come from the service response, not from guessed slugs.
Profile responses remain private/no-store. Rate-limit headers describe the serving
instance; they are not a global or per-user allowance.
The transport sends one HTTPS GET to the fixed Altss origin, rejects redirects and limits response bodies to 4 MiB. TLS verification stays enabled. Environment proxy credentials, netrc files and global cookie stores are not loaded. Timeout is 10 seconds by default, configurable above zero through 60 seconds. The same remaining time budget is applied before each socket operation and body chunk. These are socket timeouts, not a hard process deadline: operating-system DNS resolution and a slow header stream may outlast that budget. The synchronous client does not provide asynchronous task execution or cancellation.
HTTP failures raise AltssHttpError with status and retry_after; response bodies
are not retained in the exception. Missing profiles are errors, never fabricated
records. Other transport, TLS, timeout, decoding and validation failures propagate.
There are no writes, account access, contact exports, bulk exports, payments or
subscription records. Documentation MCP is a separate service at docs.altss.com/mcp.
Run python -m unittest discover -s tests -v from this directory. Build artifacts
with python -m build, then validate with python -m twine check dist/* in an
isolated development environment. Tests use deterministic transports; live reads
and registry installation are separate release checks.
Support: contact@altss.com. Source and issues. Field definitions and access terms: Altss developer reference. The proprietary license and public-data boundaries match the existing clients.
Metadata
Release files for altss-public-client 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| altss_public_client-0.1.0.tar.gz | 8.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| altss_public_client-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.1 kB
Release files / altss_public_client-0.1.0.tar.gz
| Download URL | altss_public_client-0.1.0.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
50f6da6abc19161bb7698542290e4924f51bfd4176705b327ec4fc0e9431a191
|
|
BLAKE2b-256 checksum How to use checksums |
6f5a3733f7c35480bfe72dbbf5440095232764abfd24f0330d7b3efdd850e7c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Release files / altss_public_client-0.1.0-py3-none-any.whl
| Download URL | altss_public_client-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7b849c3e0892963522b03d2a05820a741da6c2e5b7076af82271a2724f292caf
|
|
BLAKE2b-256 checksum How to use checksums |
d3a48ae8974ecfd38dead5b6c814d9e7409e3b5fc19f44b8f81c853bc167e32a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Security for altss-public-client 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.