MyProvider is the hosted operator GUI for Morpheus providers. It talks to your proxy-router over HTTP Basic Auth (same credentials as Swagger) and wraps the blockchain admin calls you would otherwise run by hand. Use it as the default path for first-time registration and day-to-day bid/config work — especially on SecretVM, where the node already exposes HTTPS on port 443.
This page describes MyProvider behavior including the onboarding wizard (active.mor.org lookup, SecretVM 5-secret export, Venice Diem presets). When in doubt, defer to the live app and Register on chain.
  1. Open myprovider.mor.org — use New provider onboarding (no node connection required yet).
  2. Pick a path: SecretVM TEE, Venice Diem resale, or Standard / Docker.
  3. Look up the model on active.mor.org inside the wizard — copy an existing Id when possible.
  4. Fill wallet / RPC / admin password and copy secrets (MODELS_CONFIG_CONTENT value for SecretVM, or a full 5-secret bundle).
  5. Deploy the node (SecretVM portal, Docker, or binary) with those secrets.
  6. Connect MyProvider to the node URL + Basic Auth; register the provider; bid on the existing model.
  7. Use Model Configuration Sync if you need to re-export MODELS_CONFIG_CONTENT after bidding.
  8. Verify with Verify your provider setup.
Mint a new model only when nothing suitable exists (new weights, or a required tee tag with no existing tee-tagged listing).

​
What it gives you today

FeatureSupported
Guided onboarding (SecretVM / Venice / standard)Yes
Look up models + competitor prices via active.mor.orgYes
Craft SecretVM 5 secrets + MODELS_CONFIG_CONTENT valueYes
Venice Diem API URL presetsYes
Connect to proxy-router API (Basic Auth)Yes
Register / update / delete providerYes
:3333 endpoint reachability checkYes
Bid on existing on-chain models (“Available Models”)Yes — prefer this
Create model + bid (single flow)Yes — use only for genuinely new models
Delete bids; replace bid priceYes
Model config sync + SecretVM / .env exportYes
Bootstrap .env generatorYes
Session monitoring / earnings dashboardNo

​
Authentication

MyProvider does not connect MetaMask or any browser wallet. It authenticates to your proxy-router:
  1. Enter the proxy-router base URL (https://your-node:8082 or SecretVM https://your-vm/).
  2. Enter the admin username/password from .cookie / COOKIE_CONTENT.
  3. The app reads the provider wallet from the node (GET /wallet) — that key must already be configured on the node.

​
HTTPS requirement

The hosted app at myprovider.mor.org can only call HTTPS proxy-router APIs (browser mixed-content rules).
Your nodeHow to use MyProvider
SecretVM (Traefik TLS on :443)Point MyProvider at https://<your-secretvm-url>/
Other HTTPS reverse proxy / ALBPoint at that HTTPS admin URL
HTTP-only :8082Use the desktop release or run npm run dev locally and connect to http://…:8082

​
When to use it vs Swagger / API

TaskBest surface
First-time provider + secrets + bid (esp. SecretVM / Venice)MyProvider onboarding + tabs
Join an existing marketplace modelMyProvider → Available Models, or API POST /blockchain/bids
Mint a genuinely new modelMyProvider Create Model & Bid, or Swagger
Bulk / scripted bid updatesAPI (endpoints reference)
TEE attestation inspectionSecretVM portal + cosign
Programmatic automationAPI

​
Agent / bot discovery

Plain-text surfaces on this host (no JS required):
PathPurpose
/llms.txtIndex + hard rules
/llms-full.txtOne-shot install → bid recipe
/AGENTS.mdAgent rules
/onboarding.mdDeploy-path steps
For protocol depth, agents should use nodedocs llms-full or MCP https://nodedocs.mor.org/mcp. Live models/prices: active.mor.org.