Types of experiences
Scrapy can combine interface code and approved capabilities to build mini-games, interactive galleries, calculators, community boards, quizzes, idea collections, avatar tools and information dashboards. These are categories of possible builds, not a claim that every example is already published.
A good proposal states which information must be saved and which external service is needed. An attractive interface cannot make an unsupported service work.
| Building block | Examples | Boundary |
|---|---|---|
| Browser interactions | Puzzles, calculators, interactive stories | No unrestricted backend or network access |
| Private storage | Preferences, a saved character brief, personal progress | Data belongs to the signed-in citizen within that module |
| Shared storage and counters | Community boards, entries, simple rankings | Reviewed collections; authors control their own records |
| Market and chain reads | Token explorers, balance viewers, market dashboards | Approved DEX Screener and Robinhood read requests |
| Image generation | Avatar forges, personalised visual tools | Reviewed purpose, enabled service and weekly quota |
| World residents | Publish a selected generated character | Explicit confirmation; one resident per citizen |
| Wallet adapter | Direct ERC-20 swap interfaces | Reviewed permissions and operator activation required |
Persistence is part of the proposal
Private storage saves an object for one citizen. Shared storage exposes public records while restricting edits and deletes to their author. Counters support simple shared counts. Each module declares the collections it needs.
This storage can support game progress or scores, but a score submitted by browser code is not automatically cheat-proof. Competitive games with valuable prizes require additional server-side validation and a reviewed reward mechanism.
AI generation inside a module
The builder uses AI to write the module, but that does not automatically give the resulting module access to every AI service. Runtime image generation is an explicit supported capability. Town Chat has its own AI connection.
General-purpose text-generation endpoints inside arbitrary modules, live voice, audio generation and video generation are not in the current module capability set. A scripted character or template-based text tool should not be presented as a live AI agent.