DUST status, transaction building and submission, and indexer queries for Midnight mainnet and preprod. REST over HTTPS, OpenAPI 3.1, no node to run.
{ block { height hash } }
Nexus Midnight API at a glance
every endpoint on both networks, with stagenet available read-only
registration status, account state, and registration transactions over REST
submit signed, already proven, or prove-and-submit on Nexus
machine-readable spec published at /v3/api-docs
status page with live health for core subsystems
Midnight chain access: DUST, transactions, and the indexer on one REST API
A Midnight REST API over plain HTTPS. The same base URL and X-Api-Key header as Cardano and Bitcoin, with an OpenAPI 3.1 spec that generates typed clients.
Six endpoint groups cover what a Midnight app needs today. The same endpoints serve mainnet and preprod, each with its own scoped key.
# DUST registration status for a Cardano reward address, mainnet
BASE="https://nexus.gerowallet.io/api/midnight/midnight-mainnet"
STAKE="stake1u9x2..."
curl "$BASE/dust/status?cardanoRewardAddress=$STAKE" \
-H "X-Api-Key: nxs_your_api_key_here"The network is in the path (midnight-mainnet, midnight-preprod), the key in the header. Each key is scoped to one chain and one network.
DUST status
Registration status, generation rate, and capacity for a single reward address, or up to 50 in one batch call.
View in docsDUST registrations
Build the Cardano-side registration, update, and deregistration transactions, and list live registrations.
View in docsDUST account state
The Midnight-side DUST account for an address, and a state snapshot for sync.
View in docsTransactions
Build an unshielded NIGHT transfer, then submit it signed, already proven, or prove-and-submit on Nexus.
View in docsTransaction UTXOs
The unshielded UTXO view of any Midnight transaction: created and spent outputs by hash.
View in docsNetwork info and indexer
Indexer, prover, and node endpoints plus the current era, and a GraphQL passthrough to the Midnight indexer.
View in docsDUST without the plumbing
DUST is the shielded resource that pays Midnight fees. It is generated by holding NIGHT, regenerates toward a cap, and decays when the backing NIGHT moves. Nexus gives you the registration flow and the live status as REST calls.
Build the registration
POST /dust/build-registration-txreturns the Cardano transaction (txCbor) that maps a reward address holding NIGHT to a DUST address. Your wallet signs it.Submit it on Cardano
The registration is an ordinary Cardano transaction, so any Cardano submit path works, including the Nexus Cardano API.
Read the status
GET /dust/statusreturnsregistered,nightBalance,generationRate,currentCapacityandmaxCapacity, so your app can show when DUST is ready to spend.
- cardanoRewardAddress
- "stake1u9x2…"
- dustAddress
- "mn_dust…9fzk"
- registered
- true
- nightBalance
- "12000000000"
- generationRate
- "5 DUST / NIGHT"
- currentCapacity
- "49400"
- maxCapacity
- "60000"
Illustrative values. Field names are the live response. Full schema in the docs.
New to NIGHT and DUST? GeroWallet's guides cover the basics: What is DUST, NIGHT, cNIGHT and DUST explained, and How to generate DUST. This page covers the same flow as REST calls for your own app.
Prove where you want
Proving is the expensive step of a Midnight transaction. Nexus offers three submit routes so you decide who does it.
- Build and sign
- Prove
- Submit to Midnight
Send the signed, unproven transaction. Nexus proves, binds, and submits it. The default for unshielded NIGHT transfers built with /tx/build-unshielded.
For shielded transactions your app built with the Midnight SDK: Nexus runs the proof and submits.
You already ran the proof against your own prover. Nexus only submits, no proving on our side.
Every route returns the transaction hash. Mainnet and preprod; stagenet is read-only.
Running your own prover, or proving at volume? Talk to us about Dedicated infrastructure.
Built by the team that ships a Midnight wallet
Nexus is built by A.D. Labs LTD, the team behind GeroWallet, which ships DUST generation in-wallet on Midnight mainnet. The same team runs Cardano, Bitcoin, and Midnight access for Nexus from one account.
Flat Midnight API pricing
Flat monthly plans instead of per-call metering. Plans start at $9 on Starter, Builder comes with a 7-day trial, and a Midnight key is included in every plan's key allowance. Every price is on the pricing page before you sign up.
Starter
$9/mo
- 3M requests / month
- 10 req/s
- 2 API keys
- Core API only
Prototypes and hobby projects.
Builder
7-day trial$29/mo
- 10M requests / month
- 25 req/s
- 4 API keys
Indie devs and side projects.
Growth
$79/mo
- 30M requests / month
- 50 req/s
- 7 API keys
Startups and DApp teams.
Scale
$199/mo
- 50M requests / month
- 100 req/s
- 13 API keys
Production applications.
Enterprise
$499/mo
- 200M requests / month
- 500 req/s
- Unlimited API keys
Exchanges, aggregators, and institutional users.
Add-ons: Market Data $19, Wallet Analytics $15, Transaction Builder $19, MCP Server $19, IPFS $5 per month, from Builder up. Bundles: Data $19, Build + AI $19, Complete $29. WebSocket packages start at $29 per month.
Midnight API questions, answered
What developers ask before putting Nexus behind a Midnight app.
What is the Midnight API?
A hosted REST API for the Midnight network. Instead of running a Midnight node, an indexer, and a proof server, you call Nexus endpoints for DUST registration status and account state, build and submit unshielded transactions, read a transaction's UTXOs, and forward GraphQL queries to the Midnight indexer. Authentication is an nxs_ API key in the X-Api-Key header, the same as Nexus's Cardano and Bitcoin APIs.
Which Midnight networks does Nexus support?
Mainnet and preprod for every endpoint. Stagenet is available read-only: network info, transactions, DUST status, and the indexer proxy work, while the transaction build and submit routes answer 501 there because stagenet runs a newer ledger version than the transaction toolchain. The network is part of the URL: /api/midnight/midnight-mainnet, /api/midnight/midnight-preprod, /api/midnight/midnight-stagenet.
Do I need my own proof server?
No. For unshielded NIGHT transfers, /tx/submit takes the signed transaction and Nexus proves, binds, and submits it. For shielded transactions your app builds with the Midnight SDK, /tx/prove-and-submit runs the proof on Nexus. If you run your own prover, /tx/submit-proven submits without proving.
How does DUST registration work through Nexus?
DUST is generated by holding NIGHT. To start generating from NIGHT held on Cardano, a Cardano reward address is registered to a Midnight DUST address. Nexus builds that registration transaction (/dust/build-registration-tx returns the CBOR for your wallet to sign), and after it is on chain, /dust/status reports registered, the NIGHT balance, the generation rate, and current and maximum DUST capacity. Update and deregistration transactions are built the same way.
Can I use the Midnight API from a Cardano wallet or app?
Yes. DUST registration is a Cardano transaction, and the status lookup is keyed by a Cardano reward address, so a Cardano wallet can offer the whole flow with a Midnight key alongside its Cardano key. Keys are scoped to one chain and one network, so a Cardano app adding Midnight issues a Midnight key from the same account and dashboard.
How much does the Midnight API cost?
The same flat monthly plans as the rest of Nexus: Starter $9, Builder $29 with a 7-day trial, Growth $79, Scale $199, Enterprise $499, each with a monthly request allowance and a rate limit rather than per-call metering. A Midnight key counts toward the plan's key allowance. Dedicated infrastructure is available on request.
Ship your Midnight app on one integration
DUST status, transaction building, three ways to submit, and the indexer behind one API key per network. Plans from $9 a month.
Dedicated infrastructure starts at $2,000 per month. A contractual SLA is available on Dedicated: contact sales.

