PHI INPUTS: PROHIBITEDPHASE: 0 — NOT FOR PHIBAA TIER: IN BUILD
Docs

API: NOT YET AVAILABLE · PREVIEW ONLY · SUBJECT TO CHANGE

Integration preview.

There is no PHIGate API today. This page previews what integration is designed to look like so you can judge the shape of the work before the endpoint exists. Everything below can change before launch.

Shape

The intended integration.

The endpoint is being built OpenAI-compatible; none of it is live today. The intended integration is a base URL change and a PHIGate key. Your SDKs, frameworks, and agents are meant to keep working.

PreviewILLUSTRATIVE
# PREVIEW. The API is not yet available.
client = OpenAI(
    base_url="https://api.phigate.ai/v1",   # planned
    api_key=os.environ["PHIGATE_API_KEY"],  # keys do not exist yet
)
Keys

What the key will carry.

Keys are planned to carry a compliance profile: permitted deployment paths, acceptable retention terms, permitted regions. Requests may strengthen the profile per call; they will not be able to loosen it. Policy failures are planned to return fixed, documented error codes. Full explanation in How it works.

Logs

What will be logged.

The gateway's own logs are designed to record routing metadata: timestamps, key ID, model route, policy decision, token counts, error codes. Not prompt bodies. Not completions. The logging boundary is a design commitment we intend to pin with tests before the endpoint goes live. The exact log-line schema will be published on this page before the API opens.

Now

Until then.

The model directory is live now and carries the compliance metadata the endpoint will enforce. The evaluation protocol is published as a draft. If you want the endpoint when it opens, join the waitlist.

Join the waitlist