tibet-gateway
Alpha -- API may change between versions.
Sovereign external API proxy with TIBET provenance. Routes all AI agent egress traffic through a single gateway with host allowlist, intent verification (SNAFT), and provenance sealing.
Install
pip install tibet-gateway
Quick start
1. Configure allowed hosts (safe default: block all)
export TIBET_GATEWAY_ALLOWED_HOSTS=api.openai.com,api.anthropic.com
export TIBET_GATEWAY_EVENT_LOG=/var/log/tibet/gateway.jsonl
2. Start the gateway
tibet-gateway serve --port 8080
3. Proxy a call
curl -X POST http://localhost:8080/proxy \
-H "Content-Type: application/json" \
-d '{
"agent_id": "my-bot.aint",
"intent": "summarize_text",
"target_url": "https://api.openai.com/v1/chat/completions",
"method": "POST",
"payload": {"model": "gpt-4", "messages": [{"role": "user", "content": "Hello"}]}
}'
The response includes the original API response plus a TIBET seal with full provenance.
4. Check stats
tibet-gateway stats
tibet-gateway events --limit 10
What happens on each call
- Host check -- target domain must be in
TIBET_GATEWAY_ALLOWED_HOSTS - TIBET envelope -- mint provenance token (actor, intent, timestamp)
- SNAFT check -- verify payload matches declared intent
- Identity headers -- attach AINS identity and TBZ signature
- Proxy -- forward to external API
- Seal -- wrap response with TIBET seal and log stats
Configuration
| Environment variable | Description | Default |
|---|---|---|
TIBET_GATEWAY_ALLOWED_HOSTS |
Comma-separated list of allowed domains | empty (block all) |
TIBET_GATEWAY_EVENT_LOG |
JSONL event log path for live gateway telemetry | /var/log/tibet/gateway.jsonl |
Structured Event Log
Besides TIBET token chains, tibet-gateway can emit a JSONL event lane for
operational governance and AI-SBOM ingestion.
Each event records:
- actor / agent identity
- provider
- model
- target URL
- route class
- TIBET envelope / seal references
- status and latency
This is the live Tier B source that tibet-ai-sbom can ingest as
observation_layer = tibet-gateway.
Part of the TIBET ecosystem
- tibet -- core provenance tokens
- tibet-airlock -- sandbox execution
- tibet-mux -- channel multiplexing
Authors: Jasper van de Meent, Gemini & Root AI (Humotica AI fAmIly) License: MIT
Enterprise
For private hub hosting, SLA support, custom integrations, or compliance guidance:
| Enterprise | enterprise@humotica.com |
| Support | support@humotica.com |
| Security | security@humotica.com |
See ENTERPRISE.md for details.
Metadata
Release files for tibet-gateway 0.4.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 | Actions |
|---|---|---|---|---|
| tibet_gateway-0.4.0.tar.gz | 18.7 kB | Without provenance | Details for tibet_gateway-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tibet_gateway-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for tibet_gateway-0.4.0-py3-none-any.whl |
Total release size: 30.6 kB
Release files / tibet_gateway-0.4.0.tar.gz
| Download URL | tibet_gateway-0.4.0.tar.gz |
|---|---|
| Size | 18.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1c320af24435a5f80f9dfea12ff2c3893d0e66029284691bc63b1c4cd77d11f7
|
|
BLAKE2b-256 checksum How to use checksums |
fb919856f7827e9b8bfa396b1284e2a4e4a695733ab4079874f6f9f6e584c50b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / tibet_gateway-0.4.0-py3-none-any.whl
| Download URL | tibet_gateway-0.4.0-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b7604e2a39c4a4dd44829a8b7e271dc8eeb283a211fc393b7df3b1ba50bc5b9c
|
|
BLAKE2b-256 checksum How to use checksums |
5b221b5de6331e492ce5c99f0858bcbd451623e93f6528a5b91e516a517594c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for tibet-gateway 0.4.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.