Skip to main content

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

  1. Encrypts all traffic via OHTTP so that even the network infrastructure cannot inspect request or response payloads.
  2. 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).
  3. Promotes the model field from JSON request bodies to the x-gateway-model-name HTTP header for gateway routing. This happens inside TNG via body_field_headers config. Multipart uploads (e.g. audio) are supported when model precedes the file. Body parsing is skipped when the target headers are already present on the request.
  4. Forwards authorization and x-gateway-model-name headers 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 fetching trustee_policy from the latest integritee release. Pass a single object to allow only one, or None to disable verification (not recommended for production).
  • ohttp — Defaults include forwarding authorization headers and promoting the model JSON body field to x-gateway-model-name via body_field_headers.

Metadata

Release files for conseel 1.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for conseel 1.1.2
File Size Uploaded Provenance
conseel-1.1.2.tar.gz 3.7 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for conseel 1.1.2
File Interpreter ABI Platform
conseel-1.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 7.5 kB

Release files / conseel-1.1.2.tar.gz

Download URL conseel-1.1.2.tar.gz
Size 3.7 kB
Tags Source
SHA-256 checksum
How to use checksums
ef3706003cfe8c39cedca22a637e6129416728a6ab075e1f0079a24c5bf0d732
BLAKE2b-256 checksum
How to use checksums
77b73f13874a872cfb63a8068e5793321e342dfec4e40e20488c1d180b6f751a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 21, 2026.

Transparency log

Release files / conseel-1.1.2-py3-none-any.whl

Download URL conseel-1.1.2-py3-none-any.whl
Size 3.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
89fa18bf03cf46ae46a0ef09bfa3379f7674ee030dad204f812787f5f6b89f20
BLAKE2b-256 checksum
How to use checksums
957e9d45fb114032b3f53ce36e67cbfccf6b1b50091eb0984adaf811c904dc25
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 21, 2026.

Transparency log

Security for conseel 1.1.2

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for conseel-1.1.2.tar.gz

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 21, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page