X Settings

What Nadia does on X

Nadia publishes to X and reads nothing back. X bills every call to its API to the application that makes it, so to UseNadia, for every connected account: creating a post, and above all reading one (every post returned is paid for, on every read). Reading a timeline back to compute statistics would cost more than a channel earns. In practice:

• Publishing: a text, up to 4 images or one video, and threads (every extra part becomes a reply to the previous tweet).
• No X analytics: not in Analytics, not on a post’s card in the calendar, not through the public API or the MCP (the answer is empty).
• No X inbox, and nothing triggered by a post’s likes (automatic repost or reply): it would mean reading the post again.
• No mention autocomplete in the composer: type the full @handle.

Connecting

In Add Channel, click X: you are redirected to X and authorise UseNadia to post on your behalf. The account connected is the one open in your browser; to connect another one, switch accounts on X first.

A post’s length is counted the way X counts it (a link is worth 23 characters, an emoji 2): 280 characters, 4,000 for a verified (Premium) account.

Limits

10 posts with a link per month and per X account

X charges $0.20 for every post that contains a link, against $0.015 without one. Each connected X account can therefore publish at most 10 posts with a link per calendar month (UTC, from the 1st to the last day of the month the post goes out). Each tweet of a thread counts for itself: a three-tweet thread with a link in each tweet uses three. A link is any address X reads as one: https://…, but also a bare domain (usenadia.com, go.deviensdev.fr/x). Posts without a link are not limited.

Scheduled posts and posts already out are counted, including a post published then deleted in Nadia or the first tweet of a thread whose reply failed (X has already billed them), and each occurrence of a repeated post. A draft does not count. Beyond the limit, the composer refuses with a clear message, and the public API and the MCP answer 400 with the same message. The count is made again when the post goes out, whatever its path (moved in the calendar, a draft scheduled, a repetition): if it is then past the limit, the post goes to ERROR with that message, and nothing is sent to X.

Connecting your own X key (your own app on the X console, billed directly to you, with no cap on our side) is planned, with no date yet.

Settings schema

__type: "x", in posts[].settings of Create a post:

{
  "settings": {
    "__type": "x",
    "who_can_reply_post": "everyone",
    "community": "",
    "made_with_ai": false,
    "paid_partnership": false
  }
}

Fields

Field	Type	Required	Description
__type	string	Yes	Must be x
who_can_reply_post	string	Yes	Who can reply to the post, see below. In the composer: Who can reply to this post?
community	string	No	URL of an X community to post in, shaped like https://x.com/i/communities/1493446837214187523. The post is shown to your followers too
made_with_ai	boolean	No	Made-with-AI disclosure. In the composer: Made with AI
paid_partnership	boolean	No	Paid partnership disclosure. In the composer: Paid partnership

who_can_reply_post

Value	Description
everyone	Everyone
following	Accounts you follow
mentionedUsers	Accounts mentioned in the post
subscribers	Your paid subscribers
verified	Verified accounts

Full example

A two-tweet thread, the second one with a link (it uses one of the month’s 10 posts with a link):

{
  "type": "schedule",
  "date": "2026-11-03T10:00:00.000Z",
  "shortLink": false,
  "tags": [],
  "posts": [
    {
      "integration": {
        "id": "your-x-integration-id"
      },
      "value": [
        {
          "content": "What I learned posting one video a day for 100 days 🧵",
          "image": []
        },
        {
          "content": "The details, numbers included: https://usenadia.com/blog",
          "image": []
        }
      ],
      "settings": {
        "__type": "x",
        "who_can_reply_post": "everyone",
        "made_with_ai": false,
        "paid_partnership": false
      }
    }
  ]
}

Known errors

Message	What happens
X quota reached: 10 posts with a link per month and per account…	The limit above is reached for this account and this month: remove the link, or schedule the post for next month
X refused the post: UseNadia's X quota is reached, try again later.	X blocked the post because UseNadia’s API budget is spent. The post ends in error, with no automatic retry: post it again later
X rate limit reached: too many requests in a short time, try again in a few minutes.	Too many posts too close together: X limits the pace per account. Nadia tries three more times, then the post ends in error
X authentication has expired, please reconnect your account	Reconnect the X account from your channel list
You are not allowed to create a post with duplicate content	X refuses a text identical to a recent post of the same account

A post in error carries the message on its calendar card (red badge) and in the failure notification.