UGCDocumentation

UGC Relay

Built-in rules engine for scheduled and event-driven wallet money movement-guide-level overview only

Updated August 28, 2026

Relay is UGC's built-in rules engine for automated wallet money movement - scheduled transfers, crypto DCA/swaps, bank withdrawals, savings sweeps, and advertiser checkout subscriptions.

This page stays high level. Undocumented URLs and private implementation details are not a supported integration surface - use the public APIs and in-product configuration described in this portal.

What Relay is for

  • Scheduled transfers - move funds between wallets or to another user on a cron schedule or a one-off run
  • Crypto DCA / swap - recurring dollar-cost-average buys or currency swaps
  • Bank withdrawals & savings - sweep a fixed amount, a percentage, or the full available balance to a linked bank account or savings wallet
  • Event-driven rules - trigger on a wallet event (e.g. wallet.credited:NGN:>=10000) instead of a schedule
  • Advertiser checkout subscription - recurring campaign-funding debits

How rules work

Every Relay rule created via API or MCP is a DRAFT requiring explicit user approval in the UGC app before it executes. A rule specifies an actionType (INTERNAL_TRANSFER, TRANSFER_TO_USER, CRYPTO_DCA, CRYPTO_SWAP, BANK_WITHDRAWAL, SAVINGS, or ADVERTISER_CHECKOUT_SUBSCRIPTION), a scheduleType (CRON, ONCE, or EVENT), an amount rule (FIXED, PERCENTAGE, or ALL_AVAILABLE), and optional safety guards (minBalanceGuard, maxAmountCap).

Dashboard configuration

Review and approve Relay rules in your UGC dashboard (exact menu labels may evolve). The docs site does not host screenshots; follow in-product guidance.

Relay and MCP

The relay_list_rules, relay_create_rule, and relay_pause_rule MCP tools wrap the same rules engine for LLM clients - see . Rules created via MCP are still drafts pending user approval; agents must instruct the user to confirm in the UGC app.

  • - Zapier / Make / n8n integrations

Did this solve your problem?