PressAI AI Connections interface
Interface illustration with sample data.
Bring Your Own Key

Use the AI provider account you already control.

PressAI Pro connects to supported AI providers through your own account. You choose the provider, model and operating order; provider usage is billed by that provider to your account.

Supported connections

Choose the provider that fits your workflow.

Model availability, quotas and billing are controlled by your provider account. PressAI gives your editorial team one place to configure and use those connections.

OpenAI

Connect an OpenAI API account and select the model available to your account for supported editorial AI tasks.

Google Gemini

Connect a Gemini API key and use the models available under your Google AI account.

OpenRouter

Use OpenRouter as a provider gateway when you want access to models offered through your OpenRouter account.

Anthropic

Connect Anthropic directly for supported Claude models available to your account.

DeepSeek

Connect DeepSeek directly and use the models enabled for your provider account.

Provider order & controls

Configure provider order, model selection, timeouts and usage controls from PressAI settings.

Credential handling

Your API keys stay under your WordPress administration.

Saved provider credentials are encrypted locally and are not re-displayed after saving. PressAI uses them only when a configured workflow needs the corresponding provider.

  • No bundled AI usage fee from PressAI.
  • No requirement to share one vendor-owned AI key across customers.
  • External requests occur only for providers and integrations you configure.
  • Provider errors, quotas and rate limits remain visible as operational conditions.

What BYOK means in practice

You choose: provider, account, model and budget.

Your provider bills: API usage under your provider account.

PressAI coordinates: the editorial workflow around those calls.

Operational resilience

AI should be a controlled dependency, not a hidden single point of failure.

Visible failures

Provider errors and failed jobs remain inspectable so an editor can decide what to retry or change.

Human workflow remains

Source monitoring, evidence review and editorial decisions do not disappear simply because an AI request cannot run.

Change providers deliberately

Administrators can adjust provider order and models without rebuilding the editorial workflow around a different tool.

Connect AI after the editorial workflow is clear.

Start with sources and operating settings, then add the provider connections your team actually needs.