About

About

MOR Token

Whitepaper

Bug Bounty

Security Audits

Products

Inference API

Capital

Morpheus Skill

Dashboards

Capital

Deposit, Stake, Claim

Manage your MOR tokens and rewards.

Builders

MOR Rewards & Staking

Register your project, manage rewards and stake in other builders

Resources

Learn

Protocol Docs

Full Morpheus documentation

FAQs

Common questions answered

Newsletter

Weekly Morpheus updates

Changelog

See what has shipped

Tools

Templates

Jumpstart app development

MOR Calculator

Compare pricing & staking yields

Session Lifecycle

Track your MOR sessions on-chain

TEE Roadmap

Hardware-enforced AI privacy

Network Status

Live model availability & uptime

Community

Projects

Community-built projects on Morpheus

Buy MOR
AboutMOR TokenWhitepaperBug BountySecurity Audits
Inference APICapitalMorpheus Skill
Deposit, Stake, Claim
MOR Rewards & Staking
Protocol DocsFAQsNewsletterChangelog
TemplatesMOR CalculatorSession LifecycleTEE RoadmapNetwork Status
Projects
OverviewModelsDocs

OpenAI-compatible AI inference for developers.

Route production AI traffic through a decentralized inference network with TEE-backed providers, no vendor lock-in, and the same API shape your apps already use.

Checking network status…

Get API KeyView Models
https://api.mor.org/api/v1
Deep DiveNetwork Status
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
import openai

client = openai.OpenAI(
    base_url="https://api.mor.org/api/v1",
    api_key="your-api-key"
)

response = client.chat.completions.create(
    model="llama-3-70b",
    messages=[
        {"role": "user", "content": "Hello, Morpheus!"}
    ]
)

print(response.choices[0].message.content)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
import OpenAI from 'openai';

const openai = new OpenAI({
  baseURL: 'https://api.mor.org/api/v1',
  apiKey: 'your-api-key',
});

async function main() {
  const completion = await openai.chat.completions.create({
    messages: [{ role: 'user', content: 'Hello, Morpheus!' }],
    model: 'llama-3-70b',
  });

  console.log(completion.choices[0].message.content);
}

main();
1
2
3
4
5
6
7
8
9
10
11
12
curl https://api.mor.org/api/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer your-api-key" \
  -d '{
    "model": "llama-3-70b",
    "messages": [
      {
        "role": "user",
        "content": "Hello, Morpheus!"
      }
    ]
  }'

OpenAI Compatible

Uses the standard OpenAI API schema. Change your base URL and API key — nothing else. Your existing code ships as-is.

TEE-Backed Providers

Phase 1 TEE adds hardware attestation on the provider side, making the runtime verifiable and blocking provider-side memory inspection or image tampering.

30+ Models

Access GLM 5, Kimi K2.5, MiniMax M2.5, Qwen3 Coder, Gemma 4, Arcee Trinity, and 40+ more models through one API.

No Prompt Logging

Morpheus does not log prompts or responses. TEE strengthens the provider trust model, while the API gateway remains the managed access layer.

Decentralized Network

Backed by a global network of independent inference providers. No central operator to go down, rate-limit you, or change the rules.

No Vendor Lock-In

Sovereign infrastructure you control. Because the API is standard OpenAI schema, you can migrate away in seconds if you ever need to.

Frequently Asked Questions

Two changes: set base_url to https://api.mor.org/api/v1 and swap in your Morpheus API key. The rest of your code stays identical because Morpheus uses the standard OpenAI API schema.
You keep the same OpenAI-compatible developer experience, but requests are fulfilled by a decentralized provider network instead of a single AI vendor. With Phase 1 TEE, TEE-enabled providers now add hardware attestation on the provider side, so the runtime can be verified instead of trusted on reputation alone.
We support 30+ models including GLM 5, Kimi K2.5, MiniMax M2.5, Qwen3 Coder, Gemma 4, Arcee Trinity, and many more. Check the Models tab for the full searchable catalog.
Morpheus does not log prompts or responses. Phase 1 TEE adds verifiable protection on the provider side, but if you use the API Gateway, the gateway layer itself is still a managed convenience layer rather than an attested one.
Today, Phase 1 protects the provider runtime with hardware attestation, encrypted memory, and anti-tampering guarantees. It improves trust in the provider path, but it does not yet make the API Gateway itself cryptographically attestable, and external LLM hops still sit outside the TEE boundary.
Check the documentation and Models tab for current rates. Because inference is sourced from a decentralized network of independent providers, there is no single pricing authority — the market sets competitive rates.

Morpheus

Privacy Policy
Ask Morphy chat assistant