Public service architecture

POM AI separates the WordPress user interface from account-side AI processing while keeping WordPress content changes local to the connected site.

Editor or feature UI
        |
        v
WordPress POM AI plugin
  - nonce and capability checks
  - input and file validation
  - signed service request
        |
        v
POM AI account service
  - license and domain authorization
  - credit estimate or consumption
  - task processing
        |
        v
WordPress POM AI plugin
  - validate response
  - store latest balance for display
  - create or update local content/media

Writing, translation, image, and transcription features follow this broad pattern, with feature-specific inputs and outputs. Estimation and execution are separate requests. A remote success does not automatically mean a local WordPress write succeeded, so each feature must validate both stages.

The MCP server is a separate site-local administration surface. MCP tools do not call the credit ledger and consume no POM AI credits. They authenticate the client, enforce WordPress capabilities and gates, then operate through WordPress, POM Theme, WooCommerce, or POM Cache APIs.

Developers should extend supported hooks and helpers rather than depend on private account routes, provider credentials, internal storage, or registry classes.

Related guides: security, privacy, and MCP transport.