Blogent

AI SEO blog for Replit

Instead of a fixed package, Replit gets an installable Agent Skill. Agent adapts the same verified publishing contract to the framework, blog, database and storage the app already uses, adds a protected idempotent endpoint and writes automated tests for it.

How to connect Blogent to Replit

Install Blogent in Replit

Use the installable Blogent Agent Skill in an existing Replit app, or open the prepared build directly in Replit. Agent adapts the same verified publishing contract to the framework, blog, database, and storage already used by the site.

Open in Replit
  1. Install it in the right project

    For an existing site, use the one-line install command below inside that Replit project. For a new build, click Open in Replit.

  2. Let Agent implement and verify it

    The installed skill makes Agent reuse the current blog and add the protected, idempotent publishing endpoint plus automated tests. Add BLOGENT_WEBHOOK_TOKEN through Replit Secrets when Agent asks.

  3. Publish, connect, and test

    Approve the Replit deployment, enter the endpoint and X-Blogent-Token in Blogent, then run inventory, create, read and update of the same real article.

Already have a Replit app?

Run this one command in that project’s Shell. Then ask Agent: “Use $blogent-publisher to connect this app.” The skill remains installed in the project for future repairs and updates.

npx skills add https://blogent.tools/integration/replit/SKILL.md --skill blogent-publisher -a replit -y
Values to copy into Blogent
Webhook URL
https://your-domain.com/api/blogent/webhook
Header name
X-Blogent-Token
Replit Secret
BLOGENT_WEBHOOK_TOKEN

Actions and stable identities

  • Shopify, HubSpot, Webflow and Framer use the connected native publisher. WordPress, OpenCart, Strapi and Lovable use the installed Blogent connector; v0 and Replit adapt it to the existing app. Wix, Make, n8n and custom endpoints implement the synchronous contract; Zapier, Albato and ApiX-Drive use completion callbacks.
  • inventory: send cursor: null and limit; return {articles: [snapshot], next_cursor: string|null}. Repeat the returned cursor until null.
  • read: send target and/or content_id; return {article_snapshot: snapshot}. Explicit native target is authoritative. Blogent’s logical content_id may differ from the native identity.
  • Each snapshot contains identity, title, alias, date, article, target, revision, urls and optional image/author metadata. article maps locales to full title, alias, HTML, preview and SEO fields. Unknown original dates may be null and unavailable URLs may be an empty map.
  • create: send the article payload, a unique operation_id, logical content_id, empty target and null expected revision. Return {posted:true,target,revision,urls} after complete publication.
  • update: send existing native target IDs and the latest expected_revision. Preserve original IDs, URLs/aliases, publication date, author and assets. Compare the revision atomically before applying changes.
Universal webhook contract

Blogent supports inventory, authenticated read, create and in-place update. Final receipts include native target IDs and revision; queued workflows complete through authenticated callbacks.

Open webhook documentation

Webhook tester

Run inventory, create, read and update on one real test article. Queued integrations wait for their completion callbacks.

Reference only. The test generates fresh IDs once and reuses them while polling.

What you get after connecting Replit

  • Agent reuses your existing blog, database and storage instead of forcing a new structure onto the project.
  • The skill stays installed in the project, so it can be used again for later repairs and updates.
  • The generated endpoint is protected and idempotent, and Agent adds automated tests for it.
  • Existing apps are covered by a one-line install command; a fresh build can be opened directly in Replit.
  • Blogent reads existing native articles and updates them with revision checks while preserving original IDs, URLs, dates, authors and assets.

Requirements and compatibility

Platform
A Replit project — either an existing app or a new build opened from this page.
Install
One command in the project Shell, then ask Agent: “Use $blogent-publisher to connect this app.”
Secret
BLOGENT_WEBHOOK_TOKEN, added through Replit Secrets when Agent asks.
Connection
The public endpoint returned by Agent, plus the X-Blogent-Token header with the same secret.
Verification
The connection test inventories existing content, creates one real article, reads its authenticated snapshot and updates the same native IDs. No public-page crawl is required.

Frequently asked questions about the Replit integration

Will this overwrite the app I already have?

No. Agent works with the framework, blog, database and storage already in the project and adds the publishing endpoint alongside them.

Where do I run the install command?

In the Shell of the Replit project that should receive articles. For a brand-new build, use Open in Replit instead.

Do I get tests?

Yes. The skill makes Agent add automated tests for the publishing endpoint.

Does the skill stay in the project?

Yes, so you can ask Agent to repair or update the integration later without reinstalling anything.

Put your SEO blog on autopilot

Create a blog, connect Replit, and Blogent will plan, write, link, and publish articles automatically.

Start now

Similar integrations

Lovable v0 WordPress OpenCart