NU Signal Partners
See proven video IP, verify the rights, and distribute it safely by API.
Preview curated NewUnivers titles, explore the catalog, request licenses, launch protected personalized playback, collect events, and reconcile settlements in one partner workflow.
Product consultation, Sandbox integration, and Production activation all begin with the same application.
Sword God
Monster Princess
Midnight Chase
Spring Days settlement example
Sungkyunkwan rights example
Sword God
Monster Princess
Midnight Chase
Spring Days settlement example
Sungkyunkwan rights exampleWho is it for?
You can get started if any of these describe your business.
Source verified short-form IP for programming through an API. Fill your lineup quickly without avoidable rights risk, receiving only titles cleared for the relevant territory and term.
Connect catalog discovery, protected playback, event tracking, and settlement once. Open a personalized hosted webview for each viewer instead of building a player or exposing source files.
License video data lawfully, with training, generation, and resale permissions stated title by title.
Redistribute safely by territory using a catalog with normalized regional and language rights.
What can you license?
Start with the content and rights you receive, not the platform.
Only licensable titles are exposed. Internal pricing, revenue shares, and original prompts remain private.
Review the content and its rights together
Partners need scenes, episode context, and rights status—not an abstract pitch. Reviewed previews and thumbnails help determine where and how each title can be played and reconciled.
A reviewed vertical preview shows the scene in a format close to the real mobile viewing experience.
Title, genre, and episode context for Sword God, Monster Princess Secret, and EP009 Confession help reviewers understand each asset quickly.
Country, language, term, exclusivity, resale, download, and editing permissions are structured as title-level fields.
Short-lived signed HLS or DASH URLs replace source-file URLs, and playback events feed the settlement ledger.
Short-form video is separated into rights units
Review source video, thumbnails, subtitles, dubbing, and data-use rights independently before contracting. Operators use risk flags and required documents to control catalog visibility.
How does it work?
Discover → play → settle. See how each stage works and what it delivers.
Explore a rights-verified catalog by API
Review title artwork, genres, episode count, average runtime, and preview availability. Only unexpired packages with clear or restricted rights are returned, narrowing the programming shortlist from the start.
Apply viewer preferences in a personalized webview
Send non-PII preferences such as language, genre, subtitle, audio, autoplay, and maturity rating to receive a hosted playback webview URL. The viewer opens one link while NU applies those settings. Access requires an ACTIVE deal, an allowed country and origin, and a short-lived signed token; source URLs stay hidden. Signed HLS or DASH is also available for partners using their own player.
Events become settlement evidence
Playback starts, completions, purchases, and refunds are collected and matched to revenue reports. Instead of keeping only monthly totals, the ledger preserves title, episode, country, and revenue-type line items so any dispute can identify the exact item.
Why NU Signal Partners
Explore titles with clear or disclosed restricted rights. Territory, language, term, resale, and AI permissions are available by API.
Source files remain hidden. Playback uses signed tokens validated against the contract, territory, and allowed origin.
Send non-PII preferences for language, subtitles, audio, and autoplay to receive a hosted webview reflecting the viewer's choices. You do not manage a manifest or player.
Playback and payment events support settlement. Item-level ledgers make MG and revenue-share calculations transparent.
REST API, OpenAPI, Postman, and Sandbox. Issue a key through self-service and validate the full flow without real charges.
Commercial models
Terms depend on the title, territory, and scale and are agreed with business development. Sandbox validation is free.
A minimum guaranteed amount is paid in advance for a title or package.
Playback and purchase revenue is divided among NU, the partner, and rights holders at the agreed rates.
Depending on the use, a flat title license or monthly API fee may also apply.
How to launch
Five steps from application to Production. The status page, read-only portal, and API use the same source of truth.
Apply with the form below or POST /v1/partner-applications.
Use the one-time application reference and status token to check the result securely.
After approval, claim a one-time approval token on the status page and issue the first Sandbox API key.
Validate catalog discovery, playback tokens, and event delivery with the Catalog, Playback, and Event APIs.
When the license deal becomes ACTIVE, upgrade to a Production key and review or dispute settlements.
Frequently asked questions
Exclusive and non-exclusive terms can both be discussed by title and territory. Include your target territories and genres in the application.
You can begin with a small pilot. Validate the integration in Sandbox first, then scale it.
Monthly item-level ledgers are built from playback and payment events, with a dispute process for individual entries.
Training, generation, and resale permissions are stated per title, so a license covers only approved uses.
Yes. Test the catalog, protected playback, and event collection without real charges. Real financial statements are available only with Production keys.
Yes. Send non-PII preferences such as language, genre, default subtitles or audio, autoplay, and maturity rating to receive a personalized hosted webview. Raw PII such as email cannot be sent; preferences are retained with the session for analytics.
Rights are normalized by territory, so only titles licensable in the requested region are exposed and played.
Partner application
Store the application reference and status token shown after submission. You can check approval and claim the first key yourself.
