PostLake
Queue a post now, publish it later, on any network, through one call. Every page below carries that network's real limits, because a scheduler that accepts a post it cannot publish is worse than no scheduler.
Straight from the same registry the publish path validates against, so nothing here can disagree with what the API does.
| Network | Caption limit | Posts a day | Media rule | Publishing |
|---|---|---|---|---|
| TikTok | 2200 / 4000 | 25 | media required | confirms later |
| 2200 | 100 | media required | immediate | |
| X | 280 | no set cap | text is fine | immediate |
| 3000 | no set cap | text is fine | immediate | |
| 63206 | 25 | text is fine | immediate | |
| Threads | 500 | 250 | text is fine | immediate |
| Bluesky | 300 | no set cap | text is fine | immediate |
| YouTube | 5000 | 100 | video required | immediate |
| 500 | no set cap | media required | immediate |
The reason this works as one integration rather than 9 is that every network answers in the same normalised shape. Your code does not branch per platform, and an agent does not need a mental model of each one. Where a network genuinely differs, the difference is declared in GET /v1/platforms rather than discovered from a rejection.
Pages listed here cover only the networks that genuinely support this. Where a network does not, it is absent rather than represented by a page explaining that it cannot.