NEW Rippy, your AI media buyer, is live. Give it a budget and wake up everywhere. See it run →
For merchants

Live by Friday. Keep every guardrail.

Set the campaign once. Browse or let Rippy find, negotiate, book, launch, track, report, and recommend rebooks under your exact rules.

STEP 01
Create the campaign

Save the objective, destination, audience, category, budget, schedule, and safety rules as one versioned draft.

STEP 02
Find eligible inventory

Browse directly or save Auto-Buyer guardrails. Category, pause, block, trust, and inventory gates run before ranking.

STEP 03
Confirm and fund

Review the exact server quote and fund from $50. A purchase cannot outrun available wallet capacity.

STEP 04
Approve the content

Every draft lands in your approval queue before it posts. Approve it, request changes, or dispute it. Nothing goes live without you.

STEP 05
Record delivery evidence

Ripal preserves the server-timed post record and requires provider evidence where an official adapter is enabled. Unavailable metrics remain unavailable.

STEP 06
Release or resolve

Eligible completion enters the payout path. Late delivery, refunds, and disputes preserve their exact evidence and money boundaries.

The Auto-Buyer

Your rules. Its clock.

Give Rippy a budget, category, platform, and price limits. It works the marketplace under those rules, while wallet limits, exclusions, and delivery evidence stay enforced.

YOUR BUDGET · YOUR RULES · NO AGENCY IN THE MIDDLE
Auto-Buyer capability status
MandateBuilt
Merchant-owned category, topic, platform, engagement, and spend rules
SelectionBuilt
Private quality bands applied only after every hard eligibility gate
FundingBuilt
Wallet capacity, immutable economics, and replay-safe purchase boundaries
ExecutionRelease-gated
Ready brief and requested-date policy required before autonomous buying
AUTONOMOUS EXECUTION RELEASE-GATED
Escrow, in plain terms
Available
Provider-confirmed wallet value that has not been reserved.
Reserved
Exact deal value isolated for a funded child deal.
Released or returned
Provider-confirmed payout, refund, or reusable wallet capacity.

The wallet never fabricates a balance or silently reuses reserved value. Late delivery makes a merchant claim available; settlement still follows the recorded deal rules and evidence.

Verification, in plain terms
Paid actions share one identity gate

Funding, purchases, offer decisions, and payout claims use the same server-owned risk and assurance boundary.

Connected stats remain provider-sourced

Ripal displays provider evidence when available and shows a neutral absence when it is not.

Sensitive actions require step-up

Assurance is checked again at the money and decision boundaries instead of trusted from screen state.

The refund-on-late rule

If a post misses its confirmed slot, the server marks it late without a grace period and makes a merchant refund claim available. The claim preserves the requested amount, deal evidence, and settlement state rather than promising an automatic outcome.

Frozen deal economics

Each funded child deal preserves its price, fees, refundability, and wallet origin.

Reports without guessed reach

Funded value, lifecycle, source, and timing are real; unsupported social metrics stay unavailable.

Guardrails you control

Save, pause, or tighten the Auto-Buyer mandate. Execution stays off until every release requirement is met.

Start with a campaign

Move from draft to a controlled purchase.

Prepare a campaign, browse current inventory, and review exact checkout economics. Listings can start at $10; autonomous execution activates only after its release safeguards pass.