SOCIAL PUBLISHING INFRASTRUCTURE FOR AGENTS

Let agents publish.
Keep proof of what happened.

Give your agent access to publish approved copy on X and Threads, with explicit schedules and receipts showing what happened. You control the accounts and permissions. LinkedIn Page access requires provider approval.

Sign in with Google. Connect your accounts and approve what your agents publish.

EXAMPLE PUBLISHING FLOW

publish_now

publish
Reviewed post campaign_01J…

Exact reviewed copy plus an explicit destination and idempotency key.

Your publishing rules FENCED
identity scope duplicate fence
Connected social account EXPLICIT
XX @Threads inLinkedIn

post id recorded · stable author matched · exact text read back

published_verified

Where do you want to start?

Run PostSteward on your machine.

Install the full runtime, pair it with your owner workspace and choose one publishing executor.

Need original release copy? Connect your own model account to prepare strategy and channel drafts from release evidence, then review and approve exact copy before delivery. Your selected customer account pays for generation; PostSteward subscription charges are separate.

Install PostSteward
curl -fsSL --proto '=https' --tlsv1.2 https://poststeward.com/install.sh | bash

Read the PostSteward installer at poststeward.com/install.sh

Linux, macOS 15/26 and WSL 2 (Ubuntu 24.04) · Bash · Python 3.10 or newer. Native installation and guarded lifecycle checks passed. Review owner pairing and provider publication on your own machine before activating. Full installation guide.

INTENT Exact approved copy

Dispatch never silently rewrites the campaign.

AUTHORITY Scoped, revocable agent access

Publishing, scheduling, automation and billing stay separate.

EVIDENCE Receipts, not assumptions

Verified, unverified and ambiguous effects remain distinct.

ONE PUBLISHING PATH

A post moves through one deliberate sequence.

Connect an account, review your text, choose when to publish and check the result. You stay in control of what your agent may do.

01 · CAPTURE INTENT

Make the consequential details explicit before dispatch.

Campaign text, destination and project routing become a durable claim boundary before any social provider is touched.

  • Exact copy remains exact at dispatch.
  • Destination identity is resolved before the write.
  • An idempotency key belongs to the operation, not the transport attempt.
CAMPAIGN REVIEW
Project proof-and-state
Destination @proofandstate · Threads
Approved text Agents can publish autonomously without making the outcome unknowable. PostSteward keeps the intent and receipt together.
Claim boundary text hash · account id · operation idempotency key
02 · ROUTE THE EFFECT

Separate provider execution from transport noise.

A timeout is not permission to publish twice. PostSteward preserves the state of the external effect and makes an uncertain outcome inspectable.

  • Durable schedules survive the agent disconnecting.
  • Provider writes are fenced against blind duplicate retries.
  • Cancellation and replacement remain explicit operations.
DELIVERY · delivery_01J… schedule
Reservation claimed

Bound to the reviewed campaign and destination.

DURABLE
Provider request started

External effect fence recorded before dispatch.

EFFECT
Provider creation ID captured

Creation is evidence, but not yet exact readback proof.

OBSERVED
Exact post read back

Stable author and exact text matched.

verified
03 · INSPECT EVIDENCE

Success is one state. Uncertainty gets its own state too.

The receipt model is designed for operators and agents to reason from the same evidence instead of compressing every outcome into green or red.

  • Verified means the recorded post was independently read back.
  • Ambiguous means the write may have happened and should not be repeated blindly.
  • Blocked and failed states remain distinct from provider uncertainty.
RECEIPT LEDGER LATEST FIRST
published_verified

Post ID, stable author and exact text independently matched.

receipt_get
ambiguous_effect

Provider outcome is uncertain. Hold the fence and inspect before retry.

receipt_recheck
drift_blocked

Current authority or reviewed intent no longer matches the claim.

review
failed

No acceptable provider effect was established.

inspect

CONNECT AN AGENT

Connect your agent to approved publishing.

Let your agent submit reviewed copy, schedule it and inspect the result. Start with an owner-issued token limited to the operations it needs. Choose remote MCP or HTTP; supported browsers can also use WebMCP.

Keep approval and account connections in your workspace. Read the agent setup guide for CLI via HTTP, document.modelContext and the operation catalogue. Provider API fees, if any, are separate.

POST https://app.poststeward.com/api/operations/schedule_create
Authorization: Bearer <scoped-agent-token>

{
  "campaign": "RETURNED_CAMPAIGN_ID",
  "at": "2026-10-01T12:00:00Z",
  "timezone": "UTC",
  "idempotencyKey": "schedule-2026-001"
}

→ durable reservation
→ provider effect later
→ receipt_get for evidence

FREE AND ADVANCED

Pay for continuing operation, not permission to publish.

Direct reviewed publishing stays free. Advanced adds bounded monitoring and replenishment; payment never silently expands posting authority.

FREE · HOSTED

Direct the work

£0 service subscription

Publish approved campaigns, create explicit schedules and preserve the resulting evidence for both humans and agents.

  • Verified account routing
  • Publish now and explicit scheduling
  • Cancellation and reviewed replacement
  • Durable receipts and export
  • All supported agent transports
ADVANCED

Keep reviewed work moving

GBP monthly price to be confirmed

Monitor reviewed sources, fill your publishing queue from approved templates, space posts and collect scheduled metrics. You approve each automation profile; Advanced does not write original content or expand your agent’s permissions.

  • Source monitoring and replenishment
  • Rolling allocation and spacing controls
  • Scheduled metrics collection
  • Inspectable inventory and category state

Purchases open when the GBP monthly price is confirmed. Free publishing and scheduling are available now.

View Advanced in your workspace →

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.