Threads API for AI agents

Updated October 2026

How do you give an AI agent access to Threads?

Connect a Threads account to Chirpie once, then your agent posts through one call: POST /api/v1/posts from code, or the chirpie_post tool from Claude, ChatGPT or any MCP client. Chirpie handles Meta's sign-in and token refresh, publishes threads as native reply chains, schedules posts, answers replies and reports views and engagement for each post.

Connecting a new Threads account is coming soon. Accounts already connected publish, schedule and report analytics exactly as described below.

What Chirpie does on Threads

• Posts up to 500 characters, as text alone or with one image (JPEG, PNG, WebP or GIF, up to 5 MB).
• Threads of 2 to 25 parts, published as a native reply chain: each part replies to the one before. A thread is all or nothing: if a part fails, every part already published is deleted again and the quota is refunded. See Threads API.
• Scheduling and drafts: schedule_at queues a post or a whole thread, and draft: true saves it without sending. See Scheduling.
• First comment: first_comment publishes one reply under the post the moment it goes out, under the last part of a thread. A failed first comment never fails the post, and it can be sent again.
• Comments: list the replies a post received, reply to one, hide one, or delete your own reply. See Comments.
• Analytics: views, likes, reposts, replies and quotes per post. See Analytics.
• Delete: DELETE /api/v1/posts/:id removes a published post from Threads, and Chirpie keeps its record marked deleted.
• Several accounts at once: one request can publish to a Threads account and to X, Bluesky, LinkedIn or Mastodon side by side, each with its own text. See Post to several accounts at once.

Connect

A Threads account connects with Meta's own sign-in. Chirpie starts the flow and returns a link; the account owner approves Chirpie on Threads, and the account appears in GET /api/v1/accounts with the id every post uses. Chirpie stores the token encrypted and refreshes it before it expires.

The same flow is available everywhere Chirpie is:

• API: POST /api/v1/accounts with { "platform": "threads" } returns an authorization_url.
• SDK: chirpie.connectThreadsAccount().
• CLI: chirpie accounts connect-threads.
• MCP: the chirpie_connect_threads tool hands the link to you in chat.
• Dashboard: the Threads card on the Accounts page.

Post from code

A post with an image and a first comment:

curl -X POST https://chirpie.ai/api/v1/posts \
  -H "Authorization: Bearer chirpie_sk_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "account_id": "YOUR_THREADS_ACCOUNT_ID",
    "text": "We just shipped dark mode. Here is what changed.",
    "media_urls": ["https://example.com/dark-mode.png"],
    "first_comment": "Changelog: https://example.com/changelog"
  }'

A scheduled thread with the TypeScript SDK:

import { ChirpieClient } from "@chirpie/sdk";

const chirpie = new ChirpieClient({ apiKey: process.env.CHIRPIE_API_KEY });

await chirpie.createThread({
  account_id: "YOUR_THREADS_ACCOUNT_ID",
  posts: [
    { text: "1/ Three things we learned shipping an agent in production." },
    { text: "2/ Retries need idempotency keys, or they post twice." },
    { text: "3/ Every tool call should say what it is about to change." },
  ],
  schedule_at: "2026-10-12T09:00:00-04:00",
});

Post from Claude or ChatGPT

Chirpie is listed in the Claude Connectors Directory, so in Claude you add it from the listing and sign in, with no URL to paste. In ChatGPT developer mode, Cursor or any MCP client, add https://chirpie.ai/mcp and sign in. Then ask in plain language:

• "Post 'Dark mode is live' to Threads and X, and add the changelog link as the first comment on Threads."
• "Turn these notes into a five-part Threads thread and schedule it for Monday at 9am New York time."
• "Which of my Threads posts this week got the most replies? Draft answers to the questions."

Setup guides: Use Chirpie with Claude and Use Chirpie with ChatGPT. Every tool is listed on the MCP Server page.

Frequently asked questions

Does Chirpie publish a thread on Threads as a real reply chain?

Yes. Each part of a thread replies to the one before it, so it reads as one connected chain on Threads. A thread is 2 to 25 parts, and if any part fails, every part already published is deleted again so nothing is left half posted.

How long can a Threads post be?

Up to 500 characters per post. A longer thought is a thread, where each part has its own 500 characters.

Can a Threads post carry an image or a video?

One image per post, in JPEG, PNG, WebP or GIF, up to 5 MB. Chirpie does not publish video to Threads.

Can my agent answer replies on Threads?

Yes. Chirpie lists the replies under a post it published, and your agent can answer one, hide one, or delete its own reply. A first comment can also go out under the post the moment it publishes.

Which numbers does Chirpie report for a Threads post?

Views, likes, reposts, replies and quotes, in the same response shape as every other network, with views arriving as impressions.