Skip to main content
Backends use Molpha when they need a verifiable API result that can later be checked by a smart contract, another service, or an AI agent. sdk.gateway.requestSignedData calls the subscription-backed gateway route (POST /v1/round/execute). A fresh wallet that has not subscribed (or been registered as a Delegate) receives 403 instead of a payload. Subscribe once with the signing wallet before the first round — or use the x402 agent path / AI agents quickstart for pay-per-request access.

1. Install the SDK

Requires Node.js >=20.19.0.

2. Initialize

3. Subscribe

Gateway rounds settle against an active USDC plan. Skip this only if the wallet already has a live subscription (or is an active delegate under one).
maxPriceUsdc is a safety bound: the transaction aborts if the on-chain price exceeds what you approved. Needs Devnet SOL for fees and Devnet USDC for the plan. If a separate hot key will sign gateway auth instead of the subscription owner, register it with add_delegate before calling requestSignedData.

4. Derive a feed ID

5. Request a signed payload

The result is ready for Solana submission, EVM verification, Starknet verification, or off-chain audit logging.

6. Publish to Solana when you need a maintained feed

Reading the maintained feed later:
The first successful submit creates the Solana Feed account if it does not exist.

7. Build contract arguments

Backend patterns

Next steps

SDK overview

Installation, wallet interface, and facade methods.

Gateway API

Request shape, response fields, caching, and auth notes.

Subscriptions

Plans, quota, and renewing access for /v1/round/execute.

x402 escrow

Pay-per-request agent path when you do not want a monthly plan.