root@poststeward:~$ man poststeward

Everything an agent needs to publish and prove it

One operation catalogue, reachable over remote MCP or plain HTTP, with the same execution rules and durable receipts on both. Browser WebMCP registers the same scoped operations on a connected workspace.

Connect

The owner signs in, connects a publishing account, binds a project and issues a scoped token. Store that token in the agent's secret manager. Remote MCP uses a Bearer header; OAuth discovery is not required for this flow.

{
  "mcpServers": {
    "poststeward": {
      "url": "https://app.poststeward.com/mcp",
      "headers": { "Authorization": "Bearer <agent token>" }
    }
  }
}

POST https://app.poststeward.com/api/operations/<operation>
Authorization: Bearer <agent token>
Content-Type: application/json

{ ...operation input }

// Real connected workspace in a supported browser
const tools = await document.modelContext.getTools({ fromOrigins: [] });
const status = tools.find(tool => tool.name === "workspace_status");
// Execute only within the scopes granted to the signed-in actor.

Scopes

A token carries only the scopes you grant, plus an expiry. Recommended for publishing: read, campaign:write, publish, schedule. Grant billing, connections or automation only when those actions are intended.

read

Inspect status, accounts, projects, campaigns, receipts, metrics and export.

campaign:write

Create project routing and store immutable campaign text.

publish

Publish now and pause or resume publishing.

schedule

Reserve, cancel and replace explicitly scheduled deliveries.

connections

Disconnect a publishing account and block its unclaimed work.

automation

Configure, preview, enable and pause continuing operation.

billing

Quote, checkout and open the billing portal.

A first publication

Resolve destinations explicitly, store the exact approved text, validate, then publish or schedule. Every mutation uses an idempotency key. A publication call returns receipt IDs; the receipt is the authority on the result.

# 1 — resolve explicit destinations
POST https://app.poststeward.com/api/operations/projects_list
{}

# 2 — store exact approved text
POST https://app.poststeward.com/api/operations/campaign_create
{ "project":"product",
  "text":{"product_x":"The exact approved update."},
  "idempotencyKey":"campaign-2026-001" }

# 3 — dry-run routing and provider text rules
POST https://app.poststeward.com/api/operations/campaign_validate
{ "campaign":"<campaign id>" }

# 4 — publish once
POST https://app.poststeward.com/api/operations/publish_now
{ "campaign":"<campaign id>",
  "idempotencyKey":"publish-2026-001" }

POST https://app.poststeward.com/api/operations/schedule_create
{ "campaign":"<campaign id>",
  "at":"2026-10-01T12:00:00Z",
  "timezone":"UTC",
  "idempotencyKey":"schedule-2026-001" }

POST https://app.poststeward.com/api/operations/receipts_list
{ "limit":50 }

POST https://app.poststeward.com/api/operations/receipt_get
{ "delivery":"<delivery id>" }

Operation catalogue

The catalogue is fixed. Each operation declares its required scope and consequence before it runs.

Rules the agent must follow

Receipt states

A receipt is the authority on what happened. There is no promise of exactly-once execution at an external provider; PostSteward prevents blind repetition after uncertainty.

scheduled

Durable reservation; nothing published yet.

waiting_container

Threads container created; readiness checks pending.

executing

Dispatch owns a durable claim.

published_verified

Provider ID, author and exact content read back.

published_unverified

Creation ID stored; exact readback unavailable.

ambiguous_effect

The provider may have published. Blind retry is blocked.

drift_blocked

Account, payload or authority changed since reservation.

failed

A known pre-publication or provider rejection.

cancelled

An unclaimed reservation was cancelled.

Limits and retention

• —20 delivery reservations per UTC day, shared across Free and Advanced.
• —100 active schedules per workspace.
• —Provider API charges are separate; there are no automatic overage charges.
• —Revoking an agent token blocks future execution under that grant.
• —Source monitoring runs every 15 minutes; scheduled metrics run daily for recent receipts.

To recover safely, inspect the receipt and the provider account before acting. Never delete the ledger to enable a second attempt.

Original release preparation

Connect your workspace’s own OpenAI or Cloudflare model account, select release evidence and approved audience/context, then inspect strategy and original channel drafts. Your selected customer account funds inference; PostSteward never supplies or delegates a shared company key.

Model checks assist review. Only the owner approves exact saved copy, and publication is a separate action. Local executors use reviewed copy export/import before local scheduling. Open release preparation or read the full preparation contract.

Next

Owner approval comes before agent publication

Manual agent deliveries require owner review of exact copy, account and time. Separately, the signed-in owner may configure bounded standing project authority; clean recurring work can then proceed without per-copy review while source, account, scope, spend and editorial checks hold. The owner may inspect and pause that authority. Payment alone never grants publishing permission.

Using a local executor? Read the installation and remote agent guide. Use the current 50-operation catalogue for hosted and local-executor operations.

Choose model and funding deliberately

Owner settings support Cloudflare Workers AI and OpenAI through prepaid Cloudflare AI Gateway Unified Billing, plus existing direct OpenAI. Choose a reviewed model, job/day budgets and optional fallback. Saving validates metadata without generating content or changing billing. Credits and provider charges belong to your account; PostSteward supplies no hidden company-funded fallback.

Live customer billing and human quality acceptance are pending. Check private model status and attempt evidence before relying on a route. Approval still creates exact reviewed copy for a separate delivery action.