Developer reference

This chapter documents the stable public contracts that integrations can rely on without depending on POM AI’s internal class or file layout.

POM AI service contracts

• Service architecture: where browser, WordPress, account service, and local writes meet.
• Credit estimates and credit consumption: separate quote and execution responses.
• License registry and multisite scope: the shared product-license source.
• Image replacement: attachment creation, reference replacement, metadata, and failure behavior.
• Privacy and security: task data, permissions, signing, and safe handling.

MCP protocol contracts

• Transport, tool schema, resource schema, and errors.
• Authentication, authorization, read versus write, and rate limiting.
• Audit and privacy.

Supported extension points

Public hooks lists current filters and their value shapes. Prompt-template extension covers the local reusable prompt-template UI. POM AI does not currently expose a public runtime registration API for arbitrary MCP tools, resources, or prompts; see tool-module extension.

These contracts are narrower than “all public PHP functions.” Treat documented hooks and helpers as supported. Do not instantiate internal MCP registry classes or depend on account-service implementation details.

For end-to-end examples, begin with MCP workflows and the prompt recipes.