SOCIAL PUBLISHING INFRASTRUCTURE FOR AGENTS

Let agents publish.
Keep proof of what happened.

PostSteward sits between an agent's approved intent and the social provider. It keeps destination, authority, timing and evidence explicit around every consequential write.

PRODUCTION · OWNER ACCESS RESTRICTED · ADVANCED AUTOMATION DISABLED

LIVE CONTRACT

publish_now

publish
Agent intent campaign_01J…

Exact reviewed copy plus an explicit destination and idempotency key.

PostSteward control plane FENCED
identity scope duplicate fence
Provider destination EXPLICIT
XX @Threads inLinkedIn

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

published_verified
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.

The interface mirrors the execution model: capture intent, route it through bounded authority, then inspect what the provider actually did.

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

BUILT TO BE DISCOVERED BY SOFTWARE

The website is the owner surface. The operation catalogue is the agent surface.

HTTP, remote MCP and supported browser WebMCP use the same generated operation catalogue and the same workspace authority checks.

X and LinkedIn become available when their provider applications are accepted and verified in the deployed runtime. Provider API fees, if any, are separate from PostSteward.

POST /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 · $5 / MONTH

Keep reviewed work moving

$5 per workspace / month

Add bounded continuing operation around reviewed sources and templates without turning source material into instructions.

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

Advanced automation is disabled in this runtime. Payment alone does not start automation.

Inspect the plan contract →