Not connectable yet
Stack Exchange is not connectable in FounderReply yet — it is marked coming-soon, so the dashboard hides the connect button and the authorisation endpoint refuses. When it opens, the only actions are answering a question and commenting on a post, both gated by the same reputation rules as the website.
You cannot connect Stack Exchange to FounderReply today. The Stack Exchange side is unusually easy — an app key is issued instantly and the write scope needs no approval — but the platform is still flagged coming-soon in the registry, so the connect path is closed until that flag flips. The connect button is disabled in the dashboard and the authorisation endpoint refuses the request, so nothing on this page is available to switch on yet — on any plan.
On Stack Exchange
Answers and comments on one site at a time. Reputation-gated, throttled, no DMs.
On Stack Exchange the useful move is a real answer to a real question. There is no post to publish, so publishing is switched off.
Asking a question is off-model for a brand account, so the connector has no publish action at all; the two write paths are adding an answer and adding a comment.
The API enforces the same reputation thresholds as the site. A new account cannot comment on strangers’ posts, whether a human or an agent is typing.
Writes are additionally throttled to roughly one a minute, and a throttle is surfaced as a failure with the backoff attached rather than retried.
Stack Exchange is a network of separate sites. The site you connect is stored with the account, and every call targets it.
The site parameter is fixed at connect time, so Stack Overflow, Server Fault and Super User are separate connections rather than one federated search.
The room
Stack Exchange questions are the highest-intent technical content on the web: someone described their exact problem, and thousands of people with the same problem found it afterwards. It is also the least forgiving surface here — the community has spent fifteen years removing promotional answers, and it is extremely good at it.
The rule is short: the answer has to work without your product. If the question can only be solved by buying something, say so and disclose the affiliation; if it can be solved another way, answer that way and mention your tool as an aside or not at all.
The ceiling
Two layers decide whether an action happens by itself: your autonomy dial, and a hard ceiling we impose per platform. The safer of the two always wins, so the dial can make things stricter and never looser. This table is generated from that ceiling.
| Action | Ships as | Most permissive allowed |
|---|---|---|
| Publish your own postOriginal content from your connected account | No API on Stack Exchange | No API on Stack Exchange |
| Reply on your own postsAnswering comments left on your content | Waits for your approval | Waits for your approval |
| Direct messagePrivate messages to a person | No API on Stack Exchange | No API on Stack Exchange |
| Comment on someone else’s postThe highest-risk action on every platform | Not permitted | Waits for your approval |
Stack Exchange punishes promotion hard and gates writes by reputation, so every action is human-gated — nothing on Stack Exchange may run unattended. Publishing has no analogue on the platform and direct messages do not exist in its API. These ceilings are already in the controller and apply the moment the platform opens.
Stack Exchange accepts a comma-separated scope list, and no_expiry means the token never expires — so there is no refresh flow at all.
Nothing here is a marketing paraphrase — it is the string the connect flow sends, copied from lib/connectors/stackexchange.ts.
write_access,no_expiry,read_inbox,private_infoFAQ
No. It is marked coming-soon in the platform registry, so the dashboard offers no connect button and the authorisation endpoint refuses the request. The connector is written; the platform is simply not enabled for connecting yet.
No. Asking a question on behalf of a brand is off-model, so the connector has no publish action. The two things it can write are an answer to someone’s question and a comment on a post, and both wait for your approval first.
Yes, in full. The API enforces the same thresholds as the website — roughly fifty reputation to comment on other people’s posts, and more on some sites — so a new account is as limited through the agent as it is through a browser.
One site per connection. The site is chosen when you connect and stored with the account, so Stack Overflow, Server Fault and Super User are separate connections. There is no cross-site search in the connector.
Stack Exchange is not connectable yet. Reddit, X, Bluesky, Lemmy and Discourse are — and the approval queue works the same way on all of them.