WordPress integration
Connect your site with an Application Password and Contengi puts an agent directly on your WordPress blog. It reads every post you have, writes new ones in your voice, edits the old ones and publishes back to the same URL.
Read, write, publish, edit, republish
The CMS lists every post on your WordPress site, newest first, with what is live and what is still a draft. Open any of them, including posts Contengi never wrote, and the agent works from the real HTML.
Content library and CMSThe SEO agent researches the keyword, reads your knowledge base and hard rules, and drafts the post. Four slop filters run before you ever see it.
Content agentsPosts go out through the WordPress REST API with the title, slug, excerpt, FAQ and featured image set. You choose whether new posts land live or as drafts, and which category they file under.
Content library and CMSAsk the edit agent to tighten an intro, add a section or fix a stat. It changes only what you asked for, checks the links and shows you a diff you can revert.
Content library and CMSAn edited or refreshed post goes back over the original. If Contengi cannot find that original, the publish stops, so a second copy never appears at a new address.
Content agentsConnect Contengi to Claude and the same blog is one chat away. Claude can open a live post, edit it section by section and leave it waiting for you to publish.
Claude connectorUnder the hood
Contengi talks to the REST API that ships with every WordPress install, so there is nothing to add to your site and nothing to keep updated.
FAQ
No. Contengi uses the REST API that is built into WordPress and authenticates with an Application Password, which WordPress has included since version 5.6.
Yes. The CMS lists every post on the site. Open one and the agent reads its real HTML through the REST API, edits the sections you ask for and publishes the result back over the same post.
Contengi sets the title, slug, excerpt, body, FAQ and featured image. Fields that belong to an SEO plugin stay with that plugin, so set those in WordPress.
Almost always one of three things: the site is not on https, permalinks are set to Plain, or a security plugin is blocking /wp-json. Contengi names which one when the test runs.
It is built for self-hosted WordPress. A WordPress.com site works if its plan exposes the REST API and Application Passwords.
Keep exploring