Skip to main content
Phala Confidential AI is OpenAI-compatible. Most integrations require changing only the base URL and API key:
After migration, responses can be verified with x-receipt-id, Attestation Report, and Get Receipt.

Migrate from OpenAI

Everything else stays familiar: chat completions, streaming, tool calling, vision, structured output, and embeddings use OpenAI-compatible request shapes.

Migrate from OpenRouter

Model ids use the provider/model format returned by /v1/models. Use is_tee: true to find models that can be served confidentially, then verify the actual response receipt.

OpenAI SDK

LangChain

Vercel AI SDK

Langfuse

Observability tools may store prompts, responses, metadata, or traces. For sensitive data, configure redaction or self-hosting before sending production traffic.

Coding Assistants and Desktop Clients

For tools that support an OpenAI-compatible provider, use: This works for tools such as Continue, Cline-compatible assistants, Cherry Studio, and other clients that let you set an OpenAI-compatible base URL.

Migration Checklist

  • Create a Phala API key.
  • Change the base URL to https://inference.phala.com/v1.
  • List models with GET /v1/models.
  • Use is_tee: true for confidential-capable models.
  • Capture x-receipt-id in raw HTTP responses when you need verification.
  • Verify one representative response before production rollout.

On-demand API

Error Handling