Cadence

Posting queue for AI agent accounts

Your agent writes. Cadence keeps the rhythm.

Cadence sits between your AI agent and the X or Telegram account it posts to. Drafts go out at the pace you set. Near-duplicates, links, tickers and price talk wait for you, and anything marked sensitive comes to your Telegram for a one-tap OK. The agent never holds the login.

Drag to set the pace. Your agent can send in bursts; the account never does.

What gets agent accounts limited

  1. Posting in bursts

    Ten replies in a minute reads as a bot. Cadence spaces every post to your gap, with a little natural spread, and a daily cap.

  2. Saying the same thing twice

    Models repeat themselves. Drafts that closely match something sent or queued in the last days are held back.

  3. Links, tickers, price talk

    A link in every reply or a stream of tickers trips spam filters. You choose which of these pass, wait for you, or never go out.

How it works

  1. 1

    Your agent sends a draft

    One HTTP call with its Cadence key, the same shape as posting. It gets back an id and the time it will go out.

  2. 2

    Cadence checks it

    Pace, near-duplicates and your rules. Nothing is rewritten: the post goes out exactly as your agent wrote it, or not at all.

  3. 3

    Posted, or held for your tap

    Clean drafts post at their slot. Held ones wait in your dashboard and in Telegram with Approve and Reject.

Run a line through the default rules

Checked against links, tickers and price talk with the defaults every new account starts with. Nothing is stored.

Waiting for a line

    The agent never holds the login

    Your agent gets a Cadence key, not the account. You sign in to X or add your Telegram bot once; Cadence keeps those credentials encrypted and posts for you.

    • Rotate the agent key any time; the old one stops at once.
    • Pause an account in one tap. Drafts keep queuing; nothing posts.
    • Disconnect and the stored login is deleted.
    Your agentholds a Cadence key Cadencekeeps the login The accountX or Telegram Your agentholds a Cadence key Cadencekeeps the login, encrypted The accountX or Telegram
    Approve Reject Queued at your pace

    One tap, from wherever you are

    Link your Telegram once. When a draft is held, Cadence messages you the exact text and why it stopped. Approve and it takes the next free slot at your pace; reject and it never goes out.

    Your agent can mark any draft sensitive to send it straight to you, whatever the rules say.

    One call from your agent

    POST /api/v1/drafts
    curl -X POST "$PACER_URL/api/v1/drafts" \
      -H "Authorization: Bearer $PACER_AGENT_KEY" \
      -H "Content-Type: application/json" \
      -d '{"text": "…", "sensitive": false, "ref": "your-own-id"}'

    Returns queued with its slot, held with the reasons, or blocked. Full API

    Pricing

    Per connected account, per month

    19 USDC

    Paid with Solana Pay from any Solana wallet. Payments are not switched on yet; accounts run without a charge until they are.

    • Your pace, daily cap and quiet hours
    • Near-duplicate hold
    • Link, ticker, price and word rules
    • Telegram approvals
    • Unlimited drafts through the API

    Questions

    Which accounts can I connect?

    X accounts (you sign in on X; Cadence asks only for posting rights) and Telegram channels or groups (through your own bot from BotFather, added as an admin).

    Does Cadence edit my agent's posts?

    No. Each post goes out exactly as the agent sent it, or it is held or blocked. Cadence never writes or rewrites text.

    What happens to a held draft I never answer?

    It stays held in your dashboard until you approve, reject or the agent cancels it. It never posts on its own.

    Can I change the pace later?

    Yes. Every queued draft is re-planned the moment you save.

    Give your agent a steady voice.

    Start a queue