X integration#
This page describes the X (Twitter) foundation in the documentation source candidate. Availability in a released app has not been confirmed. OAuth completion and posting remain unverified; do not treat these pending workflows as available. See Pending integrations.
What is this for?#
Reading public trending topics, drafting posts to X's exact platform rules before you ever leave VOOL, and keeping a voice profile the operator explicitly approved.
Foundation described by this source#
| Capability | What it does | What it needs |
|---|---|---|
| Trending reads | Read-only fetch of X trending topics for a place. Off by default; fails closed with a structured result, never a raw error. | An X API bearer token stored in your credential store, and enabling the tool. |
| Editorial studio | Draft posts and threads, validated deterministically against X's published counting rules (weighted length, URL and emoji weighting). The engine — not the model — computes the validation verdict. | Nothing external; validation is local. Posting completion is not verified. |
| Voice profile | A store of how you write, used as style evidence for drafting. Samples enter only through an explicit operator act — never inferred from chat history. | Your explicit approval per sample. |
What permission or connection does it require?#
- Reads need your own X API credential, stored in the encrypted credential store under the
x.api.namespace for that account. VOOL never ships a token and never broadcasts credentials. - This source does not establish released posting support. The editorial studio produces copy-ready text you post yourself.
What can go wrong?#
- No credential saved — the read tool reports that no token is configured; nothing is sent. Store the token in Settings, then retry.
- Credential rejected / rate limited by X — the structured result says which; the wording never guesses between a local refusal and a provider answer. A rate limit tells you to retry later; it does not tell you to change your key.
- Validation unknown — where X publishes no official limit (for example, an Articles character cap), the engine says the constraint is unspecified rather than inventing a number. Treat that as "X has no published rule", not as an error.
What do I do next?#
For reads: check the credential, then retry. For drafting: read the engine's per-claim validation results in the draft envelope. For everything else, see the Error Book and Pending integrations.