Hermes agents publish to WordPress with one HTTP call.

Setup in three steps

1. 1

   Get your API key

   Sign up at notipo.com and copy your API key. Add it to your Hermes environment as NOTIPO_API_KEY (or whatever secret store Hermes uses).
2. 2

   Add Notipo to a Hermes task

   Most Hermes tasks call HTTP endpoints as part of their plan. Add a step that POSTs to /api/posts/direct with the post body — title, markdown content, category, SEO keyword, publish flag.
3. 3

   Wire the response back into memory

   Notipo returns the live WordPress URL. Hermes can store it in working memory so the next iteration of the self-improvement loop knows what it's already shipped — useful for avoiding duplicate posts and chaining follow-up content.

The config

Drop this in. Replace your-api-key with the key from your Notipo dashboard.

# Hermes — publish a WordPress post via Notipo# In a Hermes task or self-improving routine, send one HTTP request:POST https://notipo.com/api/posts/directHeaders:  X-API-Key: $NOTIPO_API_KEY  Content-Type: application/jsonBody:{  "title":      "{{ task.title }}",  "body":       "{{ task.body }}",  "category":   "{{ task.category }}",  "seoKeyword": "{{ task.seo_keyword }}",  "publish":    true}# Hermes can publish from:#   - A research task that summarized findings into a post#   - A self-improvement loop documenting what it learned#   - A scheduled task that batches drafts and publishes weekly## Notipo returns 201 with { id, wpPostId, url }.# Hermes can then store the live URL in its working memory.

What your agent can do

• Auto-publish research summaries from long-running Hermes tasks
• Document self-improvement findings as public-facing blog posts
• Run a Hermes task that batches drafts and publishes weekly
• Combine with Hermes's research tools — finding citations, then publishing
• Keep Hermes as the planner; let Notipo handle the WordPress mechanics