conseel
Drop-in encrypted transport for AI SDKs. Wraps cohere-tng to route
requests through OHTTP encryption with TEE attestation verification. TNG
automatically promotes the model field from JSON request bodies into an
x-gateway-model-name header for backend routing (via body_field_headers
config).
Install
pip install conseel
Usage
Cohere
import cohere
import httpx
from conseel import Transport
co = cohere.ClientV2(
api_key="...",
httpx_client=httpx.Client(transport=Transport()),
)
co.chat(model="command-a-plus-05-2026", messages=[...])
OpenAI
from openai import OpenAI
import httpx
from conseel import Transport
client = OpenAI(
http_client=httpx.Client(transport=Transport()),
)
client.chat.completions.create(model="gpt-4", messages=[...])
Async
import httpx
from conseel import AsyncTransport
async with httpx.AsyncClient(transport=AsyncTransport()) as client:
resp = await client.post(url, json={"model": "command-a-plus-05-2026", ...})
What it does
- Encrypts all traffic via OHTTP so that even the network infrastructure cannot inspect request or response payloads.
- Verifies the remote TEE before sending any data, accepting either an
Intel Trust Authority passport or a background-check appraisal against the
latest signed integritee policy release (configurable via
verify). - Promotes the
modelfield from JSON request bodies to thex-gateway-model-nameHTTP header for gateway routing. This happens inside TNG viabody_field_headersconfig. Body parsing is skipped entirely for non-JSON requests (e.g. multipart audio uploads) and when the target headers are already present on the request. - Forwards
authorizationandx-gateway-model-nameheaders through the OHTTP layer to the backend.
Configuration
Transport and AsyncTransport accept the same verify and ohttp keyword
arguments as cohere_tng.Transport (see TNG configuration docs
for the full schema). The only difference is that conseel provides sensible
defaults:
verify— Defaults to Intel Trust Authority attestation. Accepts one config dict or a list of them. Defaults to a list of two verifiers: Intel Trust Authority passport, and the builtin attestation service in background-check mode fetchingtrustee_policyfrom the latest integritee release. Pass a single object to allow only one, orNoneto disable verification (not recommended for production).ohttp— Defaults include forwardingauthorizationheaders and promoting themodelJSON body field tox-gateway-model-nameviabody_field_headers.
Metadata
Release files for conseel 1.0.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 | |
|---|---|---|---|
| conseel-1.0.0.tar.gz | 3.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| conseel-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.6 kB
Release files / conseel-1.0.0.tar.gz
| Download URL | conseel-1.0.0.tar.gz |
|---|---|
| Size | 3.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
316e0e2f9ce84867e992882196045ee23ab66147685d1ee8a13d2d2e466dfadb
|
|
BLAKE2b-256 checksum How to use checksums |
897bb65738f50a88c71b6f05f0a380601451d75cf306f5454d3760a2573882a0
|
| 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 14, 2026.
Transparency logRelease files / conseel-1.0.0-py3-none-any.whl
| Download URL | conseel-1.0.0-py3-none-any.whl |
|---|---|
| Size | 3.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
242c90c59c2b14f09aa697757807d489d38194cea1d6f86566b064ed401f1a3b
|
|
BLAKE2b-256 checksum How to use checksums |
e41c3715d78db32de5e3dce898d1b9ba78b833d9a8255a3cb15d6026ff60ef7d
|
| 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 14, 2026.
Transparency log