Skip to content
GitHub

Stele web app

Preview

Stele is a standalone public web application for discovering services and, as the product matures, coordinating work between people and agents. The public preview is served at stele.monolythium.com. The intended product is not embedded in the Monolythium desktop, browser, or mobile wallet.

Stele is retired from the intended desktop product, but that release direction is not proof of absence from every existing artifact. Older or current unreconciled desktop preview builds may still retain a gated legacy Stele surface. Verify the installed version, its release notes, and the UI directly; installed-release evidence is authoritative. A legacy desktop view is not the supported standalone product.

The hosted preview targets the registered, value-less public testnet on chain ID 69420. Its availability does not prove provider participation, economic readiness, mainnet availability, or a settlement guarantee.

The current build is deliberately fail-closed:

Capability Current status
View the product shell and browse preview listings Available at stele.monolythium.com; listing data is illustrative unless its provenance says otherwise
Sign in with a browser wallet Available in the v0.4.5 GitHub prerelease, with checksums and cosign bundles; Chrome Web Store publication remains pending
Prepare private provider-listing drafts Available at stele.monolythium.com/studio; create, edit, preview, and delete durable wallet-owned drafts without publishing or creating a transaction
Connect the local Stele MCP profile Available in the v0.1.0 GitHub prerelease; exactly three read/status tools and no wallet authority
Hosted booking-approval draft tool Deployed and OAuth-accessible; production returned 0 published services during the July 16, 2026 release validation, so no successful booking-approval draft is currently possible
Book, accept, pay, escrow, dispute, or review Unavailable
Network Public testnet 69420
Economic writes Disabled
Hosted signing Disabled

In machine-readable deployment metadata, the last two controls are represented as economicWritesEnabled: false and hostedSigningEnabled: false. A UI label or draft identifier never overrides those gates.

Economic writes are disabled. Hosted signing is disabled.

The hosted preview is public-by-design: browsing does not require a wallet. A wallet is requested only when an authenticated application session is useful. At stele.monolythium.com/studio, an authenticated user can create, edit, preview, and delete durable, wallet-owned private provider-listing drafts. Those drafts are not published, discoverable, or transactable; they remain separate from the public catalog, which still contains 0 published services. The Studio has no publish, signing, submission, booking, payment, or settlement control.

The browser application exposes no customer booking, payment, or settlement action. The hosted OAuth MCP’s booking-approval draft tool is deployed and non-economic, but it cannot return a successful booking-approval draft while the production catalog has no published service. Private provider-listing drafts do not satisfy that published-listing prerequisite.

Wallet login signs a short-lived challenge bound to the requesting domain and origin, active address, chain ID, genesis hash, nonce, expiry, and requested scopes. It creates an application session only. It is not a transaction, pays no fee, and moves no value.

The browser wallet remains a generic authorization surface. It does not contain Stele screens or Stele data, and Stele never receives a recovery phrase, seed, or private key.

What a hosted booking-approval draft means

Section titled “What a hosted booking-approval draft means”

The live hosted MCP exposes a tool for creating a short-lived Stele booking-approval draft containing only a listing ID, workflow kind, and requested units. A real published listing must exist. Production search returned 0 services during the July 16, 2026 release validation, so no successful booking-approval draft can currently be created; an unknown listing ID fails closed. When a listing exists, its draft remains nonbinding. It is not a booking, provider acceptance, reservation, payment, escrow deposit, or guarantee that a provider will perform work. Its review page cannot approve or execute the draft.

This is a different record from a private provider-listing draft in the Studio. Neither the hosted nor local MCP can list, read, update, delete, or publish an existing Studio draft.

Do not put secrets, regulated records, private messages, or sensitive attachments into the public preview. Private rooms, files, and end-to-end encryption are still planned.

Stele has two distinct MCP boundaries:

  • The hosted Stele MCP is available at https://stele.monolythium.com/mcp. It is a keyless, OAuth-protected surface whose authenticated tools/list response is authoritative for the runtime inventory. Its deployed stele_search_services and stele_create_booking_draft operations provide public-catalog search and a fail-closed booking-approval draft. The booking tool requires a real published listing, and production currently has none. Any future successful booking-approval draft remains nonbinding and non-economic. It returns a human-review URL; it cannot approve, contact a provider, sign, submit, broadcast, reserve, pay, or lock funds. Booking-draft creation fails closed unless its durable backend and release-readiness gate are healthy. See Connect an agent for tested Codex and Claude Code setup.
  • The local lyth_mcp Stele profile is available in the v0.1.0 GitHub prerelease and is limited to exactly three read/status tools: connection status, service search, and dedicated-agent-wallet status. It has no wallet or key access and cannot prepare, sign, submit, or broadcast transactions.

Only when the authenticated tools/list response includes the exact stele_create_provider_listing_draft name may a client call that tool. Each successful create operation produces exactly one new private, wallet-owned, unpublished provider-listing draft. An idempotent replay returns that same draft without creating another. If the name is absent, the operation is unavailable. It is create-only: it cannot list, read, update, delete, or publish an existing draft, and it cannot sign, submit, or settle a transaction.

The hosted profile must remain keyless. Any future local economic profile would be a separate release requiring a dedicated-wallet lifecycle, protocol controls, simulation, explicit approval, and independent end-to-end validation. That future design is not part of the exact-three profile and cannot be inferred from SDK signing primitives.

Neither MCP surface nor a hosted model may receive a user’s private key.

Stele’s product direction includes provider publication, availability, verified receipts, escrow, dispute resolution, and reputation. Private provider-listing drafts are available, but those later capabilities remain target capabilities rather than current claims. No Stele fee schedule, commission, supported settlement asset, arbiter list, connector certification, or mainnet availability is active today.