1. API
  2. Docs
  3. Power your own app builder

Power your own app builder

Omi can build anything, under your name. Your customers type an idea into your product; Omi builds the full-stack app; it goes live on their domain with your brand and none of ours.

BrandingApps created or published with an API key never show a BuildItOmi badge or footer, on any plan.
DomainsConnect each app to your customer's domain with HTTPS: 3 on Starter, 10 on Pro, 100 on Scale.
OwnershipEvery app's code downloads as a ZIP. Its data is readable and writable through the API.
Your priceYou pay our credits; you set your own price. Each reply and GET /v1/usage show what each app cost you.
  1. Install the SDK

    Create a key at API keys with apps:write, domains:write and usage:read. Keep it on your server: your customers never see it.

    # JavaScript (Node 18+, Bun, Deno)
    npm install builditomi
    
    # Python 3.8+ (no dependencies)
    pip install builditomi
    
    export BUILDITOMI_KEY="bio_..."
  2. Build for a customer

    Your backend creates the app and saves its id next to your customer. Forward the streamed events to your own UI so they watch it being built, in your design.

    # Your customer typed a prompt in YOUR product. Your server asks Omi:
    ID=$(curl -s -X POST "$API/apps" -H "Authorization: Bearer $BUILDITOMI_KEY" \
      -H "Content-Type: application/json" \
      -d '{"prompt":"An order form for a bakery with pickup times"}' | jq -r .id)
    
    # Stream progress to your customer's screen until the event is "done"
    curl -N -X POST "$API/apps/$ID/stream" -H "Authorization: Bearer $BUILDITOMI_KEY"
  3. Launch on their domain

    Publish, then connect the customer's domain. Show them the DNS records the status returns; HTTPS is issued for you, usually within the hour. Until then the app works at its own link.

    curl -s -X POST "$API/apps/$ID/publish" -H "Authorization: Bearer $BUILDITOMI_KEY"
    
    # Their own domain (key needs the domains:write scope)
    curl -s -X POST "$API/apps/$ID/domain" -H "Authorization: Bearer $BUILDITOMI_KEY" \
      -H "Content-Type: application/json" -d '{"domain":"order.riyasbakery.com"}'
    # Show your customer the DNS records from .status.records, then poll GET /apps/$ID/domain
  4. Change it, and know what it cost

    Customers ask for changes in plain words; you pass them to /edit. GET /v1/usage returns your spend per day split into API calls, AI work and build time, and GET /v1/usage/keys per key. Give a big customer its own key to see its cost on its own.

    curl -s -X POST "$API/apps/$ID/edit" -H "Authorization: Bearer $BUILDITOMI_KEY" \
      -H "Content-Type: application/json" -d '{"message":"Add a cake size picker"}'
    # then stream or step until done, and publish again
  5. Hear about builds without polling

    On Pro and Scale, a signed webhook tells your server when a build finishes or fails and when an app is published. Verify it with verifyWebhook (JavaScript) or verify_webhook (Python).

What it costs you

Each API call is 1,000 credits. A build also uses the credits its AI work really costs plus its server time, shown in each reply. Plans start at $9 a month; most app builders start on Pro ($29) for webhooks and 10 domains. See pricing.