A “resale” provider runs a Morpheus proxy-router but does not host the model itself. The proxy-router forwards prompts to a hosted backend (Venice, OpenAI, Anthropic, Hyperbolic, etc.) using the backend’s API key, and you collect MOR from the marketplace.

​
Why resale

  • You already pay for capacity at a hosted LLM provider that has spare headroom.
  • You want exposure to MOR earnings without operating GPUs.
  • You can stack on top of subscription plans (e.g. Venice Diem) and arbitrage between subscription cost and per-second MOR pricing.

​
Why not resale

  • You are bound by the upstream provider’s TOS — many forbid resale; check first.
  • Your margins depend on upstream pricing changes and rate limits.
  • You cannot offer TEE attestation guarantees (see TEE overview) because you do not control the backend.

​
Venice Diem holders

If you already pay for Venice Diem (or similar) and want a low-friction way to earn MOR from spare API quota, follow Reselling Venice (Diem): look up an existing model on active.mor.org → craft secrets in MyProvider → bid. That path is designed to be mostly graphical.

​
How it works mechanically

  1. You run a normal proxy-router (containerized or bare-metal) — see Container P-Node.
  2. In your models-config.json you set apiUrl to the upstream’s chat completions endpoint and apiKey to your upstream account key.
  3. You register your provider on chain, then prefer bidding on an existing model from active.mor.org — same as a standard full provider, just without the tee tag. Mint a new model only when nothing suitable exists. MyProvider is the easiest UI for this.
  4. Consumer prompts arrive on :3333, get routed to your proxy-router on :8082, which forwards to the upstream apiUrl. Upstream responses stream back the same way.

​
Things to watch for

Upstream TOS. Most commercial inference providers have explicit clauses about reselling. Read them. Reselling someone else’s API in violation of their TOS is your risk, not Morpheus’s.
  • Concurrency. Set concurrentSlots in models-config.json to a value your upstream account actually supports — over-promising leads to dropped sessions and reputation damage.
  • Latency. Resale adds two extra hops vs a colocated backend. Bid pricing should reflect this.
  • API compatibility. The proxy-router speaks OpenAI-shaped requests; your upstream should as well. Mappings exist for Anthropic and Prodia. See models-config.json.

​
Next steps

Container P-Node

Stand up a proxy-router container.

Reselling Venice

Concrete example: Venice Diem capacity.

Registering a bid

Bid pricing for resale economics.

On-chain registration

Same flow as a full provider (without tee).