Every scheduler publishes the post. Yours can make sure people engage with it.

Launch at publish, not at schedule. A post that is rescheduled, edited or deleted before it goes live costs nothing, and the boost always lands on the real URL.

curl -X POST https://api.productclank.com/api/v1/agents/campaigns/boost \
  -H "Authorization: Bearer $PC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "post_url": "https://x.com/acmeuser/status/1234567890",
    "action_type": "replies",
    "count": 10,
    "spread_over_hours": 6,
    "post_text": "We just shipped offline mode…",
    "post_author": "acmeuser",
    "reply_guidelines": "Genuine reactions only. Mark every reply as a paid partnership."
  }'

# → { "campaign": { "id": "CAMPAIGN_ID", "action_type": "replies", … }, "delivery": { … } }

• Send post_text and post_author. You wrote the post, so you have them. It skips our fetch, which is the step most likely to fail on a post that is seconds old.
• Read campaign.action_type back. An action the platform does not support falls back to replies at the replies price. quote on a LinkedIn URL is charged as replies.
• Write campaign.id to the order at once. It is returned exactly once.
• A TikTok seconds old may not have its caption yet. The call waits up to 8 minutes for it and bills only once it drafts. No caption means the campaign closes and nothing is charged.

curl -X POST https://api.productclank.com/api/v1/agents/campaigns/boost \
  -H "Authorization: Bearer $PC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "post_url": "https://www.tiktok.com/@acmeuser/video/7400000000000000000",
    "action_type": "replies",
    "count": 10,
    "watch_quiz": {
      "questions": [{ "question": "How many steps does the demo take?", "answer": 3 }],
      "max_answers": 5
    }
  }'

Your user writes the question: they made the video, and only they know the answer. The quiz runs 24 hours. It bills 100 credits per correct answer, up to max_answers, and wrong answers are free. That charge is not in credits_used, so price the worst case. If the quiz fails, the paid boost stays and the response carries watch_quiz.error.

curl "https://api.productclank.com/api/v1/agents/campaigns/CAMPAIGN_ID/activity" \
  -H "Authorization: Bearer $PC_API_KEY"

# → { "claimed_replies": [ { "posted_url": "https://x.com/someone/status/…", "reply_text": "…",
#       "claimed_at": "…", "review_status": null, "survival_status": "alive",
#       "engagement": { "likes": 4, "replies": 1 } } ] }

Each posted_url is a result the moment it appears; posted_url: null means a person claimed the slot and has not posted yet. It is free and read-only, so call it when the user opens their post, not on a timer. Do not use /posts for results: it returns drafts without the published URL.

• Disclosure is mandatory. Put “paid partnership” in reply_guidelines on every boost. We audit.
• Never sell likes or repost. The API accepts them; a partner may not offer them. Bought engagement gets the accounts of the people doing the work penalised, not your user's.
• Boost what your users wrote. Only posts a user scheduled through you, on their own accounts. Not other people's posts.
• No misrepresenting the network. The people who answer are not your staff or your bots. Don't invent follower counts or promise engagement numbers.
• One key, one product. Violations end the account and forfeit remaining credits.