WordPress
Creates and updates the post through the WordPress REST API and uploads the hero image to your media library. Unpublishing sets the post back to draft.
You give Ryterr: Your site address, plus an Application Password or a bearer token.
Integrations
Ryterr sends each finished post to WordPress, Ghost or GitHub, to your own code through a signed webhook, or to the Content API your site reads from.

Add a connection once under Connections. Each one takes the same finished post.
Creates and updates the post through the WordPress REST API and uploads the hero image to your media library. Unpublishing sets the post back to draft.
You give Ryterr: Your site address, plus an Application Password or a bearer token.
Creates and updates the post with its feature image through the Admin API. Unpublishing sets the post back to draft.
You give Ryterr: The Admin API key of a custom integration.
Commits one Markdown file with frontmatter per post to the folder you choose. Unpublishing removes the file. A good fit for sites that build from a repository.
You give Ryterr: The repository, branch and folder, plus a token that can write its contents.
Sends the finished post to a URL you own. Each request is signed so your code can check it came from Ryterr, and a failed delivery is tried again.
You give Ryterr: A receiver URL on your site.
Your site reads the posts published to this connection over read-only REST and renders them itself. Pair it with a webhook to refresh the page the moment a post goes live.
You give Ryterr: An API key from Settings, API keys.
Hashnode, Dev.to and Notion are not offered. Every post also exports as Markdown and HTML, and the webhook reaches any site that can run code.
WordPress and Ghost receive the title, HTML, slug, excerpt and feature image. GitHub receives a Markdown file with frontmatter.
The webhook and the Content API carry all four parts.
Markdown and sanitized HTML, so you can render it or store it as is.
Title, slug, excerpt, meta description, keywords, and Open Graph and X card fields.
A hero image and inline images with their alt text and addresses.
Author, category, tags, dates, reading time and how many sources and statistics the post uses.
When the fact check leaves a warning open, such as a claim it could not confirm, the post is marked for review. A scheduled run stops there and holds the post for you instead of publishing it.
You can still publish it by hand. Ryterr asks you to confirm that you have read the warning first.
A failed webhook delivery is retried after 1 minute, 5 minutes, 30 minutes, 2 hours and 12 hours. After the sixth attempt Ryterr stops and sends you a notification.
Every attempt is listed under Recent deliveries on the connection, and you can replay one. Each event carries the same id on every retry, so your receiver can ignore a repeat.
The Next.js guide covers blog pages that read the Content API and a webhook receiver that refreshes them, with working code and a prompt for your coding agent.
Something else on your mind? Write to us.

Two posts free, no card needed. Connect a site when you have a post worth publishing.