Display, rewarded, video, subscriptions — one MCP. Every product is a tool call plus a few lines of markup; your agent sets them up and manages them with no ad-ops team.
What it is: in-content ad units plus the sitewide sticky anchor. A unit is one generic element — Rocket Sloth’s demand stack (header bidding, server-side bidding, and the Google ad exchange) decides which format fills it per auction, so your agent never picks an ad type per placement.
Setup: your agent drops a <div data-rs-ad> anywhere on the page. A bare unit fills its container; data-rs-width/data-rs-height constrain it to an exact size (e.g. 300×250). Units fill lazily as they scroll into view and collapse cleanly if nothing fills them — never a gap. The sticky anchor’s on/off switch and top/bottom/both position are one ad_settings call.
<!-- bare unit: fills its container --> <div data-rs-ad></div> <!-- size-constrained unit: 300x250 --> <div data-rs-ad data-rs-width="300" data-rs-height="250"></div>
What it is: readers watch an ad to unlock content, features, or credits — paywall-style value exchange without a payment flow.
Setup: the trigger is one line of markup. When the reader completes the ad, one of two things happens: with data-rs-reward-url the reader is sent to that URL once the reward is earned; without it an rs:rewarded event fires on the element with {status, reward} so your own script grants the reward.
<button data-rs-rewarded data-rs-reward-url="/unlock">Watch an ad to continue</button>
document.addEventListener("rs:rewarded", function (e) {
if (e.detail.reward) {
// grant the reward: unlock content, credit the account, etc.
}
});
What it is: a content player plus video ad formats riding the same demand stack as your display units — no video infrastructure for your agent to run.
Setup: the video tool handles everything: activate turns video on for your site, status reports its state, and embed returns the unit markup. Place the unit where the player should appear with an 11-character video id from your library as data-rs-video-id; the same Rocket Sloth script tag that powers your ad units turns it into a content player — no extra script. While your application is under review the unit renders a labeled placeholder; on approval the same unit plays the content player, unchanged.
<div data-rs-video data-rs-video-id="XXXXXXXXXXX"></div>
Sitewide video ad formats — the floating outstream player and the universal video player — are separate master switches on the video tool. Once enabled they serve automatically; no per-page markup is needed.
What it is: reader subscriptions, memberships, and donations — recurring revenue beyond ads, from the same MCP interface.
Setup: your agent configures and manages plans over MCP with the subscriptions tool. Call it to see the available resources and actions for your site.
Put display, rewarded, video, and subscriptions in from your first commit. Sign up on the web or connect your agent over MCP — same application either way.