Docs›Modules›Content
Module abilities-for-ai · free tier · updated 2026-03-17

Content Module

Create, read, update, and delete WordPress posts, pages, and custom post types. The foundation of everything content-related in the Abilities API.

abilities-for-ai free content read write delete
17
Total
10
Read
5
Write
2
Delete

Overview

The Content module manages WordPress WP_Post objects — posts, pages, and any registered custom post type. It wraps WP_Query, wp_insert_post(), wp_update_post(), and wp_delete_post() behind a consistent, permission-aware interface.

All write and delete abilities are pro-gated by default. Read abilities are available on the free tier. The permissions filter wp_abilities_suite_permissions controls access per user role.

Block markup notecontent/get returns raw Gutenberg block markup. If you pass this directly to content/update, the block structure is preserved. Use the Blocks module (blocks/parse, blocks/insert) to surgically modify content without touching the full post.

Ability Reference

AbilityTypeDescription
content/listRList posts with filtering by post_type, status, author, taxonomy terms. Supports pagination.
content/getRGet a single post by ID. Returns full block markup in post_content.
content/get-textRGet a post's readable text content with block markup and HTML stripped.
content/get-by-slugRRetrieve a post by post_name (slug) and post_type.
content/find-by-urlRFind a post by its full permalink URL. Useful when you have a URL but not an ID.
content/get-snapshotRComplete post data in one call: fields, all meta, taxonomy terms, and author info.
content/get-site-mapRFull hierarchical page tree — ID, title, slug, parent, and children.
content/list-structureRList post metadata without loading the content field. Fast for structural surveys.
content/discover-typesRList all registered post types with their capabilities and REST support status.
content/searchRFull-text search across post titles and content with relevance ordering.
content/createWCreate a new post. Accepts post_type, title, content (block markup), status, date, meta.
content/updateWUpdate an existing post. Accepts any post fields. Preserves block structure if content is omitted.
content/appendWAppend block markup to the end of an existing post without reading first.
content/search-replaceWBulk find-and-replace in post_content. Supports dry_run, post_type filter, post_ids filter.
content/change-typeWConvert a post between post types. Returns old/new permalink; warns about orphaned taxonomy terms.
content/deleteDMove a post to trash (default) or permanently delete with force: true.
content/batch-updateWUpdate multiple posts in a single call. Accepts an array of post objects with IDs.

Common Workflows

Publish a blog post

1. content/create        → post_status: "draft", post_type: "post"
2. taxonomies/assign     → attach category + tag term IDs
3. media/upload          → upload featured image, get attachment ID
4. meta/update-post-meta → set _thumbnail_id to attachment ID
5. content/update        → post_status: "publish"

Survey site content structure

1. content/discover-types     → see all post types
2. content/get-site-map       → hierarchical page tree
3. content/list-structure     → posts list without content (fast)
4. taxonomies/list-terms      → categories and tags in use

Surgical content edit

1. blocks/parse              → get block array from post_content
2. blocks/find-in-post       → locate target block by type/attribute
3. blocks/update-attributes  → change only what needs changing
4. content/update            → write modified block markup back
Blocks Module
13 abilities — surgical block editing
Taxonomies Module
9 abilities — categories and tags
Meta Module
13 abilities — post meta fields
Revisions Module
5 abilities — version history

Known Gotchas

Block markup preservationIf you pass a plain string (not block markup) to content/update as post_content, WordPress will save it as a Classic block. Always use blocks/serialize if you're constructing content programmatically.
post_author not yet supportedcontent/create and content/update do not accept a post_author parameter. Posts default to the bridge user. Known gap — GitHub issue filed, queued for next sprint.
search-replace on large sitesAlways use dry_run: true first. On sites with thousands of posts, consider using post_ids to batch the operation.