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.
Recommended first-time flow
- Open myprovider.mor.org — use New provider onboarding (no node connection required yet).
- Pick a path: SecretVM TEE, Venice Diem resale, or Standard / Docker.
- Look up the model on active.mor.org inside the wizard — copy an existing
Idwhen possible. - Fill wallet / RPC / admin password and copy secrets (
MODELS_CONFIG_CONTENTvalue for SecretVM, or a full 5-secret bundle). - Deploy the node (SecretVM portal, Docker, or binary) with those secrets.
- Connect MyProvider to the node URL + Basic Auth; register the provider; bid on the existing model.
- Use Model Configuration Sync if you need to re-export
MODELS_CONFIG_CONTENTafter bidding. - Verify with Verify your provider setup.
tee tag with no existing tee-tagged listing).
What it gives you today
Authentication
MyProvider does not connect MetaMask or any browser wallet. It authenticates to your proxy-router:- Enter the proxy-router base URL (
https://your-node:8082or SecretVMhttps://your-vm/). - Enter the admin username/password from
.cookie/COOKIE_CONTENT. - 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).When to use it vs Swagger / API
Agent / bot discovery
Plain-text surfaces on this host (no JS required):
For protocol depth, agents should use nodedocs llms-full or MCP
https://nodedocs.mor.org/mcp. Live models/prices: active.mor.org.
Related
- Register on chain — discover → bid (canonical steps)
- SecretVM quickstart — MyProvider-first TEE path
- Reselling Venice (Diem) — Diem → Morpheus income path
- active.mor.org — live models and prices
- API endpoints — direct equivalents