Scoped account connection
The implementation requests only identity, post, media, and offline access needed for the named workflows.
Official X API integration
X workflows designed to make cost and consent explicit.
The Novas X connector is implemented around the official X API, but production calls are intentionally blocked while the product remains in zero-spend mode. No paid request is made silently.
What the connection is for
A narrow purpose for every provider permission.
Cost-aware publishing
Supported text and media workflows remain behind a versioned cost model and an explicit spending decision.
Measured provider usage
Post and account reads are designed to remain bounded, throttled, and visible when paid access is enabled.
Permissions and formats
Only what the product needs. Nothing hidden in the background.
tweet.read
tweet.write
users.read
media.write
offline.access
Supported product formats
Text-only publishingSingle image or GIFCarouselShort-form video
Safeguards that stay visible
- Live API calls are blocked while zero-spend mode is active.
- Enabling requires an accepted pricing model, funded credits, and an explicit spending limit.
- Paid operations are not inferred from a configured environment variable.
- Manual and assisted workflows remain available while the connector is paused.
No invisible billing surface
The connector is not considered configured or connected merely because implementation code exists. The owner must separately approve the current cost model and operating controls.
Provider success still required
When enabled, Novas will retain official post IDs, publication status, and timestamped metrics. A local queue or attempted request will never be presented as a successful external action.
Your content stays yours.
Create a verified account, then connect only the profiles you own and choose to manage with Novas.