What apps/games/platforms plug in, and how · content/platform_apps.md
Platform & App Compatibility — what works with the system
Date: 2026-09-11 · The integration menu: every platform/app/game type that can plug into QALS today, what each uses, and the integration surface (how many calls it takes).
Native integrations (LIVE today)
| Platform | Type | What it uses | Status |
|---|---|---|---|
| qalarc.com | web platform | full stack: wallet, credit, provenance, wiki | live (this site) |
| tradez.au | web platform | issuer points (qalclaim), payment top-up (qalpay), signal provenance (qalpipe) | integration-ready (3 curl calls) |
| goetica.ai | AI character platform | credits (1c = 10cr canon), metered chat, qal ID accounts, RunPod compute via qmarket | gateway live (28/28 selftest) |
| goetica_phone | PWA / mobile | DID sign-in, chat commitments on-chain, hold→settle metering | scaffold v0.4, qalnet gateway built |
| gmux | AI terminal fleet | per-session capped wallets, permission alerts → phone, status board | gmux-bridge live (30/30) |
| Qal Wallet | desktop app (Tauri) | everything: money, chat, compute, identity | v6 live |
| Phone bridge | mobile web | chats, files, redeem catalog, balance | live on tailnet |
| MCP clients (any AI agent) | agent tooling | 24 tools: chat, money, compute, market, provenance, exchange desk (8 exch_* since 2026-09-14) |
live (qalmcp) |
App types that plug in (the menu)
| App type | How it integrates | Effort |
|---|---|---|
| Games | in-game currency = QALS credits (loopd accounts per player); items as paid-unlock content (qalpub); tournaments as channels with pay-to-post entry; marketplace trades via qalbazaar escrow | days — REST calls |
| Chat/social apps | encrypted DMs (qalchat protocol), channels + roles (qalpub), value-in-message, pay-to-post communities | days |
| AI agent platforms | capped wallets per agent (loopd), MCP control plane, exec via qalsh, marketplace (bazaar) | hours-days |
| API/SaaS products | metered billing (qalkeys proxy or PriceTable+holds), subscriptions via epoch-drip, provenance receipts per deliverable | hours |
| Marketplaces (any goods) | escrowed trades with receipts (bazaar pattern), reputation from settled history, challenges with anchor verification | days |
| IoT / device fleets | device DIDs (controller-bound), tailscale-bound identity, micro-payments per job, usage anchoring | days |
| Content platforms | pay-to-open media (qalpub), creator earnings, tipping in chat, NFT receipts (planned kiosk) | days |
| Internal company systems | cost-centre metering (qalkeys org mode), approval flows via phone alerts, audit trails on-chain | days |
| Exchanges/OTC desks | swap engine (qalx AMM), later real-IOTA gateway post-VASP | built, gated |
| Payment platforms (PSPs) | webhook bridge (qalpay) — top-up now, payouts (cash-out interface built: quote live, gate on) | contract ready |
The integration surfaces (what "plugging in" means)
- Money only —
loopdagents + holds/settles (3 endpoints) — any app can charge and pay in credits - Money + identity — add
qalidDID sign-in + qoll-codes (2 endpoints) — users are people, not rows - + Communication — qalchat relay (envelopes) — chat with value in it
- + Markets — qmarket/qalbazaar/qalkeys REST — sell compute, data, API usage
- + Provenance — qalpipe anchor/verify (1 CLI call) — every artifact receipted on-chain
Each layer is optional; each is live. The pattern everywhere: your app keeps its own UX; the QALS layer adds money, identity, receipts.