Creating content via the Aimogen REST API allows you to generate AI-powered content programmatically, without using the WordPress admin UI. This is intended for integrations, headless setups, automation systems, MCP clients, and external services that need to trigger content generation in a controlled, authenticated way.
The REST API does not bypass Aimogen. It invokes the same execution engine used by the UI, with the same permissions, limits, provider logic, and logging.
When content is created via REST, Aimogen behaves exactly as if a trusted user triggered content generation manually. The difference is only the entry point. Instead of clicking a button in WordPress, an authenticated HTTP request triggers the execution.
Content creation via REST always runs inside a defined execution context. That context determines which generators are used, which providers and models are allowed, which limits apply, and how the result is handled. There is no “raw AI” endpoint that simply returns text. Everything is routed through Aimogen’s content generation system.
The typical REST-based content creation flow starts with authentication. The API request must be authenticated and associated with a valid identity. That identity maps to a WordPress user or execution role, and all permission checks happen before anything else. If the caller does not have permission to create content, execution stops immediately and no AI call is made.
Once authentication and permissions pass, the request is validated. Aimogen checks that the input is complete, that the requested post type is allowed, and that the requested operation is permitted for the caller. Only after validation does the AI execution phase begin.
During execution, Aimogen selects the appropriate provider and model based on configuration, availability, limits, and fallback rules. If embeddings, assistants, or structured generation rules are part of the request context, they are applied exactly as they would be in the UI. This ensures that content created via REST is consistent with content created manually.
The generated content can be returned directly in the API response, saved as a WordPress post, or both, depending on how the request is structured. Saving content is always explicit. Aimogen does not silently publish content unless instructed to do so.
REST-based content creation supports the same concepts as UI-based generation. You can generate drafts or published posts, target specific post types, control categories and tags, and decide whether metadata is generated alongside content. The REST API does not force publication and does not skip editorial states.
Because REST execution is fully logged, every content creation request appears in Usage Logs, Execution Logs, and statistics. This applies equally to successful executions, blocked executions, and failures. From an operational perspective, REST-generated content is never invisible.
Bulk content creation via REST is possible, but it is intentionally constrained. Bulk execution respects limits strictly and stops cleanly if limits are reached. Partial results are preserved, and no hidden retries occur. This makes REST-based automation safe even when running unattended.
Content creation via REST is also fully compatible with OmniBlocks workflows. Instead of directly requesting content generation, an external system can trigger a predefined OmniBlocks pipeline. This allows complex, multi-step content creation with validation, transformation, enrichment, and structured output, all initiated via a single API call.
One important distinction is that the REST API does not replace WordPress editorial control. Generated content still lives inside WordPress, uses WordPress post types, and follows WordPress rules. Revisions, statuses, and permissions all apply normally. The API is an execution interface, not a content bypass.
Common use cases for creating content via REST include headless WordPress setups where content is generated from an external frontend, ERP or CRM systems that trigger documentation updates, MCP-based agents that orchestrate AI writing, and automated pipelines that generate or update content on a schedule.
What the REST API does not do is expose raw provider completions, stream tokens freely, or allow anonymous content creation. Those constraints are deliberate and ensure that programmatic content creation remains safe, auditable, and cost-controlled.
In practice, the safest way to use REST-based content creation is to first design and test generation behavior in the Playground or UI, then reuse those proven configurations via REST. This avoids deploying untested prompts or unstable behavior into automation.
Creating content via the Aimogen REST API turns Aimogen into a programmable AI publishing engine. You gain automation and integration without losing permissions, limits, observability, or editorial safety.
