Privacy & security

We can't leak what we never store.

Apex Ant is a Venice-only inference router on the AntSeed P2P network. Prompts and responses are never logged or persisted, only token counts and costs. The buyer stack (gateway + mux, the part that holds user keys) already runs inside an attested hardware TEE, verified live below. The seller stack (inference routing) is policy-enforced today; moving it into a TEE as well is on the roadmap.

buyer stack: TEE enclave (attested live below)

Live TEE attestation

The hosted buyer stack (mux + gateway) runs inside a Phala Cloud Intel TDX enclave. This block compares the live hardware quote of the running VM against image digests published in the public repo, refreshed every minute. Green: the code holding your keys is exactly the code you can read.

Enclave status
MRTD (launch measurement)
RTMR3 (app measurement)
Runner / KMS
Release commit
Released at
Checked at
Live enclave reportdstack worker info ↗

Container images

Verify independently on Phala Trust Center →

SCOPE
Covers the hosted buyer stack (gateway + mux): your keys, your sessions. Secrets are KMS-gated to the attested measurement. Not covered: prompts then leave for Venice ZDR inference (their guarantee); the native AntSeed path (VPR client / CLI) is trustless by design.
⌥ apex-buyer-gateway ↗
gateway + mux: the exact code the enclave runs (digests above)
⌥ openvenice ↗
chat frontend, baked into the attested image, pinned by commit
Honest framing: this hosted gateway is the easier way in, with keys sealed in the attested enclave above. The native AntSeed client is the more robust one: if your threat model excludes hardware attestation altogether, pin our peer from your own node: same seller, same prices, trustless end to end.

How it works

YOUR REQUESTS

Prompts arrive over AntSeed's end-to-end encrypted transport (X25519 + AES-256-GCM) and are proxied in memory. Never written to disk, logs, or databases. We persist only token counts, model name, latency, and a pseudonymous peer id.

UPSTREAM KEYS

Inference runs exclusively on Venice AI private-tier capacity, a provider contractually committed to not logging prompts. Upstream credentials live in memory-only pools, never on disk.

RESPONSES

Responses stream straight back through the encrypted channel. Nothing is cached or stored: no response bodies, no embeddings of them, no "abuse-prevention" retention.

Data flow

your tool / wallet ── E2E encrypted (AntSeed transport) ──▶ ▲ apex node ── HTTPS ──▶ venice ai · private tier
seller side: no-log pipeline, isolated process, no content persistence billing: USDC channels on Base · no account · no email

Guarantees

NO PROMPT LOGGING

Content is never persisted. Operational metadata only: token counts, latency, error codes.

RESTRICTED ADMIN ACCESS

Seller-side access is single-operator, key-only, and audited. The buyer stack has no interactive access at all; it runs inside the attested TEE above.

YOUR MONEY, YOUR EXIT

API users fund their own buyer address in the AntSeed escrow contract on Base. We never custody deposits. Your buyer key backup lets you withdraw without our involvement, even if we vanish.

OPEN BUYER STACK

The buyer gateway and mux are fully open source: read exactly what is kept and what is discarded, line by line, and match it against the live attestation above.

Don't trust, verify

Our pricing promise is verifiable today: the live board is regenerated from public Venice list prices. The live attestation block for the buyer stack is at the top of this page:

TEE platformPhala Cloud CVM · Intel TDX live
CVM app id29f044f3d4231dd09dd4aa8c6a643a45fd99c654
Verify via CLInpx phala cvms attestation 29f044f3d4231dd09dd4aa8c6a643a45fd99c654
Operator imagedigest pinned · distroless · reproducible
Trust centertrust.phala.com/app/29f044f3…

our seller, on-chain: 0x73b4c9335fa239f9c6df3d28d5bf5d3cdf4de736 · settlement: AntSeed deposits & channels contracts, Base mainnet · antseedstats

questions → @apex_ant. we answer.