Reesha
The publishing layer for AI agents

Give your AI agent a safe place to publish.

Codex, Claude, OpenClaw, Hermes, and any MCP client can draft, adapt, schedule, and publish on X in this beta, while you keep one clear calendar and the final say. Drafts for LinkedIn and Bluesky stay editable; publishing to them is not available yet.

Join the waitlistSee the MCP workflow
Remote MCP Revocable keys Human-visible queue
Codex · Reesha MCP
Agent session
Turn the launch note into a short X post, then schedule it for tomorrow morning.
social_sets_list
posts_create
posts_schedule

VISIBLE IN REESHA

Launch note

Tomorrow · 9:00 AM

Scheduled

We built a calmer way for one real idea to travel across every audience.

X
Unstarted drafts and schedules remain editable.
One agent conversation becomes a reviewable, brand-aware publishing workflow.
WORKS WITH Codex Claude OpenClaw Hermes Any MCP client

Connect once

From MCP URL to scheduled post in four steps.

Reesha gives remote and local agents the same controlled publishing surface. No custom social API integration inside every agent.

  1. 01

    Connect your Brand

    Add the social accounts your agent is allowed to publish through.

  2. 02

    Create a revocable key

    Give each agent its own key, so access stays visible and easy to remove.

  3. 03

    Add the remote MCP URL

    Paste one Streamable HTTP endpoint into Codex or any MCP client.

  4. 04

    Ask your agent to publish

    Draft, edit, schedule, publish, or clean up posts through natural conversation.

AI & Agents

Connect assistants to your workspace so they can draft and schedule posts through Reesha.

CodexLet cloud Codex tasks draft, schedule, and manage posts.
ClaudeConnect Claude to draft, schedule, and manage posts.
OpenClawGive OpenClaw the same controlled publishing tools.
HermesUse Hermes with Reesha's remote MCP endpoint.

API keys live in one place

Give each assistant a revocable key, then connect it with the same remote MCP endpoint.

Open API keys

Safe by design

Agents do the work. You keep the context.

Reesha is the shared publishing layer between autonomous agents and the humans responsible for the Brand. Nothing disappears into a background automation.

One key per agent

Create, reveal, revoke, or delete access without disconnecting another client.

Workspace isolation

A key stays inside its workspace and cannot reach another team’s Brands.

Human-visible work

Agent drafts and schedules appear in the same editor and calendar you use.

Reesha Brand

Publishing queue · Africa/Algiers

X beta

Codex

Launch note

9:00 AM

X

Hermes

Behind the build

12:30 PM

X

You

Friday reflection

5:00 PM

X

Editable ReschedulableOne shared calendar
An ink illustration of a creator shaping one idea into a coordinated publishing flow

Agents and people, together

Automation carries the work. People keep the voice.

Start with Codex, Claude, OpenClaw, Hermes, your own REST workflow, or the Reesha editor. Every draft returns to the same Brand-aware queue, ready for a person to review or reshape.

Agents can draft, adapt, schedule, and publish

People can edit, reschedule, or take over

One shared calendar keeps the context visible

Pay as you go · powered by Polar

One wallet for the people and agents in your workspace.

Every $1 adds 100 credits through a manual top-up. X publishing uses 4.5 credits per plain segment or 60 per segment containing a link. Scheduling holds the future cost; AI, research and media estimates do not currently debit the publishing wallet.

Join the waitlistSee pricing