poixe-encrypt
Python SDK for encrypting vendor API keys for the Poixe platform.
Encrypt upstream model provider API keys (OpenAI, Anthropic, AWS Bedrock, etc.) locally in your process before submitting them to Poixe. The plaintext key never leaves your machine — only the enc:v2:... ciphertext is transmitted or stored.
Installation
pip install poixe-encrypt
Requires Python 3.8+ and the cryptography package (installed automatically).
Usage
from poixe_encrypt import ChannelType, encrypt
# OpenAI
cipher = encrypt(ChannelType.OPENAI_CHATGPT, "sk-proj-...")
# Anthropic
cipher = encrypt(ChannelType.ANTHROPIC_CLAUDE, "sk-ant-...")
# Azure (requires endpoint)
cipher = encrypt(ChannelType.AZURE_CHATGPT, "my-key",
endpoint="https://my-resource.openai.azure.com")
# AWS Bedrock (requires region)
cipher = encrypt(ChannelType.AWS_BEDROCK_CLAUDE, "AKID...",
region="us-east-1")
# Google Vertex Gemini (Service Account JSON)
import json
cipher = encrypt(ChannelType.GOOGLE_VERTEX_GEMINI, json.dumps(sa_dict))
# Pin the public key fingerprint (recommended for production / CI)
cipher = encrypt(ChannelType.OPENAI_CHATGPT, "sk-proj-...",
fingerprint="19bb2f0101de7bb3e1ca6fea27fa06474b37de654b0191e3430b4e30f5c6e761")
Output is a single enc:v2:... string ready to submit to the Poixe System API or dashboard.
Updating
pip install -U poixe-encrypt
Update when Poixe adds new channel types — older versions will not have the new type constants.
Public key
The SDK fetches https://poixe.com/security.json once per process and caches the result. The key's SHA-256 fingerprint can be verified independently:
dig TXT _encryption.poixe.com +short
# "v=v2; kid=k1; fp=19bb2f0101de7bb3e1ca6fea27fa06474b37de654b0191e3430b4e30f5c6e761"
See the verification guide for details.
Supported channel types
All 32+ types are available as constants on ChannelType. See the full list.
License
MIT
Metadata
Release files for poixe-encrypt 0.1.1
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 | Actions |
|---|---|---|---|---|
| poixe_encrypt-0.1.1.tar.gz | 5.6 kB | With provenance | Details for poixe_encrypt-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| poixe_encrypt-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for poixe_encrypt-0.1.1-py3-none-any.whl |
Total release size: 11.8 kB
Release files / poixe_encrypt-0.1.1.tar.gz
| Download URL | poixe_encrypt-0.1.1.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fe8cc479bb79d40e1b0e129cc4101ecfe621b2831608f4256d04ad420a86a50d
|
|
BLAKE2b-256 checksum How to use checksums |
894e30ed838b058ef49abe72cad923ded9d2bb0c70f5d807d7158cda05eef1a9
|
| 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 Nov 13, 2026.
Transparency logRelease files / poixe_encrypt-0.1.1-py3-none-any.whl
| Download URL | poixe_encrypt-0.1.1-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
91faa3b007bf94e2579af31de24454785371295f599213c09182b548ea2440e2
|
|
BLAKE2b-256 checksum How to use checksums |
66374b2b2a17825ecea4efea68e82e1d8348868eeaf60f810033d35a13d3c6dd
|
| 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 Nov 13, 2026.
Transparency logSecurity for poixe-encrypt 0.1.1
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
Both files in this release have been uploaded with provenance metadata.
Attestation for poixe_encrypt-0.1.1.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 Nov 13, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.