Ask her anything
Every question about your fans, answered from evidence.
She answers from the live lake — fan counts, campaign performance, top cities, who's heating up — with the real numbers, never a guess. And when the answer is an action, she takes it: drafts the campaign, pulls the report, files the work.
How did the fall tour actually do?
21 shows, 4,203 captures, 803 page views to 141 new fans this week alone. Night 4 in Vegas outperformed everything — your Vegas fans are your hottest segment right now. Want the per-city breakdown?
Text the Vegas list about the presale.
drafted, segmented by city, awaiting your send — you're always in command
✦
Sara · Copilot
floating panel✦
Copilot on every admin surface
one key away, everywhere you work
◈
Sees the live platform snapshot
stats, campaigns, fans — as context, never stored
⌘
Scoped to your role
an agency sees only its own roster
↗
Acts, not just answers
draft campaigns, pull reports, file work
The ✦ Copilot
One key away, everywhere you work.
A floating copilot lives on every admin surface. It sees the live platform snapshot as context — never stored, never shared — and it's scoped to your role: an agency sees only its own roster, a talent only their own lake.
The operator API
Drive the platform from your own tools.
The same intelligence Sara rides is yours through the operator API — stats, geo, campaigns, fans, sends, talent discovery, and draft creation, with scoped ndop_ keys. Plus a native MCP server, so your own agents can operate NuData directly.
operator API · ndop_ keys
$nudata operator stats
→{ "fans": 4203, "events_24h": 141, "campaigns": 12 }
$nudata operator campaigns --talent "Elijah Scott"
→fall-tour-2026 · 803 views · 141 captures · 2 live pages
$nudata operator campaigns create --draft "Vegas presale"
→draft created — camp-9f2 · review in the console
The benefit
Why Sara OS changes the job.
The platform builds itself
Campaign pages painted and written in ~60 seconds, on-brand by construction — a designer and a copywriter on retainer, in the loop.
Answers, not dashboards
Ask in plain language; get the real number with the evidence behind it. The console is for acting, not hunting.
She works while you sleep
The loop keeps moving — captures enriched, sends drafted, reports filed. You wake up to receipts.
You stay in command
Outward actions wait for your send. She drafts, you decide — always.
Every capability
What she does.
Build
✦AI campaign pages in ~60 seconds
✦On-brand by construction — kit + assets
✦Copy, visuals, and layout together
✦Tour date import from any poster or list
Answer
✦Live lake stats and geo
✦Campaign performance on demand
✦Fan lookups by name or city
✦Plain-language, evidence-grounded
Operate
✦Draft campaigns from a sentence
✦The ✦ copilot on every admin page
✦Operator API with scoped ndop_ keys
✦MCP server for your own agents
Discipline
✦Scoped to your role, always
✦Live snapshot as context — never stored
✦Outward actions confirmed by you
✦Every action receipted