sentinos-sdk-core (Python)
Low-level generated Python client for the Sentinos API. Choose sentinos-sdk-core when you want direct OpenAPI coverage, typed models, and full control over HTTP behavior.
Most teams should install sentinos instead. The higher-level wrapper adds curated helpers, runtime integrations, and a simpler onboarding path on top of this generated client.
Choose this package if...
- You want the raw generated client for custom automation or framework integration
- You need access to the full typed API surface without higher-level abstractions
- You care about sync and async entry points for every endpoint
- You want to build your own retry, logging, or instrumentation layer around the HTTP client
Install
pip install sentinos-sdk-core
Configure
export SENTINOS_API_URL="https://api.sentinos.ai"
export SENTINOS_ACCESS_TOKEN="<access-token>"
Then create an authenticated client:
import os
from sentinos_core import AuthenticatedClient
client = AuthenticatedClient(
base_url=os.environ.get("SENTINOS_API_URL", "https://api.sentinos.ai"),
token=os.environ["SENTINOS_ACCESS_TOKEN"],
)
Example: inspect and replay a decision trace
from uuid import UUID
from sentinos_core.api.default import trace_get, trace_replay
from sentinos_core.models.trace_replay_body import TraceReplayBody
trace_id = UUID("11111111-1111-1111-1111-111111111111")
trace = trace_get.sync(client=client, trace_id=trace_id)
print(trace.trace_id, trace.policy_evaluation.decision.value)
replay = trace_replay.sync(
client=client,
trace_id=trace_id,
body=TraceReplayBody(include_explain=True),
)
print(replay.drift_detected, replay.replayed_at.isoformat())
Async uses the matching asyncio(...) entry points:
import asyncio
async def main() -> None:
trace = await trace_get.asyncio(client=client, trace_id=trace_id)
print(trace.trace_id)
asyncio.run(main())
Generated client ergonomics
Every endpoint module exposes four call styles:
sync(...)for the parsed modelsync_detailed(...)for parsed data plus HTTP metadataasyncio(...)for async codebasesasyncio_detailed(...)for async metadata access
Models live under sentinos_core.models.*, and the underlying AuthenticatedClient exposes its shared httpx clients so you can attach hooks, logging, or custom transport settings.
Resources
Release files for sentinos-sdk-core 0.1.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| sentinos_sdk_core-0.1.8.tar.gz | 1.1 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sentinos_sdk_core-0.1.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.8 MB
Release files / sentinos_sdk_core-0.1.8.tar.gz
| Download URL | sentinos_sdk_core-0.1.8.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b64e15453efb188fd2ee59942b637e0dac0f292f11019e2a74b46bf9b758e061
|
|
BLAKE2b-256 checksum How to use checksums |
5f014bb460f67b15c3a591eeee09ea709129dee8c71647e935e698a63e0e028f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 30, 2026.
Transparency logRelease files / sentinos_sdk_core-0.1.8-py3-none-any.whl
| Download URL | sentinos_sdk_core-0.1.8-py3-none-any.whl |
|---|---|
| Size | 627.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
676d1b38f398b4094196ad6417ebe5159babf717cd95e918c6a59291cad9ff15
|
|
BLAKE2b-256 checksum How to use checksums |
41902f128a976f3e32156deec6cc8f6a47dc3f9ea3a375d8985c3ae0ffdd32c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 30, 2026.
Transparency log