JubJub
Sub-pillar 02The jobs AI handles

The actual jobs AI handles for you on JubJub.

There is a lot of noise about AI doing things for creators. Most of it is vague. This page is not. If JubJub is connected to your assistant, here is exactly what it can do right now.

No hype · Just the list · Everything here runs today.

There is a lot of noise about AI doing things for creators. Most of it is vague.

This page is not. If you have JubJub connected to your AI assistant via MCP, here is exactly what it can do — broken down by the real jobs, with the actual tasks under each.

01Publishing

Publishing.

Your AI can take a piece of content and publish it across platforms in a single instruction. You tell it what to publish, where, and when. It handles the platform settings, the scheduling, and the submission.

Jobs it can run

  • Publish a video to one or multiple platforms
  • Schedule a publish for a specific time
  • Set titles, descriptions, and visibility per platform
  • Retry a failed launch

You need JubJub connected first: how to connect your AI.

02Analytics and performance

Analytics and performance.

Your AI can pull your content’s performance data and give you a plain-language summary. No dashboards. No logging in. You ask, it answers.

Jobs it can run

  • Summarise how a video is performing across platforms
  • Compare performance between two pieces of content
  • Flag which content is earning the most revenue
  • Pull a weekly or monthly summary on request

How ownership records connect to performance data: ownership.

No dashboards. No logging in. You ask, it answers.
Pull quote · 01
03Splits and collaborators

Splits and collaborator management.

Your AI can handle the operational side of working with other people — inviting collaborators, confirming splits are set correctly, checking revenue allocation before a publish goes out.

Jobs it can run

  • Invite a collaborator to a workspace
  • Check the current revenue split on a piece of content
  • Confirm splits are correct before publishing

How collaborator ownership allocation works: /ownership/collaborator-ownership. How split payments route automatically: /monetisation/splits.

04Ownership and registration

Ownership and registration.

When content is published through JubJub, ownership is registered on-chain automatically. Your AI can verify that happened and pull the ownership record for any piece of content in your catalogue.

Jobs it can run

  • Confirm a publish triggered an ownership record
  • Check who holds ownership tokens on a piece of content
  • Pull the provenance record for a file

How on-chain ownership works: ownership.

05Agent payments

Agent payments.

When autonomous agents interact with your content, JubJub handles the payment infrastructure. Your AI can check on those flows without you having to dig into dashboards or transaction logs.

Jobs it can run

  • Check agent payment activity on your catalogue
  • Verify that payment rails are active
  • Review earnings from agent consumption of your content

How agent-as-customer works: agents. MCP setup: connect your AI.

06What it cannot do

What it cannot do.

The AI handles the operational layer. It does not make creative decisions, write your scripts, or tell you what content to make. That part stays with you.

The line

The AI is your operator, not your creative director. It runs the logistics so you keep the part only you can do.

Hand off the operational layer.

Connect an assistant and let it run the jobs above on your word. You keep the creative work. It keeps the logistics moving.

Connect your AI

Free for human users. You scope exactly what it can touch.

FAQThe jobs, answered plainly

Questions, answered plainly.

Do I have to give the AI permission before it can do these things?

Yes. The AI only acts within the permissions you grant when you connect JubJub via MCP. You can scope access to specific tools, specific workspaces, or require approval before any action executes.

Can the AI publish without me confirming?

That depends on how you configure it. You can require your sign-off before any publish goes out, or let the AI execute autonomously. Both modes are supported.

What happens if the AI makes a mistake on a publish?

Launches can be cancelled before they go live. Ownership records are immutable once registered — the publish record cannot be altered after the fact, which is the point.

Is this different from scheduling tools?

Scheduling tools queue posts. JubJub’s AI integration can orchestrate the full workflow — ownership, splits, publishing, and payment — in a single instruction. It is a different layer of the stack, not a replacement for a single point tool. See why the current creator tech stack is broken: the creator tech stack.