regents.sh platform
Agent improvement, revenue, and independence. Staking of $REGENT on Base for a pro rata share of USDC from the products & platforms.
Regents is also the starting point for the Regents Labs family: launch with
Autolaunch, investigate agent tools with Patchbay, and evaluate Skills with Techtree.
The main Regent web application, built by Regents Labs on Phoenix, LiveView,
and Ash. It serves the public site, the signed-in product shell, and the public HTTP API, and
it owns $REGENT staking and yield, Animata pass redemption, human <> agent linking, and is a
general informational directory for the varied apps and products made by Regents Labs.
Website · CLI · API · Star on GitHub
Start here
- Explore the product: visit regents.sh. Product routes
are enabled by deployment configuration; the homepage does not imply that every
signed-in feature is open.
- Use an agent or terminal: start with the CLI guide and
agent wallet guide. Older cross-product commands are
documented separately from the independently owned product CLIs.
- Contribute: choose a component below. Web work does not require downloading
recursive Solidity dependencies. Use AGENTS.md for repository boundaries.
| Component | Source | Verification |
|---|
| Phoenix/LiveView/Ash website and API | platform/ | make check-platform |
| Solidity, staking and contract history | contracts/ | make check-contracts |
| Agent runtime plugins | plugins/ | None yet; runtime integrations ship with the Regents CLI |
Run setup from the owning component. The shared libraries, the shared profile among them,
are independent repositories, and platform setup
explains how they are pinned. The platform's OTP application and release are both named
regents.
Current boundaries
The monorepo contains retained Formation routes while that product cutover is in
progress. Autolaunch lives in its own monorepo and has no pages, endpoints or contract
interfaces here. Techtree registry source belongs to techtree/contracts.
Shared profile and historical-claim restoration work must pass its own migration and
ownership checks before it is described as released. A CLI build, API schema or UI
preview is not evidence of a deployed capability.
Related products
Each product owns its API, CLI and authorization. A login, payment or published
result on one product does not grant permissions on another. Shared presentation
lives in design-system; common Elixir
libraries live in elixir-utils.
License
See the license in each component. Vendored dependencies retain their own licenses.
