Multisite POM AI license scope

POM AI service authorization is site-specific in multisite. Each subsite reads the license assigned to its own management scope, and that license’s account supplies the AI credits for the subsite’s domain.

This is separate from plugin updates. The common private updater uses the network or main-site product license so it can detect POM AI updates even when the plugin is inactive on a target site. Do not use the updater license as the subsite’s AI service credential.

Integration rules

• Resolve the POM AI license in the current blog context with pom_ai_get_license_key().
• Do not switch to the main site to “find” a missing service license.
• Do not copy a license into every subsite option.
• Authorize the exact domain served by the subsite.
• Treat a cloned or domain-changed site as a new authorization check.

The main site is still a site and needs its own POM AI service authorization when it uses AI features. A shared subscription can fund multiple authorized sites according to its plan, but each site remains explicitly connected.

When reporting a license problem, include the site URL and blog context but never the key. In a multi-network or mapped-domain environment, verify the public domain used by WordPress rather than assuming the network base domain.

Related guides: multisite license setup, network update license, and license registry contract.