Turn any API
into{ on-chain data }
in minutes
Create permissionless oracle jobs from external APIs and use the result directly inside your smart contract.
Turn any API
into{ on-chain data }
in minutes
Create permissionless oracle jobs from external APIs and use the result directly inside your smart contract.
{ Protocol pillars }
Oracle infrastructure for arbitrary data, not just price feeds.
SDK-first setup
Create the job, fund the subscription, and consume verified data from one developer flow.
Arbitrary data support
Prices, outcomes, scores, reserves, registries, telemetry, flags, hashes, or custom values — from any API.
One signature, every chain
Verify one threshold-signed payload across all supported EVM chains.
USDC subscriptions
Pay predictable monthly fees in USDC. No oracle token. No governance token.
Create the job, fund the subscription, and consume verified data from one developer flow.
Built for arbitrary API-backed data
Builder defines the job
SDK handles creation, funding, and usage
Apps consume verified data on demand
Chain-agnostic signed payloads
USDC-native, predictable subscriptions
Optimized around predefined price feeds
Vendor decides what data exists
Custom ops required for integrations
On-chain apps wait for feed updates
Chain-specific oracle setup
Native-token gas and token exposure
{ Solution }
From price feeds to programmable external data.
Molpha is not "better price feeds." It is an SDK-accessible oracle layer for arbitrary external data.
Old way
Molpha way
{ Start on testnet }{ Use Cases }
Where arbitrary data becomes executable
Molpha is not limited to price feeds. Any API-backed signal can become a verified input for smart contracts, agents, markets, and protocols.
01/06
Prediction markets
Settle markets with verified outcomes.
- Match result / score
- Election outcomes
- Weather at expiry
- Market close price
- Cancellation flag
Why Molpha fits
Prediction markets need settlement proof, not a permanentl feed.
02/06
AI agents
Let agents act on verifiable web data.
- Payment status
- Rebalance signal
- Risk lookup
- Delivery confirmation
- Off-chain task completion proof
Why Molpha fits
Molpha turns off-chain API responses into verifiable contract inputs.
03/06
RWA and finance
Bring off-chain financial references on-chain.
- Fund NAV
- Proof-of-reserves total
- SOFR / FX reference
- Invoice status
- Custody attestation
Why Molpha fits
RWA workflows rely on statuses, attestations, and custom reference data.
04/06
DePIN
Verify real-world network conditions on-chain.
- Uptime score
- Coverage status
- Outage flag
- Bandwidth usage
- Compute availability
Why Molpha fits
Protocols can verify external network state before execution.
05/06
Registries and compliance
Use external records as contract inputs.
- License validity
- Property status
- KYC / eligibility flag
- Sanctions result
- Title verification
Why Molpha fits
Many workflows require verifiable status checks — not price feeds.
06/06
Supply chain and trade finance
Trigger contracts from real-world logistics events.
- Shipment delivered
- ETA deviation
- Customs cleared
- Warehouse receipt
- Invoice approved / paid
Why Molpha fits
Business events can be verified directly from external APIs.
{ Use Cases }
Where arbitrary data becomes executable
Molpha is not limited to price feeds. Any API-backed signal can become a verified input for smart contracts, agents, markets, and protocols.
Prediction markets
01/06
Settle markets with verified outcomes.
- Match result / score
- Election outcomes
- Weather at expiry
- Market close price
- Cancellation flag
Why Molpha fits
Prediction markets need settlement proof, not a permanentl feed.
AI agents
02/06
Let agents act on verifiable web data.
- Payment status
- Rebalance signal
- Risk lookup
- Delivery confirmation
- Off-chain task completion proof
Why Molpha fits
Molpha turns off-chain API responses into verifiable contract inputs.
RWA and finance
03/06
Bring off-chain financial references on-chain.
- Fund NAV
- Proof-of-reserves total
- SOFR / FX reference
- Invoice status
- Custody attestation
Why Molpha fits
RWA workflows rely on statuses, attestations, and custom reference data.
DePIN
04/06
Verify real-world network conditions on-chain.
- Uptime score
- Coverage status
- Outage flag
- Bandwidth usage
- Compute availability
Why Molpha fits
Protocols can verify external network state before execution.
Registries and compliance
05/06
Use external records as contract inputs.
- License validity
- Property status
- KYC / eligibility flag
- Sanctions result
- Title verification
Why Molpha fits
Many workflows require verifiable status checks — not price feeds.
Supply chain and trade finance
06/06
Trigger contracts from real-world logistics events.
- Shipment delivered
- ETA deviation
- Customs cleared
- Warehouse receipt
- Invoice approved / paid
Why Molpha fits
Business events can be verified directly from external APIs.
If data is accessible
through an API
Molpha can make it
verifiable on-chain
{ How Molpha works }
From API to on-chain data in minutes
Create once. Request when needed. Verify anywhere.
01Subscribe
Choose a plan and activate your USDC subscription on Solana.
02Define the job
Create an API-backed job with custom parsing, freshness, and value rules.
03Request signed data
Request the latest result via SDK or gateway and receive a threshold-signed payload.
04Use on-chain
Verify or publish the signed data across supported chains.
01Subscribe
Choose a plan and activate your USDC subscription on Solana.
02Define the job
Create an API-backed job with custom parsing, freshness, and value rules.
03Request signed data
Request the latest result via SDK or gateway and receive a threshold-signed payload.
04Use on-chain
Verify or publish the signed data across supported chains.
{ For developers }
Easy integration in just a few minutes
Copy code into your smart contract and read verified data on-chain.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
import { Connection } from "@solana/web3.js";
import { MolphaSDK } from "@molpha-oracle/sdk";
import { walletFromKeypairFile } from "@molpha-oracle/sdk/utils";
const sdk = new MolphaSDK({
connection: new Connection("https://api.devnet.solana.com", "confirmed"),
wallet: walletFromKeypairFile("~/.config/solana/id.json"),
});
const { result, signature } = await sdk.executeAndSubmit(jobId, {
apiConfig: {
url: "https://api.example.com/price",
responseParser: "$.price",
},
});
const feed = await sdk.solana.readFeed(jobId);
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
struct DataUpdate {
bytes32 jobId;
uint32 registryVersion;
uint32 signaturesRequired;
bytes32 value;
uint64 canonicalTimestamp;
}
struct SchnorrSignature {
bytes32 signature;
address commitment;
uint256 signersBitmap;
}
interface IMolphaVerifier {
function verify(DataUpdate calldata dataUpdate, SchnorrSignature calldata schnorrData)
external view returns (bool);
}
contract MolphaConsumer {
IMolphaVerifier public immutable verifier;
constructor(address _verifier) {
verifier = IMolphaVerifier(_verifier);
}
function readValue(DataUpdate calldata update, SchnorrSignature calldata sig)
external view returns (bytes32 value, uint64 timestamp) {
require(verifier.verify(update, sig), "invalid update");
return (update.value, update.canonicalTimestamp);
}
}
{ Secure by design }
Security is not a feature. It’s the oracle.
External data becomes a protocol risk the moment smart contracts rely on it. Molpha delivers cryptographic proof — not infrastructure promises.
Read DocsRotating verifier selection
Verifier sets rotate deterministically between rounds, reducing fixed-node trust.
Threshold-signed data
Selected verifiers independently fetch, compute, and sign the same value.
Bonded verifier nodes
Verifier nodes stake USDC and can be penalized for provable misbehavior.
Stateless verification
Every payload includes signer metadata for visible, auditable verification.
Signer transparency
Signer participation is embedded directly into every payload.
User-controlled private API keys
API credentials remain encrypted and controlled by the job owner.
Config-bound payloads
Payloads are cryptographically bound to the job configuration.
{ Pricing }
Choose the right plan for your workload
Transparent pricing for public and private oracle execution across every stage of growth.
Starter
For developers evaluating the protocol and testing integration
Free
/ month
1,000 public ops
1 sandbox job
Public jobs only
Testnet only
Builder
For builders launching their first public mainnet workloads.
$49
/ month
10,000 public ops
2 jobs included
1 mainnet chain
3-of-5 signing
$10 per 10k public ops
Starter
For developers evaluating the protocol and testing integration
Free
/ month
1,000 public ops
1 sandbox job
Public jobs only
Testnet only
Builder
For builders launching their first public mainnet workloads.
$49
/ month
10,000 public ops
2 jobs included
1 mainnet chain
3-of-5 signing
$10 per 10k public ops
{ Philosophy }
Why we’re building Molpha
Blockchains made execution verifiable, but real-world data still lives off-chain.
Accessing it often means relying on closed feeds, custom integrations, or unnecessary infrastructure complexity.
We believe off-chain data should be open, composable, and verifiable by default.
Mission
Make external data a native, verifiable input to on-chain applications.
Vision
A world where smart contracts can safely interact with off-chain systems without depending on closed oracle access.
Goal
Make verified data simple to create, simple to access, and usable across chains.
{ Try Molpha }
Create your first verified API job
Start with any API endpoint. Get a signed payload. Verify it on-chain.
No sales calls
No long onboarding
No long-term commitments