build-monetized-app

Builds, deploys, and monetizes apps on Eliza Cloud using the cloud SDK.

19.2k|5.7k|Updated Jul 9, 2024
One-click install
npx skills add https://github.com/elizaOS/eliza --skill build-monetized-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-monetized-app
Source: https://github.com/elizaOS/eliza/tree/main/packages/skills/skills/build-monetized-app
Command: npx skills add https://github.com/elizaOS/eliza --skill build-monetized-app

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @elizaos/cloud-sdk, and includes references (resource) components.

What problem does it solve?

Building an app that earns money on Eliza Cloud requires coordinating app registration, container deployment, markup configuration, OAuth-based user auth, payment requests, and payout redemptions across many APIs. This Skill provides the exact 6-step flow with code so an agent can ship a revenue-generating app without inventing any of the plumbing.

Core Features & Use Cases

  • End-to-end build flow: Register an app with createApp, deploy the prebuilt first-party container image, configure monetization markup, and patch the deployed URL and allowed origins.
  • Monetization and payments: Configure inference markup percentages, create app charge requests via Stripe/OxaPay, issue x402 crypto payment requests, and redeem creator payouts in elizaOS tokens.
  • Survival economics: Explains how app earnings auto-fund the agent's own container hosting through the earnings-first billing cron, keeping a profitable agent online indefinitely.
  • Failure recovery: A reference table covers name collisions, deploy gating (503/403), insufficient balance, and auth flow failures with concrete recovery steps.
  • Use Case: An autonomous agent registers a chat app, deploys it to a *.apps.eliza.app subdomain with a 100% inference markup, and the resulting earnings cover its own ~$0.67/day hosting cost.

Quick Start

Use the build-monetized-app skill to register and deploy a new monetized chat app on Eliza Cloud with a 100% inference markup.

Frequently Asked Questions about build-monetized-app

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a monetized app on Eliza Cloud?

Follow the 6-step SDK flow: register the app with createApp and skipGitHubRepo, deploy the prebuilt first-party image with deployApp, set the inference markup via updateMonetization, patch app_url and allowed_origins, then report the live URL. Each step is idempotent so you can restart from any failed step.

How does an Eliza Cloud app earn money from inference?

Every user request forwarded to /api/v1/messages with an x-app-id header debits the user's org credit balance and records the configured markup as creator earnings. Those earnings accumulate in the redeemable_earnings_ledger and can fund hosting or be cashed out.

Can I deploy my own container image to Eliza Cloud apps?

No, app deploys are restricted to a prebuilt allowlist of first-party ghcr.io/elizaos/* images, and build-from-repo is disabled. Template apps created with skipGitHubRepo get the default template image stamped automatically.

Why does deployApp return 503 apps_deploy_disabled?

The deploy endpoint is gated behind APPS_DEPLOY_ENABLED=1 on the Worker and a production org allowlist. If you hit the 503 or a 403, the apps-deploy backend is not armed for your environment, so report it to the human rather than working around it.

How do app earnings keep an agent's container running?

The daily container-billing cron pulls from the redeemable_earnings_ledger before touching purchased credits when pay_as_you_go_from_earnings is enabled. If app earnings exceed the roughly $0.67/day hosting cost, the container stays online indefinitely without credit top-ups.

What payment methods does Eliza Cloud support for app charges?

App charge requests support Stripe and OxaPay checkout, while x402 payment requests settle in crypto on Base, Ethereum, BSC, and Solana. Creator payouts are redeemed in elizaOS tokens via the /api/v1/redemptions endpoint after admin review.