Console
Overview
Month is the calendar month in UTC. Balances move only by ledger entries.
Add credit
Checkout is hosted by Stripe. The card is saved with Stripe for automatic top-ups.
Between $10 and $10,000.
Auto top-up
When the balance falls below the threshold, the saved card is charged the top-up amount. It needs a card saved by a completed checkout.
Spend alerts
RecommendedAn alert fires once per calendar month (UTC) when this month's usage crosses each amount. Alerts never stop a session. With no amounts set, they default to 50%, 80% and 100% of the spend limit, if there is one.
Monthly spend limit
Available, not recommendedA limit is a hard stop, and it ends streams already in progress, not just new ones. Once this month's usage reaches it, new sessions are refused, every live stream and call ends within 15 minutes as its token fails to renew, and auto top-up stops until the month turns over or the limit is raised. Topping up does not lift it. To watch spend without risking an outage, use spend alerts instead.
Ledger
Newest first.
| When | Kind | Amount | Reference |
|---|
Usage, last 30 days
Usage charges per UTC day, from the ledger. Hover a bar for the exact amount.
Savings against Agora
Every metered minute in the period, from the ledger: what MOQOM charged, and what Agora's list price would charge for the same participant-minutes at the same tier and role.
| Tier | Role | Relays | Minutes | Egress | MOQOM | Agora list | Saved |
|---|
What if
EstimateA month of usage you describe, priced by the API with the rate card in force. The bitrate per tile is an assumption you can change; the bill is metered on bytes delivered.
The default bitrates follow MOQOM's default camera ladder (180p 0.2, 360p 0.6, 720p 1.8, 1080p 4, 4K 12 Mbit/s). Tiers are by aggregate pixels received, the same boundaries Agora bills on.
Connect Agora to plan a migration
Paste an Agora Customer ID and Customer Secret (Agora Console, RESTful API). MOQOM sends them once, from its servers to api.agora.io over HTTPS, to read your project list and the last 90 days of usage by resolution tier. They are not saved, logged or sent back, and this page does not keep them.
Create a new Customer Secret for this, read-only if your Agora account offers that, and delete it in Agora Console when you are done.
Agora usage,
Estimate| Tier | Minutes | Assumed kbps | Agora list | MOQOM (estimate) | Saved |
|---|
Agora projects
Only the first 20 projects were read.
| Project | ID | State | Minutes | Note |
|---|
API keys
Backend keys manage the account and mint tokens. Mint keys only mint viewer and publisher tokens, and read-only keys only read, so an agent, MCP server or dashboard never needs a backend key. Relay keys only report usage from a self-hosted relay. Rotate a key to replace it without a gap: the new key works at once and the old one keeps working until the overlap ends.
| Name | Kind | ID | Created | Limits | State |
|---|
Mint and read-only keys default to 600 calls a minute; backend and relay keys have no limit unless you set one. A key used from outside its allowed networks is refused.
Store this key now. It is shown once and cannot be recovered, only revoked and replaced.
Rooms
Read-only. Creating rooms, moderation (kick, mute, ban) and minting tokens use the admin API ↗ with a backend key.
| Room | State | Owner | People | Devices | Recording | Created |
|---|
Room events
Joins, leaves, publishing, moderation and lifecycle changes as they happen. Choosing one room also replays its recent history. Newest first, last 500 kept in this tab.
| When | Room | Seq | Event | Detail |
|---|