Five products. One site console. One bill per account.
NX Stories, NX Translations, NX Summary, NX Quiz / Poll, and NX SEO. Enable any of them on a site, invite teammates to only the sites they should see, and let usage accumulate on that site’s billing account.
- Free tier with included calls
- No credit card required
- Cancel anytime
- Self‑serve API keys
Trusted by product teams shipping with AI
Five publishing products. Enabled per site.
Stories, translations, summaries, quizzes, and SEO. Turn on only what a site needs. AI requests are handled by NX Suite, then counted on that site’s billing account.
A site for each property. Products on that site.
Each site has its own domain, API key, and product entitlements. Invite someone to two of your three sites and they only see those two. The billing account is chosen per site.
- As many sites as you need
- One billing account per site, many sites per account
- Invites per site: owner, admin, editor, viewer
One curl away from production.
Authenticate with an x-api-key header plus the request Origin. Every call is metered against the project's subscription and counts against included calls first.
curl -X POST https://saas.nxsuite.io/api/v2/service/nx-stories \
-H "Content-Type: application/json" \
-H "x-api-key: nxk_live_••••••••••••" \
-H "Origin: https://yoursite.com" \
-d '{ "postId": 1234, "template": "feature-launch" }'Everything you'd build anyway — already built.
Auth, projects, keys, domains, usage, plans, billing accounts. Focus on what makes your product different, not on plumbing.
Sites, teams, and billing accounts
Create as many sites as you need. Invite people per site, and assign one billing account to each site.
Scoped API keys
Mint, rotate and revoke API keys per project. Origin allow‑lists block leaked keys from third parties.
Domain verification
Prove ownership via DNS TXT, HTML file or manual admin approval before any traffic is accepted.
Per‑product usage
Each product has tiers of 200, 500, and 1,000 included uses. Extra uses bill at that product’s own rate and roll up on the site’s billing account.
Hardened security
bcrypt password hashing, hashed API keys, role‑based access for projects and billing accounts.
AI stays in NX Suite
Stories call Claude and the other products call Gemini from this API. The WordPress plugin only sends the work and reads entitlements.
Teams ship faster on NXSUITE.
“We replaced three vendor dashboards with NXSUITE. Projects, billing and usage tracking finally live in one place.”
“Spinning up a new product project with its own API key and Gemini quota now takes us less than a minute.”
“The included‑calls + pay‑per‑extra model is exactly how we want to charge our own customers downstream.”
Each product has its own tier. Usage adds up on the billing account.
Tiers are 200, 500, or 1,000 included uses. Summary and SEO are $0.25 per extra use, Quiz / Poll $0.40, Translations $0.65, and Stories $0.90. A site points at one billing account, and that account’s total is the sum of its sites.
Common questions
How does licensing work?+
Each product is priced on its own: a prepaid tier of 200, 500, or 1,000 uses, then a per-use charge after that. Those charges add up on the billing account assigned to the site.
Can I use NXSUITE on multiple sites?+
Yes. Each site is a project with its own domain, API keys and module subscriptions. One billing account can pay for many sites, and you can invite teammates per project.
How are API keys secured?+
API keys are hashed at rest. We only ever store a short prefix for display. Each plugin validates against the site’s allowed origin, and keys can be revoked instantly from the dashboard.
Which WordPress versions are supported?+
NXSUITE modules target the latest WordPress release plus the previous major version, with Multisite supported across NX Translation and the rest of the suite where it makes sense.
Build your next AI feature this afternoon.
Sign up, create a project, drop an API key in your app. The first calls are on us.