X (Twitter) posting: included under fair use

Posting to X is included in every paid plan under fair use: 30 posts a month on Pro, 100 on Ultra, 300 on Ultra+, per workspace. Posts with a link, and posts past the allowance, use credits, and credits are cheap: €4.99 buys 140, which is 140 posts or 14 posts with a link, paid once, with no subscription. X posting starts with your first paid month, not during the trial. X connects like every other platform: any account with an active plan or trial can add it on the Accounts page.

What is included

The allowance belongs to the workspace, not to each member: everyone posting to X in it shares the same count. A month is a calendar month in UTC, and the count starts again on the 1st. The allowance starts with your first paid month; during the trial, X posts do not go out.

How posts are counted

A plain post (no link in its text) counts 1 against the month's allowance, per X account it goes to:

• A post going to one X account counts 1.
• The same post going to three X accounts counts 3.
• A post going to X plus Instagram plus LinkedIn counts 1. Only the X part is counted.

Only posts that publish are counted. A post X refuses gives its count back.

Posts with a link

A post with a link is not part of fair use. It uses 10 credits for each X account it goes to, from credits you add in Settings. Ultra+ includes 30 credits a month for posts with a link, from the first paid month; they are gone at the end of each billing period.

What counts as a link

Any web address in the text of the post: https://…, www.…, and bare ones like example.com, the same addresses X turns into links. Photos, videos, @mentions and #hashtags do not count.

What credits cost

Credits are cheap: €4.99 buys 140 credits, which is 140 posts without a link or 14 posts with a link. It is one payment, plus VAT where it applies, with no subscription and nothing to cancel. Credits last 90 days. Add them in Dashboard → Settings, in the X (Twitter) panel.

Where to see usage

Dashboard → Settings shows the X fair-use meter: how many plain posts of this month's allowance are used, what is left and the date it resets, next to the credits you hold. If you use Schedchie through an AI assistant, the same numbers come back from get_x_usage: see connect an AI assistant.

At the limit

When the month's allowance is used up, a plain X post uses 1 credit if you hold any. Otherwise it does not go out on X: the post stays saved and is marked failed for X with the reason on it, and every other platform on the same post goes out normally.

• From the 1st, plain X posts go out again on the new month's allowance.
• To send a post that was held, retry it from the post after the reset.
• Scheduling still works at the limit; Schedchie tells you when X posts in a batch will not go out.

Credits you already hold

Credits you already hold stay valid until their expiry date. They pay for posts with a link, and for plain posts once the month's allowance is used up.

Your own X app (Ultra+)

On Ultra+ you can post to X through an X developer app of your own instead of Schedchie's. Posts through it are not counted against the fair-use allowance and use no credits, with or without a link. X bills them to your own developer account.

We strongly recommend turning auto top-up off in the X developer console, so a busy week never costs more than you decided. The save form asks you to confirm that auto top-up is off; Schedchie cannot see your billing settings at X.

Setting it up

• In the X developer console, create an app on Pay Per Use.
• Turn on OAuth 2.0 with the app permissions, type of app and callback URL the card in Settings shows.
• In Settings, X (Twitter), Use my own X app, paste the app's OAuth 2.0 client ID and client secret, confirm that auto top-up is off and save.
• On the Accounts page, choose Use my X app on each X account that should post through it.

How the keys are kept

The client ID and the client secret are both encrypted at rest with the key that protects the platform tokens of every connected account, and that key is held only on our server. Neither is ever shown again: the card shows a fingerprint (the first 4 and last 4 characters of the secret's SHA-256 hash) and the date you saved it. Saving again replaces the stored keys whole; the old ones cannot be viewed or edited.

Removing the app deletes the keys at once and asks X to revoke the tokens it issued. Disconnecting the last X account that uses it does the same.

Your X Developer Agreement makes you responsible for your own keys, and X may limit or suspend an app whose keys are used by a third-party service. Schedchie keeps them sealed and never shows them again.

What X supports once it is connected (text, images, video, reply settings, the 280-character limit) is on the X platform page and in the platform limits reference.