EXTENDED DOCUMENTATION

Providers

Morpheus Oracle supports two provider modes:

Built-in providers — selected by
text
```
provider
```
and configured per project in Supabase
Custom source requests — user-supplied
text
```
url
```
, optional encrypted token/payload, and optional compute script

Built-in Providers

Current built-ins:

text
```
twelvedata
```
text
```
binance-spot
```
text
```
coinbase-spot
```

Built-ins are intentionally raw:

no aggregation
no smoothing
no medianization
no extra normalization beyond provider-specific request formatting and response extraction

TwelveData

Required env:

text
```
TWELVEDATA_API_KEY
```

Typical config:

json
{
  "symbol": "NEO-USD",
  "endpoint": "price",
  "interval": "1min"
}

Binance Spot

Required env:

none

Typical config:

json
{
  "pair": "NEO-USD",
  "symbol": "NEOUSDT",
  "base_url": "https://api1.binance.com"
}

Coinbase Spot

Required env:

none

Typical config:

json
{
  "symbol": "NEO-USD"
}

Provider Config Control Plane

Project-level provider configs are stored in

text

morpheus_provider_configs

Management endpoint:

text

GET /api/provider-configs?project_slug=demo

text
```
POST /api/provider-configs
```

text

DELETE /api/provider-configs?project_slug=demo&provider_id=twelvedata

Recommended production protection:

set

text

MORPHEUS_PROVIDER_CONFIG_API_KEY

or a legacy fallback

text

ADMIN_CONSOLE_API_KEY

send it via

text

x-admin-api-key

text

Authorization: Bearer ...

The dashboard includes a Provider Configs panel that can manage these records directly.

Request-Time Resolution

Both the web API layer and the Phala worker can resolve provider defaults from Supabase when

text

project_slug

and

text

provider

are present.

The web API layer resolves provider defaults before proxying to Phala:

text

GET /api/feeds/:symbol?provider=twelvedata&project_slug=demo

text

POST /api/oracle/query

with

text

{ "provider": "twelvedata", "project_slug": "demo" }

text
```
POST /api/oracle/smart-fetch
```
with the same fields

Resolution rules:

request-level
text
```
provider_params
```
override stored project config keys
stored project config fills in missing provider defaults
disabled project providers are rejected before the request reaches Phala

Custom Source Requests

Users can bypass built-ins and send direct Oracle requests with:

text
```
url
```
optional
text
```
encrypted_token
```
or
text
```
encrypted_payload
```
optional
text
```
script
```
or
text
```
script_base64
```

This supports three useful modes:

plain fetch — URL only
fetch + compute — URL plus script
private fetch + compute — URL plus encrypted payload plus script

PriceFeed Pair Catalog

Default built-in USD pairs now cover:

Core crypto:

text
```
NEO-USD
```
text
```
GAS-USD
```
text
```
FLM-USD
```
text
```
BTC-USD
```
text
```
ETH-USD
```
text
```
SOL-USD
```
text
```
TRX-USD
```
text
```
BNB-USD
```
text
```
XRP-USD
```
text
```
DOGE-USD
```
text
```
USDT-USD
```
text
```
USDC-USD
```

Commodity / hard-asset:

text
```
PAXG-USD
```
text
```
WTI-USD
```
text
```
BRENT-USD
```
text
```
NATGAS-USD
```
text
```
COPPER-USD
```
text
```
WHEAT-USD
```
text
```
CORN-USD
```
text
```
SOY-USD
```

Equities / ETFs:

text
```
AAPL-USD
```
text
```
GOOGL-USD
```
text
```
MSFT-USD
```
text
```
AMZN-USD
```
text
```
TSLA-USD
```
text
```
META-USD
```
text
```
NVDA-USD
```
text
```
SPY-USD
```
text
```
QQQ-USD
```
text
```
GLD-USD
```

FX:
- text
```
EUR-USD
```
- text
```
GBP-USD
```
- text
```
JPY-USD
```
  (inverted from
  text
```
USD/JPY
```
  )
- text
```
CNY-USD
```
  (inverted from
  text
```
USD/CNY
```
  )

Production sync defaults to

text

twelvedata

only. Other built-in providers remain available for Oracle fetch flows and project-specific overrides.

Inspect at runtime with:

text
```
GET /api/feeds/catalog
```
or worker
text
```
GET /feeds/catalog
```

On-chain storage is provider-scoped, for example:

text
```
TWELVEDATA:NEO-USD
```
text
```
BINANCE-SPOT:NEO-USD
```

Canonical pair table

Use these names exactly in contracts, automation jobs, and documentation. Under the global

text

1 USD = 1,000,000

precision model, direct pair ids such as

text

FLM-USD

and

text

JPY-USD

are canonical again.

Deprecated legacy storage key:

historical basket keys such as
text
```
TWELVEDATA:1000FLM-USD
```
and
text
```
TWELVEDATA:1000JPY-USD
```
should be treated as deprecated
use
text
```
TWELVEDATA:FLM-USD
```
and
text
```
TWELVEDATA:JPY-USD
```
on-chain instead
use
text
```
FLM-USD
```
and
text
```
JPY-USD
```
everywhere in user-facing configs, contracts, and docs

Pair	Category	Meaning	TwelveData symbol	On-chain unit	Note
text `NEO-USD`	Crypto	price of 1 NEO in USD	text `NEO/USD`	text `1 NEO`
text `GAS-USD`	Crypto	price of 1 GAS in USD	text `GAS/USD`	text `1 GAS`
text `FLM-USD`	Crypto	price of 1 FLM in USD	text `FLM/USD`	text `1 FLM`	direct pair under the global 1e6 USD scale
text `BTC-USD`	Crypto	price of 1 BTC in USD	text `BTC/USD`	text `1 BTC`
text `ETH-USD`	Crypto	price of 1 ETH in USD	text `ETH/USD`	text `1 ETH`
text `SOL-USD`	Crypto	price of 1 SOL in USD	text `SOL/USD`	text `1 SOL`
text `TRX-USD`	Crypto	price of 1 TRX in USD	text `TRX/USD`	text `1 TRX`
text `PAXG-USD`	Crypto	price of 1 PAXG in USD	text `PAXG/USD`	text `1 PAXG`	gold-backed token
text `USDT-USD`	Crypto	price of 1 USDT in USD	text `USDT/USD`	text `1 USDT`
text `USDC-USD`	Crypto	price of 1 USDC in USD	text `USDC/USD`	text `1 USDC`
text `BNB-USD`	Crypto	price of 1 BNB in USD	text `BNB/USD`	text `1 BNB`
text `XRP-USD`	Crypto	price of 1 XRP in USD	text `XRP/USD`	text `1 XRP`
text `DOGE-USD`	Crypto	price of 1 DOGE in USD	text `DOGE/USD`	text `1 DOGE`
text `WTI-USD`	Commodity	WTI crude oil reference price in USD	text `WTI/USD`	text `WTI reference unit`
text `BRENT-USD`	Commodity	Brent crude spot reference price in USD	text `XBR/USD`	text `Brent spot reference unit`
text `NATGAS-USD`	Commodity	natural gas reference price in USD	text `NG/USD`	text `natural gas reference unit`
text `COPPER-USD`	Commodity	copper futures proxy in USD	text `HG1`	text `1 copper futures reference unit`	front-month proxy
text `WHEAT-USD`	Commodity	wheat futures proxy in USD	text `W_1`	text `1 wheat futures reference unit`	front-month proxy
text `CORN-USD`	Commodity	corn futures proxy in USD	text `C_1`	text `1 corn futures reference unit`	front-month proxy
text `SOY-USD`	Commodity	soybean futures proxy in USD	text `S_1`	text `1 soybean futures reference unit`	front-month proxy
text `AAPL-USD`	Equity	price of 1 AAPL share in USD	text `AAPL`	text `1 share`
text `GOOGL-USD`	Equity	price of 1 GOOGL share in USD	text `GOOGL`	text `1 share`
text `MSFT-USD`	Equity	price of 1 MSFT share in USD	text `MSFT`	text `1 share`
text `AMZN-USD`	Equity	price of 1 AMZN share in USD	text `AMZN`	text `1 share`
text `TSLA-USD`	Equity	price of 1 TSLA share in USD	text `TSLA`	text `1 share`
text `META-USD`	Equity	price of 1 META share in USD	text `META`	text `1 share`
text `NVDA-USD`	Equity	price of 1 NVDA share in USD	text `NVDA`	text `1 share`
text `SPY-USD`	ETF	price of 1 SPY share in USD	text `SPY`	text `1 ETF share`
text `QQQ-USD`	ETF	price of 1 QQQ share in USD	text `QQQ`	text `1 ETF share`
text `GLD-USD`	ETF	price of 1 GLD share in USD	text `GLD`	text `1 ETF share`
text `EUR-USD`	FX	price of 1 EUR in USD	text `EUR/USD`	text `1 EUR`
text `GBP-USD`	FX	price of 1 GBP in USD	text `GBP/USD`	text `1 GBP`
text `JPY-USD`	FX	price of 1 JPY in USD	text `USD/JPY`	text `1 JPY`	fetched as text `USD/JPY` , then inverted
text `CNY-USD`	FX	price of 1 CNY in USD	text `USD/CNY`	text `1 CNY`	fetched as text `USD/CNY` , then inverted

Selection Model

PriceFeed can use a built-in provider directly
Privacy Oracle can use either a built-in provider or a custom URL flow
Provider configs let each project pin defaults without hardcoding them into requests

Previous Built-in Compute NextDeployment Node

REVISION 1.0.2LAST UPDATED: 2026-03-11

EDIT ON GITHUB