PostSteward
Menu

GET STARTED

Start publishing with PostSteward

Start with a hosted workspace. Connect accounts, create a project and review a post. You can add an agent or local runtime when you need one.

Start with your workspace. Sign in with Google, connect your accounts through OAuth, then create a project and review your first post. Agent access is optional.
  1. [01]

    Connect a publishing account

    Sign in with Google and connect X or Threads through OAuth. PostSteward verifies the account identity before publication. LinkedIn Page access will become available after provider approval.

    Create your workspace
  2. [02]

    Create a publishing project

    A project groups the accounts an agent is allowed to use and gives each one a stable alias. The agent references the alias, not raw credentials.

    Create a publishing project
  3. [03]

    Review, schedule and check the result

    The agent submits exact copy as an immutable campaign, validates it, then publishes now or on an explicit schedule. Every attempt returns a durable receipt the agent must read instead of retrying blindly.

    In your workspace, enter exact copy under Create & schedule, validate it, then choose a date or publish now. Agent-created deliveries need owner approval in Schedules & results.

    HTTP example for agent developers
    ┌─ Create and publish
    curl -X POST https://app.poststeward.com/api/operations/campaign_create \
  -H "Authorization: Bearer <agent token>" \
  -H "Content-Type: application/json" \
  -d '{
    "project":"<project id>",
    "text":{"<account alias>":"The exact text to publish."},
    "idempotencyKey":"campaign-001"
  }'

curl -X POST https://app.poststeward.com/api/operations/publish_now \
  -H "Authorization: Bearer <agent token>" \
  -H "Content-Type: application/json" \
  -d '{"campaign":"<campaign id>","idempotencyKey":"publish-001"}'
  4. [04]

    Optional: connect an agent

    Create a token limited to the operations the agent needs, with an expiry. The token is shown once. Give it to the agent as a Bearer credential over remote MCP or plain HTTP.

    MCP configuration for your agent
    ┌─ MCP client configuration
    {
  "mcpServers": {
    "poststeward": {
      "url": "https://app.poststeward.com/mcp",
      "headers": { "Authorization": "Bearer <agent token>" }
    }
  }
}
    Create agent token

Check the result

Receipts record the delivery status, the verified account and the published link when the provider confirms one. An uncertain result stays uncertain until it is resolved; the agent must not repeat the call.

Receipt lookup for agent developers
┌─ List receipts
POST https://app.poststeward.com/api/operations/receipts_list
{ "limit": 50 }

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

Owner approval comes before agent publication

Each agent-created delivery waits for the owner to review the exact copy, account and time. Only the signed-in owner can approve it. Payment access does not grant publishing permission.

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