# Nexus > Nexus is a full-stack blockchain data and transaction API for UTXO chains (Cardano, Bitcoin, Midnight), built by A.D. Labs LTD, the team behind GeroWallet. One account and one base URL cover chain data, DEX market data, wallet analytics, transaction building, and WebSocket streaming, with multi-provider failover for Cardano chain data. ## Key facts - Base URL: https://nexus.gerowallet.io/api - Auth: X-Api-Key header. API keys use the nxs_ prefix. Each key is scoped to one chain and one network. - Cardano networks: mainnet, preprod, and preview on the same endpoints, selected with the ?network= query parameter. - Machine-readable OpenAPI 3.1 spec: https://nexus.gerowallet.io/v3/api-docs - Cardano failover upstreams: Nexus-operated indexers, Yaci, Koios, and Blockfrost, with per-provider health checks. - Cardano chain data endpoint groups: accounts, addresses, assets and holders, blocks, epochs and protocol parameters, enriched stake pools, DReps and governance (Conway: proposals, votes, committee, constitution), scripts and datums, transactions, submit and evaluate. - Market Data add-on: prices, OHLCV candles, pools, TVL and reserves, order books, swaps, top traders, NFT collections and sales across 11 indexed Cardano DEXes, plus ADA/USD candles. - Wallet Analytics add-on: holdings, transaction history, and FIFO cost-basis P&L per wallet. - Transaction Builder add-on: server-side UTXO selection and fee calculation for transfers, staking, and Conway governance actions. Returns unsigned CBOR; users sign with their own keys, so Nexus never holds private keys. - WebSocket streaming: market-data topics on a 10-second cadence, plus Blueprints, self-serve on-chain event streams with UTXO or TRANSACTION granularity and REST backfill for replaying missed events. - DEX aggregator: best-price swap routing across verified venues Minswap V1 and V2, WingRiders V1 and V2, Splash, and SaturnSwap. Non-custodial. - MCP Server add-on: hosted Model Context Protocol endpoint so Claude and other AI agents can query Nexus data and tools with an API key. - IPFS add-on: resolve, inspect, and pin content through a Nexus-hosted node. - Bitcoin: chain data including ordinals, runes, and mempool. Midnight: network info, unshielded transaction build and submit, and DUST registration. - Over-quota behavior: HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, and Retry-After headers. No auto-ban. - Freshness: in an August 2026 test from a single client in Frankfurt, Nexus served new Cardano mainnet blocks a median 575 ms after the block timestamp against 3,845 ms on Blockfrost (6.7x), and served the new block first on 102 of 107 contested blocks. 119 blocks over 45 minutes at matched request rates. ## Pricing (flat monthly, USD) - Starter: $9/mo, 3M requests/month, 10 req/s, 2 API keys. - Builder: $29/mo, 10M requests/month, 25 req/s, 4 API keys. Comes with a 7-day trial. - Growth: $79/mo, 30M requests/month, 50 req/s, 7 API keys. - Scale: $199/mo, 50M requests/month, 100 req/s, 13 API keys. - Enterprise: $499/mo, 200M requests/month, 500 req/s, unlimited API keys, all add-ons and WS Unlimited included. - Dedicated: from $2,000/mo, isolated infrastructure and a contractual SLA, via sales. - Add-ons (all self-serve plans): Market Data $19/mo, Wallet Analytics $15/mo, Transaction Builder $19/mo, MCP Server $19/mo, IPFS $5/mo. - Bundles (all self-serve plans; one per plan): Data $19/mo (Market Data + Wallet Analytics, $34 separately), Build + AI $19/mo (Transaction Builder + MCP Server, $38 separately), Complete $29/mo (all four, $72 separately). IPFS and WebSocket packages are not bundled. - WebSocket packages (all self-serve plans): WS Starter $29/mo (2 connections, 100k messages), WS Pro $59/mo (10 connections, 2M messages), WS Unlimited $99/mo. - There is no free tier. The trial is 7 days on the Builder plan. ## Pages - [Home](https://nexus.gerowallet.io/): product overview, plan calculator, and the Blockfrost freshness benchmark - [Pricing](https://nexus.gerowallet.io/pricing/): every plan, add-on, bundle and WebSocket package, a plan comparison, and the pricing FAQ - [Cardano API](https://nexus.gerowallet.io/cardano/): the Cardano hub, endpoint groups, streaming, market data, transaction builder, governance, FAQ - [Blockfrost alternative](https://nexus.gerowallet.io/alternatives/blockfrost/): fact-checked Blockfrost vs Nexus comparison - [API documentation](https://nexus.gerowallet.io/docs): full endpoint reference with request and response shapes - [Blog](https://nexus.gerowallet.io/blog/) ## Full corpus - Marketing site, full text of every indexable page: https://nexus.gerowallet.io/llms-full.txt (generated from the site at build time) - API reference, every endpoint with request and response shapes: https://nexus.gerowallet.io/docs/llms-full.txt - [Status](https://status.gerowallet.io): public live health for core subsystems - [Get started](https://nexus.gerowallet.io/get-started/) ## Contact - Sales: nexus@gerowallet.io - Support: support@nexus.gerowallet.io --- # Full text of the marketing site Generated at build time from the pages listed in https://nexus.gerowallet.io/sitemap.xml. The API reference is a separate corpus: https://nexus.gerowallet.io/docs/llms-full.txt # Solada Markets, Powered by Nexus: Cardano Swaps URL: https://nexus.gerowallet.io/blog/solada-markets-powered-by-nexus/ Description: Solada Markets runs on the Nexus swap widget and market kit: best-price routing across Cardano DEXes, live charts, and native indexing of Solada tokens. Blog · Updated November 2, 2026 ## Solada Markets, Powered by Nexus: How a Cardano Launchpad Added Best-Price Swaps Solada and GeroWallet are now partners. Solada is a Cardano coin launchpad, and its trading hub, Solada Markets , runs on Nexus, the data and transaction API built by A.D. Labs, the team behind GeroWallet. Every swap on Solada Markets is routed by Nexus across Cardano's exchanges, and every price, chart and trade on the page is read from Nexus Market Data. This post explains what that integration actually does, why a launchpad needs it, and how any Cardano team can put the same stack on its own site. ### TL;DR - Solada Markets ( solada.fun/markets ) embeds the Nexus swap widget and the Nexus market kit. Swaps are routed across Cardano DEXes for the best price, and the user signs every transaction in their own wallet. - Order types on the page: market, limit, stop and OCO. - Nexus Market Data indexes Solada natively. GET /api/market/solada lists Solada tokens on the bonding curve and after they graduate, and graduates are indexed from the block that creates their pool. - Same stack, your site: a public partner key, an origin you register, and the Market Data add-on for the page's market reads. ### Why Solada chose a partner, in their words Solada announced the partnership on 2 November 2026, the same day it shipped Solada V3. Their announcement put the decision down to three things: Trust: "Our entire team is fully doxxed, and accountability matters to us. We want to know that the people we're building with share not only our vision but also our values." Execution: "Ideas are a dime a dozen. We look for teams that can actually deliver, keep improving and keep showing up even when the market gets tough." Strategic alignment: "The right partnership should make both projects stronger and create something useful for the people using them." And on the choice itself: "After several calls with Adam Cazes, partnering with @GeroWallet was a no-brainer. Adam and his team have been building on Cardano since 2021. Today, that work includes @NexusByGero , the engine behind Solada Markets." We take that as a standard to keep meeting, not a compliment to frame. ### What Nexus runs inside Solada Markets Solada Markets is the part of solada.fun where people trade any Cardano token, not only coins launched on Solada. Two Nexus components do the work: The swap widget ( ). A user picks a pair and an amount. Nexus quotes the trade across the DEXes it can build on, picks the best route, and returns an unsigned transaction . The user signs it in their own wallet, then Nexus co-signs and submits it. The aggregator is non-custodial: Nexus never holds the user's funds or keys. On mainnet the build path today covers Minswap (V1 and V2), WingRiders (V1 and V2), Splash and SaturnSwap, and the live list is always the one GET /api/aggregator/supported-dexes returns. The market kit ( ). Around the swap panel sits a full market page: a token screener with sparklines, a trending strip, market stats, token pages with candlestick charts, recent trades, an order book, per-DEX markets, top traders and a live swaps feed. The data comes from Nexus Market Data, which covers all 11 Cardano DEXes Nexus indexes. Every fee is shown in the swap details before the user signs, and on Solada Markets the order panel offers market, limit, stop and OCO orders. For Solada, this meant a complete trading surface without running an indexer, a pricing service or a routing engine. Solada keeps its own domain, branding and navigation; Nexus keeps the page and the routing working, and fixes and features reach Solada's users without a release on Solada's side. ### Launchpad tokens, from the curve to the pool A launchpad token has two lives. It starts on an off-chain bonding curve, priced by the launchpad, and if it fills its curve it graduates to an on-chain liquidity pool. Most market data products only see the second life, and often only after a delay. Nexus Market Data tracks both, for Solada and for snek.fun: source on a price row | What it means | SOLADA | A row from the Solada launchpad list: a token still on the curve, or a graduate, as Solada lists it | SOLADA_GRADUATE | A Solada token that graduated to an on-chain pool and is indexed like any other token: price, candles, swaps and pools from chain | absent | An ordinary token indexed from its on-chain pools | GET /api/market/solada returns Solada's tokens as a bare array of price rows, refreshed every 30 seconds: curl "https://nexus.gerowallet.io/api/market/solada?limit=50" \ -H "X-Api-Key: nxs_your_api_key_here" A Solada graduate is indexed in near real time: it is listed from the block that creates its pool, and from then on it appears in the main price lists such as /api/market/prices and /api/prices/latest . Launchpad tokens always carry verified: false , because they are not in the Cardano token registry (CIP-26). That flag describes the metadata, not the price. For a wallet, a portfolio tracker or a trading bot, this is the difference between a token that appears the moment it can be traded on chain and one that shows up a day later with no history. ### Put the same stack on your own site What Solada uses is available to any Cardano project with a swap box, a token page or a community site: - Create a public partner key on Cardano mainnet in the Nexus dashboard. It is public by design and only works from the browser origins you register on it. - Register your site's origin on the key. - Embed the widget, the market page, or both. The market page is two tags and one element: A partner key needs no Nexus plan to embed the swap widget. The market reads on the page need the Market Data add-on on the key owner's plan, and building and submitting swaps needs the Transaction Builder add-on. Teams that would rather build their own interface can call the same Market Data and aggregator endpoints from a server with an ordinary API key. See: Cardano market data API · See: Cardano transaction builder API ### Built for UTXO chains Solada Markets runs on the Cardano side of Nexus, where coverage is deepest: chain data, DEX market data across 11 exchanges, wallet analytics, transaction building, WebSocket streaming and the DEX aggregator. The same platform also serves Bitcoin (addresses, blocks, fees, mempool, ordinals, runes and transaction submit) and Midnight (network info, unshielded transaction build and submit, DUST registration), all on one Nexus account, with API keys scoped per chain and network. Live component health, latency and indexer sync lag are public at status.gerowallet.io . ### Welcome to Solada Solada closed its announcement with "More builders working together. More reasons to use Cardano. More ways to have fun." We agree on all three. Thank you to the Solada team for the trust, and congratulations on V3. If you run a Cardano product and want the same routing and market data behind it, start the 7-day Builder trial . ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # Cardano API Providers Compared (2026): How to Choose | Nexus URL: https://nexus.gerowallet.io/blog/cardano-api-providers-compared/ Description: Cardano API providers compared after Maestro's exit: what Blockfrost, Koios and Nexus cover, how each one prices, and how to pick the right data layer. Blog · Updated November 2, 2026 ## Cardano API Providers Compared: How to Choose a Data and Transaction Layer Most teams building on Cardano reach a point where running their own infrastructure stops being a good use of engineering time. A synced cardano-node , db-sync , an indexer and a chain-tip follower are a lot to operate for a team whose product is something else. At that point you start evaluating Cardano API providers: hosted services that sit between your application and the chain and hand back the data and transaction primitives your product needs. The shortlist changed in 2026. Maestro announced on 18 August 2026 that its developer API would retire on 18 September 2026, and it has now shut down, so the hosted options most teams compare today are Blockfrost, Koios and Nexus. This guide explains what a Cardano API provider does, the five kinds of capability they cover, how the three options differ, and what to weigh before you commit. ### TL;DR Every Cardano API provider serves chain data. They differ on everything above it. Blockfrost is the long-standing chain-data API, and Koios is the open-source, community-run one. Nexus, built by A.D. Labs, the team behind GeroWallet, is the full data and transaction layer: chain data plus DEX market data, wallet analytics, transaction building, a DEX aggregator and WebSocket streaming, on Cardano, Bitcoin and Midnight. | Blockfrost | Koios | Nexus | Chain data | Yes | Yes | Yes | Market data across 11 Cardano DEXes | No | No | Yes | Wallet analytics (FIFO P&L) | No | No | Yes | Transaction building (unsigned CBOR) | No | No | Yes | DEX aggregator (quote to submit) | No | No | Yes | Real-time delivery | Webhooks | No | WebSocket streaming | Official MCP server for AI agents | No | No | Yes | MeshJS provider | Yes | Yes | Yes | Chains | Cardano, Midnight (beta) | Cardano | Cardano, Bitcoin, Midnight | Pricing model | € tiers or pay as you go in ADA | Community tiers | Flat monthly plans from $9, 7-day Builder trial | SLA | Enterprise | None | Dedicated | Rule of thumb: if your product only ever reads blocks and transactions, any of the three will serve you. The moment it needs prices, P&L, transaction construction or live data, Nexus is the only one of the three that covers it without adding more vendors. ### What "Cardano API provider" means and who needs one A Cardano API provider is a hosted service that exposes blockchain data, and sometimes transaction building and real-time event feeds, through an HTTP or WebSocket interface. You do not operate the node and indexing stack yourself. Instead of querying a database you maintain, you call an endpoint with an API key. The teams who need one usually fall into three groups. dApp and DeFi builders. DEXes, lending protocols, NFT platforms, wallets and portfolio trackers need on-chain data, and often token prices, wallet profit and loss, and the ability to construct transactions, without standing up that machinery in-house. Multi-chain and UTXO teams. Teams building across Cardano, Bitcoin and Midnight want a consistent data model rather than a separate vendor and runbook per chain. Enterprises and institutional data consumers. Exchanges integrating Cardano, fintechs, analytics firms and trading desks bring procurement and compliance requirements: contractual uptime, data isolation, documented provenance, and pricing they can model in advance. The common trigger is the same across all three: the moment a feature needs more than raw block and transaction reads, or the moment a best-effort setup stops being reliable enough for production traffic. ### What Cardano API providers actually do It helps to separate "blockchain API" from "the full data layer a product needs." The first is a subset of the second. Provider capabilities fall into five categories. #### On-chain data The foundation: blocks, transactions, addresses, UTxO sets, native-asset balances, stake and delegation state, protocol parameters, and metadata. Because Cardano uses the extended UTXO model, this layer has to handle multi-asset outputs and UTxO-level queries as first-class concepts. Every serious provider offers on-chain data. This is table stakes. One subtlety worth understanding here is read consistency . A Cardano stack typically has more than one component watching the chain, for example db-sync for historical data and a separate follower for the chain tip. If those components fall out of sync, a transaction can be recorded in one view before it appears in another. That matters most when you chain transactions, because building a second transaction that spends an output from one you just submitted can fail against an inconsistent UTxO view. When you evaluate providers, ask specifically how they handle tip consistency. #### Market and DEX data Token prices, candles, liquidity, and trade history aggregated across Cardano's decentralized exchanges. This is a fundamentally different workload from on-chain reads: it requires decoding the on-chain activity of each DEX's contracts and normalizing it into prices and pairs. Cardano has many DEXes, several with multiple protocol versions, so "market data coverage" really means "how many of these venues are indexed and kept current." Blockchain-only APIs do not cover this layer at all. #### Wallet analytics Higher-level interpretation of a wallet's activity: holdings, transaction history, and realized profit and loss, often computed on a FIFO (first-in, first-out) cost basis. This is derived data, not raw chain data, and it requires the provider to reconstruct positions over time. Portfolio trackers, tax tooling, and institutional reporting depend on it, and it is one of the capabilities most often missing from blockchain-only APIs. #### Transaction building Constructing valid Cardano transactions server-side, such as ADA and native-token transfers, staking and delegation, governance actions and reward withdrawal, and returning an unsigned transaction (typically as CBOR) for the client to sign. The security-relevant design question is whether private keys ever touch the provider's servers. A sound model returns an unsigned transaction and keeps signing entirely client-side. Not every provider offers transaction building, and those that do vary widely in how many operations they support. #### Real-time streaming Push-based delivery of events, such as new blocks, address activity and price updates, over a persistent connection instead of repeated polling. For order books, live dashboards, and alerting, streaming removes the latency and overhead of asking "anything new?" on a loop. This is one of the less commonly offered capabilities in the Cardano provider landscape. The key takeaway: a provider can be excellent at on-chain data and offer none of the other four. Knowing which categories your product needs, now and one roadmap step ahead, is the single most useful thing to settle before comparing vendors. ### The trade-offs to weigh Beyond raw capability, four trade-offs tend to decide the choice. Breadth versus stitching. A blockchain-only API is perfectly adequate if on-chain reads are all you need. But if your product needs prices, P&L, or streaming, a narrow provider means integrating additional services and maintaining several integration surfaces. The cost is not just dollars. It is the operational overhead of keeping multiple vendors synchronized and the cascading-failure risk of more moving parts. Pricing model. Two models dominate. Flat tiers charge a predictable monthly rate for a request allowance, which is easy to budget against. Usage-based and compute-credit models charge per request, sometimes weighted by how expensive each call is, which can be efficient at low volume but harder to predict as traffic grows. When comparing, look past the headline number to whether you can forecast next month's bill. Reliability and support. Community-run and best-effort services are great for experimentation, but typically carry no SLA and no commercial support path. Production services with uptime obligations, especially regulated ones, generally need a contractual SLA, defined support response times, and sometimes isolated infrastructure. This is often the deciding factor for enterprise buyers. Single-chain versus multi-chain. If you only ever touch Cardano, a Cardano-only provider is fine. If you expect to add Bitcoin or Midnight, a provider that covers UTXO chains as a group, with the same data model and one bill, avoids a second vendor relationship later. The large EVM-focused platforms generally do not support Cardano or the UTXO model at all, so they rarely belong on a Cardano shortlist. ### The well-known Cardano providers A factual orientation to the names you will encounter. Pricing moves, so check current figures with each provider before deciding. #### Blockfrost Blockfrost is the established incumbent and a respected part of the Cardano ecosystem: a hosted REST blockchain API for Cardano, with webhooks and a wide range of SDKs. It offers flat plans at roughly €29 and €79 per month above an entry plan, a custom Enterprise tier, and a newer pay-as-you-go option billed per request in ADA. It lists Midnight support in beta. It is deliberately a blockchain API: it does not cover market data, wallet P&L, transaction building, or streaming. Teams sometimes self-host its open-source backend as usage scales. A July 2026 on-chain governance proposal to turn Blockfrost into a community-governed not-for-profit expired without ratification, so its commercial plans continue unchanged. The head-to-head is in Nexus vs Blockfrost . #### Koios Koios is an open-source, community-run, Cardano-only API with no central instance, and you can self-host it. Alongside public access it offers Pro and Premium plans at around $30 and $75 per month. Its Conway governance endpoints are among the deepest available. The trade-offs are inherent to its community model: single-chain, no SLA at any tier, no commercial support, and query timeouts on the heaviest queries. It is well suited to experimentation and cost-sensitive workloads, less so to production services with uptime obligations. The head-to-head is in Nexus vs Koios . #### Maestro Maestro was the broader dApp platform of the group, with an indexer, APIs and transaction tooling, priced on compute credits. On 18 August 2026 it announced that its developer API would retire on 18 September 2026 across Bitcoin, Cardano and Dogecoin, and it has now shut down. If your application called Maestro, the Maestro alternatives guide maps its endpoints to replacements. #### Demeter.run Demeter.run, from TxPipe, is adjacent rather than a direct head-to-head: a low-level infrastructure platform offering managed cardano-node , db-sync , Ogmios, Kupo, and related components, billed per connection-time. It is more complementary than competitive, and useful if you want managed building blocks rather than a high-level data API. #### How much does switching cost? One structural detail shapes this whole market. MeshJS and Lucid Evolution , the two dominant Cardano transaction-building libraries, treat the data API as a swappable provider, so moving between providers is largely a configuration change. Nexus ships as a provider in MeshJS: NexusProvider is part of @meshsdk/provider , so a Mesh app can switch to it the same way it would switch to any other provider. Its Lucid Evolution provider is an open pull request upstream. For code outside those libraries, Nexus exposes a Blockfrost-compatible surface , so existing Blockfrost SDK code keeps working when pointed at Nexus, and it ships an official TypeScript SDK, @adlabs/nexus , alongside plain REST with an OpenAPI spec. ### Where Nexus fits Against that map, the gap is visible. The established Cardano providers each serve part of the stack, but a product that needs on-chain data and market data and wallet P&L and transaction building and streaming has historically had to assemble them from several vendors. Nexus closes exactly that gap: the full stack under one subscription. Alongside the on-chain data layer it offers: - Market data across all 11 Cardano DEXes: prices, OHLCV candles, order books, pool liquidity and NFT sales. - Wallet analytics with FIFO-based profit and loss, including multi-wallet aggregation. - A transaction builder covering six operation families, from transfers and delegation to Conway-era governance, returning unsigned CBOR with no private keys on its servers. - A DEX aggregator that routes swaps from quote to submission. - WebSocket streaming for live prices, swaps and events. - An MCP server , so Claude and other AI agents can call Nexus data and tools directly. It is also multi-chain in the UTXO sense. Bitcoin (including ordinals and runes) and Midnight are live alongside Cardano, on one account and one base URL. Each API key is scoped to one chain and one network, which is a deliberate safety decision: a leaked testnet key cannot touch mainnet. #### Built by the team behind GeroWallet Nexus is built and run by A.D. Labs, the team behind GeroWallet, the non-custodial Cardano and Midnight wallet. It is not a side project for the wallet: it is what the wallet runs on. GeroWallet's swap routing quotes and builds every swap through the Nexus swap API, its Market tab reads prices, candles and order books from the same Nexus feed you get on a Cardano key, and its transfers and swaps are built server-side by the Nexus transaction builder. That matters when you pick a data layer. The endpoints you integrate are the ones a production wallet depends on every day, so breakage is noticed and fixed by the people who built them. Nexus also works with partners across the ecosystem, including FluidTokens, BloxBean, SongMarketCap and the Cardano Foundation, and publishes a public status page with per-service health and incident history. #### Pricing you can forecast The pricing follows the flat-tier model described above. Plans start at $9 per month for the core API (Starter), and Builder at $29 comes with a 7-day trial and unlocks add-ons such as market data and wallet analytics. From there it runs through Growth at $79, Scale at $199 and Enterprise at $499, which bundles every add-on. There is no overage billing, no compute units and no per-method credits, so you can forecast next month's bill before you write a line of code. For teams with production or compliance requirements, Dedicated (from $2,000 per month) adds isolated infrastructure and a contractual SLA. ### Frequently asked questions Which Cardano API provider is best for production apps? It depends on what the app needs. For chain reads alone, Blockfrost, Koios and Nexus all work. For a product that also needs prices, P&L, transaction building or live data, Nexus covers that full stack, and it already runs GeroWallet in production. How is Nexus priced? Flat monthly plans: Starter at $9 for the core API, Builder at $29 with a 7-day trial and add-ons, then Growth, Scale and Enterprise. There is no overage billing and no compute credits. Which Cardano API providers offer market data? Of the three main hosted options, only Nexus, across all 11 Cardano DEXes. Blockfrost and Koios are chain-data APIs and do not serve prices, candles or order books. What happened to Maestro's Cardano API? Maestro announced on 18 August 2026 that its developer API would retire on 18 September 2026, and it has now shut down. Teams that used it need to move to another provider, and the Maestro alternatives guide covers the mapping. Do I need a provider with an SLA? Only if you have uptime obligations of your own. Hobby projects and prototypes run well on best-effort services. A product with paying customers usually needs a contract behind its data layer. Can I switch Cardano API providers later? Usually, yes. In MeshJS, Blockfrost, Koios and Nexus are all available as providers, so switching is a configuration change. Elsewhere, moving to Nexus is a REST integration, made shorter by its Blockfrost-compatible surface. ### Get started The most direct way to evaluate any of these capabilities is to try them on your own data. The 7-day Builder trial gives you a Nexus API key against the real product, the same one GeroWallet runs on, so you can validate data quality and latency in your own environment before committing any budget. Start the 7-day Builder trial , or read the API overview and the docs first. ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # Bitcoin Runes & Ordinals API: Balances, Inscriptions, UTXOs URL: https://nexus.gerowallet.io/blog/bitcoin-runes-ordinals-api/ Description: Read Bitcoin runes balances, ordinals inscriptions and inscription-aware UTXOs through an API, with endpoint examples and how to avoid burning assets. Blog · Updated November 6, 2026 ## Bitcoin Runes and Ordinals API: Inscriptions, Rune Balances and Safe UTXOs Ordinals and runes turned Bitcoin UTXOs into carriers of assets. An inscription lives on a specific satoshi. A rune balance lives on a specific output. For anyone building a wallet, marketplace, portfolio tracker or exchange integration, that changes what "read the balance" means. You now need to know not only how many sats an address holds, but which outputs carry inscriptions or runes and must not be spent by accident. This guide explains what a runes and ordinals API needs to return, the endpoints you will call most, and the UTXO handling mistake that quietly destroys user assets. ### Who needs a runes and ordinals API - Wallets that show inscriptions and rune balances, and must avoid spending them as fees. - Marketplaces and launchpads that list inscriptions or runes and verify ownership before a trade. - Portfolio and tax tools that value rune holdings and track inscriptions over time. - Exchanges and custodians that credit rune deposits and need to know exactly what arrived in each output. All of them share one requirement: an index that follows the ord protocol rules precisely, since a balance computed with slightly different rules is simply wrong. ### Ordinals and runes in two paragraphs Ordinals number every satoshi in the order it was mined. An inscription attaches content (an image, text, JSON or other data) to one of those satoshis, and the inscription moves with that sat from output to output. Each inscription has an ID made of the reveal transaction ID, the letter i , and an index, for example 6fb9...e9a5i0 , and a sequential inscription number. Runes are fungible tokens recorded with OP_RETURN messages. A rune is etched once, with a name such as UNCOMMON•GOODS , a block:tx ID, a divisibility and optional mint terms. Balances are held by transaction outputs, and transfers move them between outputs according to the runestone in each transaction. ### Three ways to get the data - Run ord yourself. The reference indexer is open source and authoritative. It also needs a full Bitcoin Core node, a large and growing index, and someone to keep both healthy and in sync. - Use a Bitcoin specialist API. Several Bitcoin-focused providers offer ordinals and runes endpoints. Check coverage, rate limits and whether their index tracks the current ord release. - Use a multi-chain UTXO API. If you also build on Cardano or Midnight, one provider for all your UTXO chains means one account, one bill and one set of docs. Whichever you choose, verify three things: that inscription and rune data are returned on the UTXO , not only per address; that the index exposes its sync height so you can tell when it lags the chain tip; and that batch lookups exist, because checking outputs one at a time does not scale. ### The endpoints you will use The examples below use Nexus, the multi-chain data and transaction API from A.D. Labs, which runs Bitcoin Core, electrs and ord through a single endpoint. Requests go to https://nexus.gerowallet.io with a Bitcoin-scoped key in the X-Api-Key header. The paths are representative of what any good runes and ordinals API should offer. #### Everything an address holds curl -H "X-Api-Key: $NEXUS_BTC_KEY" \ "https://nexus.gerowallet.io/api/btc/addresses/$ADDRESS/ordinals" Returns the address with its inscriptions , its outputs , a runesBalances list and its satBalance . Each rune balance carries runeId , name , amount (in raw units), divisibility and symbol . Divide amount by 10 to the power of divisibility to display it. #### Inscriptions held by an address, paged curl -H "X-Api-Key: $NEXUS_BTC_KEY" \ "https://nexus.gerowallet.io/api/btc/addresses/$ADDRESS/inscriptions?limit=25" Each entry has the inscription id , number , satpoint , txid , vout , satOffset , value and genesisHeight . Follow nextCursor for the next page (up to 100 per page). #### One inscription in detail curl -H "X-Api-Key: $NEXUS_BTC_KEY" \ "https://nexus.gerowallet.io/api/btc/ordinals/inscriptions/$INSCRIPTION_ID" Returns the current address , contentType , contentLength , height , timestamp , sat , satpoint , parents , children , charms and, when present, the rune it etched. #### One rune curl -H "X-Api-Key: $NEXUS_BTC_KEY" \ "https://nexus.gerowallet.io/api/btc/ordinals/runes/UNCOMMON%E2%80%A2GOODS" You can pass either the spaced name (URL encoded, the separator is • ) or the block:tx ID. The response includes name , symbol , divisibility , etching , premine , mints , burned , mintable , turbo and the mint terms . #### What sits on a specific output curl -H "X-Api-Key: $NEXUS_BTC_KEY" \ "https://nexus.gerowallet.io/api/btc/ordinals/outputs/$TXID:$VOUT" For many outputs at once, POST /api/btc/ordinals/outputs accepts up to 250 outpoints and returns each one's value , spent , confirmations , inscriptions and runes . ### The mistake that burns inscriptions A standard Bitcoin wallet picks UTXOs by value. It sees a 546 sat output and a 10,000 sat output and happily spends either one to cover a payment or a fee. If that 546 sat output carries an inscription, the inscription is sent to the recipient or, worse, given to a miner as fee. If an output carrying runes is spent without a runestone, its runes move to the first non- OP_RETURN output, which may be the payment recipient. If the runestone is malformed, the runes are burned. The fix is to make coin selection asset-aware. Fetch UTXOs with their ordinals data attached and exclude any output that carries an inscription or a rune balance, unless the user is deliberately sending that asset: curl -H "X-Api-Key: $NEXUS_BTC_KEY" \ "https://nexus.gerowallet.io/api/btc/addresses/$ADDRESS/utxos/page?includeOrdinals=true&limit=100" With includeOrdinals=true , each UTXO includes ordinalsIndexed , an inscriptions array and a runes array. A safe selection rule is short: const spendable = utxos.filter( (u) => u.ordinalsIndexed && u.inscriptions.length === 0 && u.runes.length === 0 ); Note the ordinalsIndexed check. If the ord index has not yet processed an output, treat it as unsafe rather than empty. That single condition is the difference between a cautious wallet and one that loses assets during index lag. The response also returns the chain tip , so you can show users when data is a block or two behind. ### Fees, broadcast and the rest of the stack Asset-aware wallets need the ordinary Bitcoin endpoints too: - GET /api/btc/fees for fee estimates, and GET /api/btc/mempool for mempool state. - GET /api/btc/addresses/{address}/balance and /txs for balances and paged history. - GET /api/btc/blocks and GET /api/btc/chain/tip for chain state. - POST /api/btc/txs/submit with {"rawTxHex": "..."} to broadcast a transaction you built and signed client side. Nexus does not construct Bitcoin transactions server side. You build and sign them in your own code or with a library such as bitcoinjs-lib, then submit through the API. ### Where Nexus fits Nexus is built for teams that work on more than one UTXO chain. The same account that serves Bitcoin addresses, fees, mempool, ordinals inscriptions and runes also serves Cardano, with the deepest coverage there (DEX market data, wallet P&L, transaction building and streaming), and Midnight. API keys are scoped to one chain and one network, so a Bitcoin key and a Cardano key sit side by side under one subscription and one bill. Pricing is flat and published: Starter is $9 a month for the core API, Builder $29 with a 7-day trial, then Growth $79, Scale $199 and Enterprise $499. There is no credit multiplier for heavier endpoints. Component health for bitcoind, electrs and ord is visible on the public status page . To be precise about the limits: there is currently no endpoint that lists every holder of a rune, and no endpoint that lists or searches all runes. Lookups are by address, by output, by inscription ID and by rune name or ID. For a broader view of Bitcoin data needs beyond ordinals, read Bitcoin Data Infrastructure: What Your App Actually Needs . If you are moving off a retired provider, Maestro Alternatives for Bitcoin and Cardano includes an endpoint migration map. ### Common questions How do I display a rune amount correctly? APIs return rune amounts in raw units. Divide by 10 to the power of the rune's divisibility . A balance of 150000 for a rune with divisibility 2 is 1,500.00. Can I look up a rune by name? Yes. Use the spaced name with the • separator, URL encoded, or the block:tx rune ID. Names are uppercase. Why does a fresh UTXO show ordinalsIndexed: false ? The ord index processes each block after it is confirmed. Until it does, the API cannot say whether that output carries assets, so your wallet should not spend it. Does this work on testnet? Bitcoin keys are scoped to a network. Nexus supports Bitcoin mainnet and testnet4. ### Get started To try these endpoints against your own addresses, start the 7-day Builder trial , create a Bitcoin key, and follow the Quick Start . ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # TapTools API Alternative for Cardano Market Data (2026) URL: https://nexus.gerowallet.io/blog/taptools-api-alternative/ Description: TapTools wound down and its API is offline. Compare the options for Cardano token prices, OHLCV candles, DEX pools and NFT sales, with a migration map. Comparison · Updated October 19, 2026 ## TapTools API Alternative: Cardano Market Data After the Wind-Down On 2 June 2026 TapTools announced that it would wind down operations over the following two weeks, citing the departure of its founders and rising infrastructure costs ( The Block ). For four years it had been the default place Cardano developers went for token prices, charts and NFT data. As of October 2026 its API host no longer resolves and the main site shows only an "Under construction" notice. If your wallet, dashboard, bot or tax tool called the TapTools API, you have probably already patched around the gap. This guide is for replacing that patch with something you can run in production: what the realistic options are, what each one actually covers, and how TapTools-style requests map onto a supported API. ### TL;DR If you need the same kind of data TapTools served (token prices, candles, market cap, volume, pools and NFT sales) from a commercially supported API, Nexus Market Data is the closest replacement. It indexes 11 Cardano DEXes and adds order books, a DEX aggregator, FIFO wallet P&L and WebSocket streaming on the same subscription. If you only need an ADA reference price, an oracle feed is enough. If you need a one-off analysis rather than a live feed, a SQL warehouse is cheaper. Option | What it covers | Best for | Commercial support | Nexus Market Data (A.D. Labs) | Token prices, OHLCV candles, market cap, FDV, holders count, volume, pools, order books, NFT collections and sales, top traders | Apps that need live DEX-level market data | Yes, flat monthly pricing | Pyth | Oracle reference prices for major assets | On-chain contracts that need a price feed | Yes, oracle network | Dune | Cardano ledger tables in SQL | Research, dashboards, one-off analysis | Yes, but no DEX trade tables for Cardano | Cardanoscan API | Explorer data | Chain lookups with light market fields | Paid tiers, small scale | DexHunter partner API | Quotes and OHLCV | Teams already integrated with DexHunter | Partner terms, not public | Build your own indexer | Whatever you write | Teams for whom market data is the product | Your engineering time | ### What TapTools gave you, and why it is hard to replace TapTools did something unglamorous and difficult: it watched every major Cardano DEX, turned raw swaps and pool states into prices, and kept doing it as each DEX shipped a new contract version. That is the part teams underestimate when they plan to "just index it ourselves". Three things make Cardano market data harder than it looks: - Every DEX is its own contract family. Minswap V1 and V2, SundaeSwap V1 and V3, WingRiders V1 and V2, Splash, VyFi and others each encode pools, orders and fees differently. A price feed has to decode all of them and keep up with upgrades. - A price is a decision, not a number. The same token trades in several pools at different depths. You need a rule for which pool or which weighted average represents "the" price, and a rule for ignoring thin pools that are easy to move. - Candles need history. Live prices are only half the job. Charts, P&L and tax reports need a reliable history of open, high, low, close and volume, backfilled and kept consistent. Any replacement should be judged on those three points, not on whether it returns a number for ADA. ### What to check before you pick a replacement - DEX coverage. List the DEXes your users actually trade on and check each one by name. - Price method. Ask whether the price is last trade, pool spot, or volume or TVL weighted, and whether you can see the per-DEX breakdown. - History depth and resolution. Confirm the candle resolutions and how far back the history goes for the tokens you care about. - Delivery. Polling REST is fine for dashboards. Trading interfaces and alerts usually want a push stream. - Who answers when it breaks. A community dataset with no support path was acceptable when TapTools existed as the fallback. It is less acceptable now. - Price predictability. Credit or compute-unit billing makes a chart-heavy app hard to budget. Flat tiers are easier to forecast. ### The realistic alternatives #### Nexus Market Data Nexus is the full-stack data and transaction API for UTXO chains, built by A.D. Labs, the team behind GeroWallet. The Market Data add-on covers 11 Cardano DEXes, including Minswap, SundaeSwap, WingRiders, Splash, VyFi, TeddySwap, MuesliSwap and CSwap. It returns per-token prices in ADA and USD with a volume weighted price, TVL, 24 hour volume, price change over 1 hour, 24 hours, 7 days and 30 days, market cap, fully diluted value and holder count. It also serves OHLCV candles, pool reserves, order books, recent swaps, top traders per token, and NFT collection floors and sales. The same subscription can add FIFO wallet P&L, a DEX aggregator with swap quotes and transaction building, and WebSocket streaming, so the pieces teams used to stitch around TapTools sit behind one API surface. The same account also covers Bitcoin and Midnight. Cardano has the deepest coverage. #### Pyth Pyth gives Cardano projects oracle reference prices, and has offered a free one-year Pro key to Cardano projects since June 2026. It is the right tool when a smart contract needs a signed price for a major asset. It does not index Cardano DEX pools, so long-tail native tokens, pool data and NFT sales are out of scope. #### Dune Dune added Cardano tables in April 2026. It is excellent for SQL research and dashboards at the ledger level. It does not currently provide decoded DEX trade tables for Cardano, so you would be reconstructing prices yourself, and it is a query engine rather than a low-latency API for an app. #### Cardanoscan and other explorers Explorer APIs are useful for chain lookups and some token fields. They are not built as a multi-DEX market feed, and their published plans top out at small scale. #### DexHunter DexHunter runs an aggregator with its own quotes and charts and offers a partner API on undisclosed terms. If you are already a DexHunter partner it is worth asking about. It is not a public, self-serve market data product. #### Building your own Teams with a dedicated data function can index DEX contracts directly from a node using open tools such as Oura or Kupo. Budget for decoding every DEX version, choosing a pricing rule, backfilling history and running it all around the clock. This is what TapTools found expensive, by its own account. ### Migration map: TapTools-style requests to Nexus The table maps the kinds of requests most TapTools integrations made onto Nexus endpoints. All Nexus requests go to https://nexus.gerowallet.io with your key in the X-Api-Key header. The market endpoints sit behind the Market Data add-on. What you used TapTools for | Nexus endpoint | Current price of a token | GET /api/market/prices/{assetId} | Price of a token on every DEX | GET /api/market/prices/{assetId}/all | Prices for all tracked tokens | GET /api/market/prices | ADA price | GET /api/market/ada | Top tokens by volume | GET /api/market/prices/top-volume?limit=10 | Top tokens by TVL | GET /api/market/prices/top-tvl | Token metadata | GET /api/market/tokens/{assetId}/metadata | Price history | GET /api/market/history/{assetId}?from=&to= | OHLCV candles for a token | GET /api/prices/historical/candles?assetId=&resolution=1h&from=&to= | ADA candles in USD | GET /api/prices/ada/candles?currency=usd&resolution=1h | Pools for a token | GET /api/dex/pools/token/{policyId}/{assetName} | Order book depth | GET /api/dex/orderbook/{poolId}?levels=10 | Recent swaps for a token | GET /api/dex/swaps/token/{policyId}/{assetName} | Top traders of a token | GET /api/dex/tokens/{policyId}/{assetName}/top-traders | NFT collection floor | GET /api/nft/collection/{policyId}/floor | NFT sales | GET /api/nft/collection/{policyId}/sales?limit=20 | Wallet portfolio and P&L | GET /api/wallet/{stakeAddress}/holdings , GET /api/wallet/{stakeAddress}/pnl (Wallet Analytics add-on) | A first call looks like this: curl -H "X-Api-Key: $NEXUS_API_KEY" \ "https://nexus.gerowallet.io/api/market/prices/$ASSET_ID" The response carries priceAda , priceUsd , weightedPriceAda , tvl , volume24h , priceChange24h , marketCap , fdv and holders , among other fields. Field names differ from what TapTools returned, so plan a small mapping layer rather than a find and replace. If you polled TapTools every few seconds for a trading screen, consider the WebSocket instead. Nexus pushes price updates every 10 seconds on /topic/market/prices and per token on /topic/market/prices/{assetId} , which removes most of the polling traffic. The Cardano WebSocket API guide walks through the connection. ### What Nexus does not do Being specific here saves you a surprise later: - It is a paid service. Starter is $9 a month for the core API; Builder is $29 a month after a 7-day trial, and Market Data is a paid add-on on top (add-ons start at Builder). - There is no free-text token search endpoint. You list tracked tokens with GET /api/market/tokens and look up by asset ID. - Holder counts are returned per token, but there is no endpoint that lists every holder address. - Market data covers Cardano. Bitcoin and Midnight are live on Nexus for chain data and transactions, not DEX market data. ### Pricing Nexus uses flat monthly tiers. Starter is $9 a month (3M requests, core API only), Builder $29 (7-day trial, 10M requests), Growth $79 (30M), Scale $199 and Enterprise $499. Market Data is $19 a month as an add-on, and add-ons start at Builder, so the smallest production setup for a TapTools replacement is $48 a month. Wallet Analytics is $15 and WebSocket packages start at $29. Enterprise bundles every add-on and unlimited WebSocket streaming. Every price is on the pricing page before you sign up, with no credit multipliers. ### Common questions Is TapTools coming back? TapTools said in June 2026 that it was open to acquisition or other arrangements. As of 15 October 2026 its API host does not resolve and its site shows "Under construction". Build on the assumption that the old API will not return, and treat any relaunch as a bonus. Can I keep my TapTools response format? Not directly. The concepts map closely, but field names and some units differ, so write a thin adapter in your backend. That also makes the next vendor change, if there ever is one, a one-file job. Which DEXes does Nexus price? Eleven Cardano DEXes, including Minswap V1 and V2, SundaeSwap V1 and V3, WingRiders V1 and V2, Splash, VyFi, TeddySwap, MuesliSwap and CSwap. Check the Market Data guide for the current list before you rely on a specific venue. Do I need a Cardano node or chain data provider as well? Not for market data. If your app also reads UTxOs, builds transactions or submits them, those are on the same Nexus account. The Cardano API providers comparison covers the chain data side. ### Next step Losing a data vendor you did not choose to leave is a good moment to put the replacement behind an adapter and test it against real traffic before you depend on it. List the TapTools calls your code made, map them with the table above, and run the new feed beside your current workaround for a week. To do that now, start the 7-day Builder trial , add Market Data, and follow the Quick Start . ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # Get a Cardano API Key: Signup to First Call | Nexus URL: https://nexus.gerowallet.io/blog/cardano-api-onboarding-signup-to-first-call/ Description: What onboarding to a Cardano data API involves, what to evaluate before you commit, and the exact steps from Nexus signup to your first authenticated call. Blog · Updated November 3, 2026 ## Onboarding to a Cardano Data API: From Signup to First Call ### What "onboarding" actually means for a blockchain data API Every hosted data API puts the same four gates between you and your first byte of chain data: create an account, pick a plan, get a credential, make an authenticated request. The gates are universal. What differs between providers, and what actually decides how long onboarding takes, is what each gate demands of you and how much you can learn before you walk through it. This matters most to the teams who evaluate tools hands-on before committing budget: dApp and DeFi builders wiring up token prices or wallet history for the first time, and engineering teams moving a product from testnet to mainnet who need a production-grade data layer under it. For them, time-to-first-call is not a vanity metric. It is the cost of finding out whether a provider fits at all. ### TL;DR Getting a Cardano API key takes minutes at any serious provider. What differs is what you learn on the way. Check four things: whether the docs are public before signup, what the plan gate costs you, how keys are scoped, and what the first response tells you about limits and errors. With Nexus the flow is verify your email, start the 7-day Builder trial, create a key in the dashboard, and send one request with an X-Api-Key header. Gate | What to check | Nexus | Docs | Public before signup, full spec, playground | Public, OpenAPI 3.1, live playground | Plan | Free plan or trial, and what the trial exposes | No free plan. Starter $9/month (core API only, no trial); 7-day trial on Builder, $29/month | Credentials | Auth mechanism, key scope, issuance speed | X-Api-Key header, one chain and one network per key, instant | First call | Rate-limit headers, distinguishable errors | X-RateLimit-* headers, separate 429 cases, 402 for add-ons | Where Nexus fits: one account and one base URL across Cardano, Bitcoin and Midnight, with an official TypeScript SDK and a Blockfrost-compatible surface for teams that are migrating. ### The four gates, and what to check at each one #### Gate 1: Can you read the docs before you sign up? The cheapest evaluation is the one that needs no account. A provider that publishes its full endpoint reference publicly lets you answer the fit question, "does this API even return the data my product needs?", before you type an email address. Look for a complete OpenAPI spec rather than curated highlights, and ideally an interactive playground where you can see request and response shapes. Most serious providers clear this bar. Blockfrost publishes its OpenAPI spec on GitHub and it has become the closest thing Cardano has to a de facto data standard. Koios documents its community-run API publicly. If a provider makes you sign up to see what the API returns, treat that as signal. #### Gate 2: What does the plan gate cost you? Providers split into two camps here. Some offer a permanent free plan: Blockfrost's Starter plan gives 50,000 requests per day at no cost, with no card, which is genuinely useful for hobby projects and long-running experiments. Others gate access behind a paid plan with a trial window, which trades away the permanent free home for full access to the paid surface during evaluation. Neither model is better in the abstract. A free plan suits open-ended tinkering. A trial suits a scoped evaluation: you know what you need to test, you test it against the real paid product, and you decide. What you should check is whether the trial exposes the capabilities you are actually buying, or a reduced version of them. #### Gate 3: How do credentials and auth work? Three questions decide how much integration friction the credential model adds: - What is the auth mechanism? A single HTTP header is the least friction: no SDK required, every language's standard HTTP client works, and a curl one-liner proves the key is live. - What is the key scoped to? Some providers scope credentials per project, some per chain and network. Scoping affects how many credentials you manage as you grow, but a narrower scope also means a leaked mainnet key cannot touch anything else. Know the model before you design your config. - How fast is issuance? Key creation should be self-serve and instant from a dashboard, not a request to a sales team. If issuance involves a human, you are not onboarding to an API, you are onboarding to a vendor relationship. That is sometimes what enterprises want, but it should be a choice, not a surprise. #### Gate 4: What does the first request teach you? The first authenticated call is where the product starts telling you the truth about itself. Two things worth reading closely in that first response: - Rate-limit visibility. Does the API tell you where you stand? Headers like X-RateLimit-Remaining on every response mean you can monitor quota programmatically from day one instead of discovering limits by hitting them. - Error taxonomy. A provider that distinguishes "you are sending too fast" from "your monthly quota is exhausted" from "this capability is not on your plan", with different status codes and machine-readable bodies, is a provider you can build automated handling against. One that returns a generic 429 for everything leaves you guessing in production. An evaluation that stops at "the key works" wastes the window. Point real traffic at the API: your query patterns, your peak request rates, your chained-transaction flows if you have them. Onboarding is fast everywhere the day nothing is wrong. What you are evaluating is what the API tells you when something is. ### Where Nexus fits: the actual walk-through Nexus is the full-stack data and transaction API for UTXO chains, built by Gero Labs: on-chain reads, market data across 11 Cardano DEXes, FIFO wallet P&L, server-side transaction building, and WebSocket streaming behind one REST surface, with Cardano, Bitcoin, and Midnight live today. Here is exactly what its four gates look like, stated plainly so you can hold us to it. Before signup: the docs are public. The full endpoint reference, close to 200 endpoints on an OpenAPI 3.1 spec, is browsable with a live playground at nexus.gerowallet.io/docs . You can settle the fit question without an account. Step 1: Create an account and verify your email at nexus.gerowallet.io . Step 2: Choose a plan. Builder ($29/month) opens with a 7-day trial that exposes the full API surface; Starter ($9/month) is the core API without add-ons or a trial. To be direct about the mechanics, because trial fine print is where onboarding friction likes to hide: there is no free plan, adding a payment method is what starts the trial and unlocks key creation, and if you cancel before day 7 you pay nothing. You are evaluating the real paid product, not a demo of it. Step 3: Create an API key from the dashboard. Issuance is self-serve and immediate. Each key is scoped to one chain and one network (a Cardano mainnet key is not a preprod key), and Builder includes 4 keys, so you can separate environments from the start. Keys start with nxs_ and are shown once, so store yours when you create it. Keys survive the trial-to-paid transition; nothing gets re-issued or breaks on day 8. Step 4: Make the first call. The whole protocol is HTTPS plus an X-Api-Key header. No SDK is required and there is nothing else to install: curl -H "X-Api-Key: nxs_your_api_key_here" \ https://nexus.gerowallet.io/api/blocks/latest One mistake is worth avoiding on the first try. The key goes in the X-Api-Key header. Putting it in Authorization: Bearer returns 401, because that header is reserved for dashboard session tokens. That is the full flow: verify, subscribe, create a key, curl. The only waiting is the email verification. Watch it live: Adam Cazes, co-founder and CEO of A.D. Labs, walks through the Nexus dashboard, API keys, the playground and a live WebSocket subscription at Cardano Developer Office Hours . On the gate-4 questions, Nexus is built to be measured. Every metered response carries X-RateLimit-Limit , X-RateLimit-Remaining , and X-RateLimit-Reset headers. The two 429 cases are distinguishable (the monthly-quota one carries the quota headers and a reset_at body; the per-second one sends Retry-After: 1 ), and plan gating uses HTTP 402 with a machine-readable addon field. Builder meters at 2 million requests per month and 25 requests per second with a 250-token burst, and there is no overage billing: at the cap the API returns 429 until you upgrade, so the bill you modeled is the bill you get. ### SDKs and migration paths You do not need an SDK, but there is one. Nexus ships an official TypeScript client, @adlabs/nexus , installed with npm install @adlabs/nexus . Every other language works over plain REST, and the OpenAPI spec generates typed clients if you want them. If your consumer is an AI agent, the MCP server is the third route. Arriving from Blockfrost. The same Nexus key works as a project_id against the Blockfrost-compatible surface , so existing Blockfrost SDK code is the shortest path in. Arriving from Maestro. Maestro announced on 18 August 2026 that its developer API retires on 18 September 2026. The Cardano migration reference maps its endpoints to Nexus routes, and the Maestro alternatives guide covers the decision. Two honest caveats so the picture is complete. Native providers for MeshJS and Lucid Evolution are not released yet. The Lucid Evolution provider is an open pull request upstream, so today you integrate through the SDK, the REST spec or the Blockfrost-compatible surface. And if your workload is pure on-chain reads with no market data, P&L, transaction building, or streaming, a cheaper single-purpose provider may fit better; the walk-through above only pays off if you need the stack it unlocks. ### Related reading - Nexus vs Blockfrost - Nexus vs Koios - Maestro alternatives for Bitcoin and Cardano - Inside the Nexus API ### Try the four gates yourself The fastest way to test everything this article claims is to run the gates against your own workload. Browse the full endpoint reference and live playground at nexus.gerowallet.io/docs , then start the 7-day Builder trial at nexus.gerowallet.io and point a week of real traffic at it. For Dedicated infrastructure, custom SLAs, or compliance documentation, reach the team through the support page . ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # Nexus vs Koios: Cardano API Comparison URL: https://nexus.gerowallet.io/blog/nexus-vs-koios/ Description: Nexus vs Koios, compared by engineers who run both: query model, cluster architecture, tiers, timeouts, SLAs and price. Re-verified September 2026. Comparison · Updated October 19, 2026 ## Nexus vs Koios: Managed Full-Stack API or Community-Run Endpoint? ### Nexus or Koios for your Cardano data layer? Full disclosure before anything else: we know Koios well because we use it. Koios is one of the fallback providers in Nexus's own Cardano read path, and Gero Labs appears on Koios's community page among the projects building on it. So this is not a takedown of a competitor; it is an engineering comparison between two deliberately different models, written by a team that runs against both. Koios is an open-source, DAO-governed, community-operated data layer that sets the price floor of the entire Cardano API market. Nexus is a managed commercial platform that covers the same on-chain layer and then a lot of surface Koios intentionally does not attempt. The decision between them is rarely about quality. It is about which failure modes, cost structures, and scopes fit your product. Everything below was verified against primary sources in July 2026 and re-checked at the end of September 2026. Koios is in an actively good state: spec v1.4.2, shipped on 2026-07-14, is still the current release, and the repositories show commits as recently as September 2026. The timing matters. Maestro announced on 18 August 2026 that its developer API retires on 18 September 2026, which leaves Blockfrost, Koios and Nexus as the practical shortlist for a hosted Cardano data layer. If you are arriving from Maestro, the Maestro alternatives guide covers the migration itself; this page is about the choice between two of the three. ### TL;DR Koios and Nexus overlap on chain data and diverge on everything else. Koios is the cheapest serious source of Cardano chain data, open source and community-run, with no SLA at any price and payment in ADA only. Nexus is a managed commercial API that covers the same chain data and adds market data, wallet P&L, transaction building, swap routing and streaming, with invoices and a contractual SLA on its Dedicated tier. Pick on scope and accountability, because on price per chain read Koios wins. | Koios | Nexus | Model | Open source, DAO-governed, community-operated | Managed commercial service | Entry price | $0 (5,000 requests/day, no key) | $9/month Starter (core API only); Builder $29/month with a 7-day trial | Paid tiers | ~$29.99 and ~$74.99/month, paid in ADA | $79, $199, $499/month, card and invoice | Chain data | Yes, about 102 endpoints | Yes, about 70 endpoints | Conway governance | 15 current endpoints, the broadest available | 13 governance and DRep endpoints | Market data, wallet P&L | No | Yes, as add-ons | Transaction building | No, submission of signed CBOR only | Yes, 6 builders returning unsigned CBOR | Streaming | No | Yes, WebSocket | SLA | None, at any tier | Contractual on Dedicated | Other chains | Cardano only | Bitcoin, Midnight, Apex Fusion | Rule of thumb: if your workload is chain reads and cost is the constraint, use Koios. If your product needs prices, P&L, transaction construction, streaming, or a contract behind its data layer, that is what Nexus sells. Where Nexus fits: one account and one base URL across Cardano, Bitcoin and Midnight, flat monthly pricing from $9, with a 7-day trial on Builder, and the layers above chain data that Koios deliberately leaves out. ### Two architectures, honestly described Koios is a federation. Each instance runs the guild-operators stack: cardano-node, cardano-db-sync into PostgreSQL, Koios's own SQL normalization and cache layer (all MIT-licensed, every query public ), PostgREST to expose it, and HAProxy in front. Independent community operators (the project commits to at least four trusted mainnet instances; Eternl, NMKR, VESPR, and TosiDrop run their own) register into a monitoring and proxy layer that does DNS-based load balancing, health checks that verify instances are serving tip-synchronized data, DDoS protection, and tier enforcement via JWT. There are at least two DNS entrypoints to avoid a single point of failure, and you can bypass the cluster entirely and hit an instance directly. Governance is a DAO grown out of the Guild Operators group, with five named core maintainers. Two engineering consequences of that design worth knowing before you build on it. First, reads are served by whichever healthy instance the proxy picks, so Koios documents that paginated queries should always pass an explicit order parameter, or sort can differ between pages served by different backends. Second, accountability is structural, not contractual: health checks and failover are real and well-built, but nobody owes you anything (more on the terms below). Nexus is a managed service: a Java 21 / Spring Boot API in front of a prioritized provider chain per network, with Nexus's self-hosted yaci-store indexers as the primary read path and Koios and Blockfrost as circuit-breakered fallbacks. Health checking includes a tip-staleness test that routes around an indexer that is alive but serving stale data. Above the chain-data layer sit the in-house market-data indexer, the analytics engine, the transaction builder, the DEX aggregator, and the WebSocket broadcaster. One operator, one bill, one accountable counterparty. Koios's model gives you transparency and exit; you can setup-grest.sh a bit-identical private instance and your client code does not change. Nexus's model gives you accountability and scope. Those are genuinely different virtues. ### API surface Koios ( api.koios.rest , base https://api.koios.rest/api/v1 , plus preprod and preview hosts) documents about 102 endpoints (roughly 91 once you exclude the 11 deprecated-but-still-served ones): network and epoch state, blocks, transactions (including CBOR fetch and submission of signed transactions), addresses and payment credentials, stake accounts (13 endpoints), assets (13), pools (a deep group of 16, down to per-epoch delegator history), scripts and datums, an Ogmios HTTP passthrough, and a genuinely excellent Conway governance group: 15 current endpoints (18 counting deprecated ones) covering DReps (list, info, metadata, updates, voting-power history, delegators), the committee, proposals, per-proposal voting summaries, vote lists, and pool voting-power history, with correctness fixes as recent as v1.4.2. The query model is PostgREST, and for batch-heavy consumers it is a real feature: vertical filtering with ?select= , horizontal filtering with PostgreSQL operators ( ?pool=eq.pool1... ), CSV output via the Accept header, offset/limit pagination with Content-Range (1,000 rows per page), and bulk POST bodies (send 25 tx hashes in one call). Koios itself calls bulk queries its major differentiator, and it is right. The cap to know: request bodies are limited to 1 KB on the public tier and 5 KB registered, and blowing it returns a 413 (documented as of v1.4.2 after users hit it at around 100 IDs per call). What Koios deliberately does not have, confirmed against the full spec: no market, price, or DEX data of any kind; no P&L or portfolio analytics; no transaction building (submission of signed CBOR only); no WebSockets, webhooks, or streaming. Koios competes on chain data and price, not breadth. That is a design choice, not a failure. Nexus covers the same on-chain layer with about 70 Cardano chain-data endpoints (accounts, addresses, assets, blocks, epochs, pools, scripts, datums, submit, evaluate, batch CBOR) and then the layers above it: roughly 54 market-data endpoints (current and historical prices, OHLCV candles at 15m/1h/1D/1W, RSI(14), real and AMM-simulated order books, pool TVL and reserves, recent swaps, top traders, NFT floors and sales) aggregated across venues spanning 15 routable DEX integrations (live-verified September 2026: Minswap V1/V2, SundaeSwap V1/V3, WingRiders V1/V2, VyFi, Splash, TeddySwap, MuesliSwap, CSwap, Genius Yield, SaturnSwap, ShadowBook, SnekFun); FIFO wallet P&L including multi-wallet aggregation in one POST; a 6-operation transaction builder returning unsigned CBOR (transfers, delegation, stake registration with optional reward withdrawal, DRep registration, vote delegation with Trezor-compatible certificates, withdrawals) signed client-side via CIP-30; a DEX aggregator from quote to co-signed submission at a 0.10% fee (0.05% for GERO holders); SockJS/STOMP WebSocket streaming with snapshot-then-update semantics; 13 governance and DRep endpoints; a hosted MCP server with 25 tools; and live Bitcoin (including ordinals and runes), Midnight (including DUST and transaction building), and Apex Fusion networks, with keys scoped per chain and network. On governance specifically, credit where due: Koios's governance group is still broader than Nexus's today. If your product is a governance explorer, Koios is arguably the best free source on the market. ### Tiers, limits, and the fine print Koios's tiers , as we last verified them in July 2026. Check the live page before you budget against it: | Public | Free | Pro | Premium | Custom | Price | $0, no key | $0, key required | ~$29.99/mo | ~$74.99/mo | negotiable | Requests/day | 5,000 | 50,000 | 500,000 | 1,200,000 | "unlimited" | Rate limit | 100 per 10s | 100 per 10s | 250 per 10s | 500 per 10s | negotiable | Query timeout | 30s | 30s | 60s | 120s | negotiable | CORS | restricted | open | open | open | open | Details that matter in production: quotas are counted separately for mainnet versus testnets; queries that exceed the timeout return 504 (so the free tiers effectively cannot run the heaviest queries at all, which Koios documents rather than hides); more than 100 requests per endpoint per 10 seconds from one IP triggers a 60-second 429 sleep; and CORS being restricted on the Public tier means browser-side dApps need at least a registered key. The payment and legal mechanics are unusual and deserve plain statement. All payments are in ADA, via a CIP-30 wallet-signed flow on the Koios site; there is no fiat option, no invoices (the DAO "is not a legal entity" per its own terms ), and no refunds. And there is no SLA at any price point, including Premium: the terms state that Koios does not guarantee any specific service level or uninterrupted operation and encourage users to implement their own redundancy. For a hobbyist, none of this matters. For a company whose accountant needs a VAT invoice or whose customers have uptime obligations, each item is a procurement conversation. Nexus tiers : Starter $9/month (3M requests/month, 10 req/s with a 100-token burst, 2 keys, core API only, no add-ons, no trial), Builder $29/month (10M, 25/250, 4 keys, 7-day trial; there is no free tier), Growth $79 (30M, 50/500, 7 keys), Scale $199 (50M, 100/1,000, 13 keys, streaming included), Enterprise $499 (200M, 500/5,000, unlimited keys, all add-ons and unlimited WebSocket bundled), Dedicated from $2,000 (physically isolated infrastructure, negotiated contractual SLA, 4-hour support response). Add-ons: Market Data $19, Wallet Analytics $15, Transaction Builder $19, MCP $19, IPFS $5; WebSocket packages $29/$59/$99 on Builder and Growth. Metering is dual (monthly pool plus per-second token bucket), quota state comes back in X-RateLimit-* headers, add-on gating is a machine-readable 402, and there is no overage billing: the cap is a hard 429 until you upgrade. Billing is conventional (PayPal rails, card-friendly, invoices exist), which is precisely the boring property some finance departments require. On raw price per on-chain request, Koios wins and it is not close: 500k requests per day for ~$30 versus 10M per month for $29 (or 3M for $9 on Starter). If your workload is chain reads and fits Koios's timeouts and limits, Koios is the rational choice, and we say that as a paying-attention competitor. The Nexus $29 buys a different thing: a smaller pool of requests against a much larger surface, plus a commercial counterparty. The comparison is scope and accountability, not volume. ### Reliability Koios's reliability engineering is better than "community-run" might suggest: health-checked failover across independent instances, tip-synchronization checks, DDoS protection, and a public track record of steady releases (v1.4.0 in March 2026, v1.4.2 in July 2026). But its documented operating envelope is real: 504s on long queries by design, the anti-DoS 429 sleep, 413s on oversized bulk bodies, no public status page we could find, and the no-SLA terms quoted above. The honest summary is best-effort infrastructure run by competent people who explicitly tell you to bring your own redundancy. Nexus is managed infrastructure with the redundancy built in (the provider chain and tip-staleness routing described earlier) and contracts where contracts belong: Dedicated carries a contractual SLA, isolated infrastructure and a 4-hour response channel. Nexus publishes a public status page with per-service uptime and incident history. It does not yet publish a third-party uptime figure, and we will not invent one here; the 7-day trial plus the rate-limit headers exist so you can measure behavior against your own workload before paying. ### When Koios is the better fit - Cost-sensitive chain-data workloads. Learning, prototyping, hobby projects, research, indexer backfills: 50k requests/day for free with a key, half a million for ~$30. Unbeatable, full stop. - Batch pipelines that fit the PostgREST model. Column selection, rich filters, CSV out, bulk POSTs: for analytical extraction jobs this query model is genuinely more expressive than a fixed REST surface, Nexus's included. - Governance tooling. The 15-endpoint Conway group is the broadest free governance API on Cardano. - A self-hosting or decentralization mandate. The whole stack is open source and deployable as a bit-identical private instance; there is no vendor to be locked into, structurally. - Paying in ADA is a feature for you (a DAO treasury, say) rather than a procurement problem. ### When Nexus is the better fit - Your product needs anything above on-chain reads. Prices, candles, order books, P&L, transaction construction, swap routing, streaming: none of it exists in Koios, so the real alternative is Koios plus two or three more systems you build and operate. That composite, not Koios itself, is what a Nexus subscription competes with. - You have uptime obligations to your own customers. Best-effort upstream means your reliability ceiling is someone else's volunteer capacity, and Koios's terms say so explicitly. Accountability has to flow downhill through contracts. - Your queries are heavy or your traffic is bursty. Nexus's per-second buckets with defined bursts, monthly (not daily) pools, and absence of query-timeout tiering behave more predictably under production load than a 100-per-10s IP throttle with 30-to-120-second timeout ceilings. - Procurement needs an invoice, a fiat rail, or an SLA. Koios structurally cannot provide any of the three; Nexus provides all of them (the SLA on its Dedicated tier). - You want the multi-chain UTXO surface (Bitcoin, Midnight, Apex Fusion, live today) from the same vendor and docs. ### Bottom line Koios is the best value in Cardano chain data, an exemplary open-source project, and structurally incapable of being your accountable vendor; those are all the same fact viewed from three angles. Nexus overlaps it on the chain-data layer, exceeds it everywhere above that layer, and sells the accountability Koios's model deliberately omits. Plenty of serious teams should choose Koios. The moment your product needs market data, analytics, transaction construction, streaming, or a contract behind your data layer, the comparison stops being close. Evaluate the full surface against your own traffic with the 7-day Builder trial: get a key at nexus.gerowallet.io , browse the live endpoint playground at nexus.gerowallet.io/docs , or contact us about Enterprise and Dedicated via the support page . Still comparing? Read Nexus vs Blockfrost for the other half of the shortlist. ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # Nexus vs Maestro: Cardano Data API Comparison URL: https://nexus.gerowallet.io/blog/nexus-vs-maestro/ Description: A deep technical comparison of Nexus and Maestro: Cardano API surface, credit-based vs flat pricing, reliability data, and the Bitcoin pivot, verified September 2026. Comparison · Updated October 19, 2026 ## Nexus vs Maestro: Cardano-First Data API or Bitcoin-First dApp Platform? ### Nexus or Maestro for your Cardano data layer? Maestro deserves a serious comparison. It is the best-funded API provider in the Cardano ecosystem, its documentation is genuinely excellent, and two of its Cardano products (the Transaction Manager and the Managed Contracts API) have no direct equivalent anywhere, including at Nexus. If your evaluation shortlist is honest, Maestro is on it. But the comparison in September 2026 is not the comparison from a year ago, because Maestro today is visibly two businesses, and the developer platform is not the headline one. This article walks through what that means concretely, then compares the two Cardano API surfaces endpoint group by endpoint group, digs into the pricing models (compute credits versus flat request pools, which is the most consequential technical difference), and looks at measured reliability. All claims were verified against primary sources in July 2026; links inline. ### The strategic picture: where Maestro is investing These are observable facts, not spin, and you can click every one of them. - Maestro's root domain, gomaestro.org , no longer markets the developer platform. It is "Maestro Institutional": a Bitcoin treasury and yield platform for accredited investors (the Mezzamine miner-credit vaults, myBTC, a treasury manager). The developer API business lives one level down at gomaestro.org/developer , and the old pricing URL now 404s. - The funding story points the same direction: the February 2025 $3M seed round , co-led by Draper Associates, was headlined "to Propel the Bitcoin DeFi Revolution." - The company blog's most recent post as of this writing (March 2026) announces Mezzamine, a Bitcoin-native institutional credit market . The September 2025 Maestro Institutional launch post lists the company's track record entirely in Bitcoin protocols and L2 infrastructure. Cardano does not appear. - On the engineering side, Maestro's Cardano changelog tops out at "v1.8.0, Conway compatibility" (the Conway era shipped in 2024), while the Bitcoin changelog shows sustained new-endpoint growth, and the open-source work (the Symphony indexer, the MCP server, the Esplora proxy) is Bitcoin-side. Maestro's own platform matrix still lists Cardano Node RPC, Cardano Mempool Monitoring, and the Cardano Event Manager as "Coming Soon," unchanged for a long time. None of this means Maestro's Cardano API is bad. Its Cardano indexer is up, monitored, and performing (numbers below). It means the roadmap energy is elsewhere, and if you are a Cardano-first team, you should price in what "Coming Soon" has meant so far. Nexus's investment runs the other way: Cardano is the deepest chain on the platform, and the 2026 roadmap work (aggregator venues, governance endpoints, Midnight transaction building, partner widgets) has been shipping continuously on the UTXO side. ### Cardano API surface, group by group Maestro's Cardano offering, from its published OpenAPI specs and docs: - Blockchain Indexer: 58 endpoints (spec v1.8.0): accounts and staking, addresses with batch UTxO lookups and payment-credential queries, asset and policy queries, blocks, datums, ADA Handle resolution, epochs, protocol parameters, stake pools, scripts, and transactions including CBOR fetch and redeemer evaluation. Cursor-based pagination with a next_cursor token, explicitly designed so pages stay duplicate-free while the chain grows. This is a good, modern chain-data API. - Market Price API: 4 endpoints (list DEXes, list pairs, OHLC, trades), gated to the $49 Conductor tier and above. The supported-DEX list is only discoverable through the authenticated endpoint itself; the docs' worked example is Minswap. There are no order-book, TVL/reserves, top-trader, or NFT-market endpoints. - Transaction Manager: 5 endpoints , including Turbo submit (priority propagation) and webhook-driven lifecycle tracking (pending, confirmed, failed, rolled back). This is genuinely differentiated managed infrastructure; nobody else in the Cardano API market runs your transaction's lifecycle for you like this. - Managed Contracts API: about 23 endpoints wrapping pre-deployed, audited Plutus templates: direct swaps, multisig, staking campaigns, subscription payments, vesting. Powerful if a template matches your product; it is not a general-purpose builder. - Governance: zero endpoints. No DRep, proposal, vote, or committee queries anywhere in the Cardano spec. Conway data surfaces only as certificate fields inside transaction details. - Not present on Cardano: node RPC, mempool API, the Event Manager, and the Wallet API (Maestro's wallet endpoints with historical USD balances exist for Bitcoin only ). There is no WebSocket streaming anywhere in the Maestro product; push means webhooks. The Nexus Cardano surface, for the same buckets: about 35 core chain-data endpoints (accounts, addresses, assets, blocks, epochs, pools, scripts, datums, tx submit and evaluate, batch CBOR), roughly 48 market-data endpoints (current and historical prices, OHLCV candles at 15m/1h/1D/1W, RSI(14), real and AMM-simulated order books per pool, pool TVL and reserves, recent swaps, top traders, an LP leaderboard, NFT collections with floor and sales, token metadata), wallet analytics with FIFO P&L (single wallet, or multi-wallet in one POST), a 6-operation transaction builder returning unsigned CBOR (transfers, delegation, stake registration with optional reward withdrawal, DRep registration, vote delegation with Trezor-compatible certificates, withdrawals), a DEX aggregator that quotes and routes across 15 venues (live-verified July 2026 via GET /api/aggregator/supported-dexes : Minswap V1/V2, SundaeSwap V1/V3, WingRiders V1/V2, VyFi, Splash, TeddySwap, MuesliSwap, CSwap, Genius Yield, SaturnSwap, ShadowBook, SnekFun) with non-custodial co-signed submission at a 0.10% fee (0.05% for GERO holders), SockJS/STOMP WebSocket streaming (price topics, per-asset feeds, executed swaps, dApp blueprint events), DRep governance endpoints (list, detail, delegators, votes with proposal context), and a hosted MCP server exposing 25 tools to AI agents. Summarized honestly: Dimension | Maestro (Cardano) | Nexus (Cardano) | Core chain data | 58 endpoints, mature, cursor pagination | ~35 endpoints | Market data | 4 endpoints, OHLC + trades, $49+ only | ~48 endpoints: candles, order books, TVL, NFT, indicators | Wallet P&L analytics | No (Bitcoin only) | Yes, FIFO, multi-wallet | Tx submission | Yes, with managed lifecycle + Turbo | Yes (plain submit + evaluate) | Tx building | Fixed audited templates only | General builders, intent in, unsigned CBOR out | DEX swaps | Via swap template | Aggregator across 15 venues, quote to submit | Governance | None | DReps: list, detail, delegators, votes | Streaming | None (webhooks) | WebSocket (SockJS/STOMP) | Mempool | Coming Soon | No | AI agents | MCP + x402 pay-per-call (Bitcoin-centric) | MCP, 25 tools incl. Cardano tx building | Where Maestro is ahead on Cardano: raw indexer breadth, transaction lifecycle management, audited contract templates, and webhook push. Where Nexus is ahead: everything market-facing, analytics, general transaction construction, swap routing, streaming, and governance reads. ### Pricing models: compute credits versus flat requests This is the most consequential engineering difference between the two, because it changes how you forecast. Maestro ( pricing ) sells compute credits: Artist is free (1M credits/month, 10 req/s, hard-capped), Conductor is $49/month (4M credits, 100 req/s, overage at $2.50 per 100k credits), Virtuoso is $199/month billed yearly or $284 month-to-month (16M credits, 200 req/s, overage at $2.00 per 100k), Enterprise is custom. Each API call burns credits weighted by "the global average duration of that process" per the docs , and the actual per-endpoint credit table is not public; it lives behind the dashboard login. Your remaining allowance comes back in X-Maestro-Credits-Remaining headers (which the docs describe as daily allowances, while plans are sold monthly, a wrinkle to clarify with them if you evaluate). Two new payment rails are worth crediting: subscriptions payable in stablecoins, and x402 keyless pay-per-call, which lets an AI agent buy API access on the fly. That last one is ahead of the whole field, Nexus included. The engineering consequence of credit weighting: your bill is a function of your endpoint mix, not just your call count, and the weights can change with the provider's own measured costs. You cannot compute next month's bill from a traffic forecast without the private weight table; heavy endpoints can dominate spend in ways a request counter never shows. Past the allowance, metered overage kicks in, so a runaway job costs money rather than failing. Nexus sells flat request pools where every request costs exactly one request, on any endpoint: Starter $9/month (3M requests, 10 req/s with 100 burst, 2 keys, core API only, no add-ons), Builder $29/month (10M requests, 25 req/s with 250 burst, 4 keys, 7-day trial; there is no plan at no charge), Growth $79 (30M, 50/500), Scale $199 (50M, 100/1,000, streaming included), Enterprise $499 (200M, 500/5,000, every add-on and unlimited WebSocket bundled), Dedicated from $2,000 (isolated infrastructure, negotiated SLA). Capability add-ons are flat too: Market Data $19, Wallet Analytics $15, Transaction Builder $19, MCP $19, IPFS $5, WebSocket packages $29/$59/$99 on the lower tiers. Quota state is exposed in standard X-RateLimit-* headers, gating is a machine-readable HTTP 402, and there is no overage billing at all: at the cap you get 429s until you upgrade. A runaway job fails loudly instead of costing money. Which failure mode you prefer is a legitimate choice; Nexus picked predictability. A concrete comparison at the $49-to-$106 band: Maestro Conductor at $49 includes market data and 4M credits. Nexus Builder with the Market Data, Wallet Analytics, and Transaction Builder add-ons is $82 ($29 + $19 + $15 + $19) for 10M requests, or Growth fully loaded at $132 for 30M. If your workload is chain reads plus OHLC candles, Conductor is very likely cheaper. If it also involves order books, P&L, swap routing, or streaming, the Maestro side of the ledger needs additional vendors or in-house builds that no longer make $49 the real number. Run your own endpoint mix through both; with Nexus you can do that arithmetic on paper, which is rather the point. ### Reliability: measured, not marketed Maestro operates a public status page with per-component uptime, and deserves credit for it. As of 2026-09-14 it shows five short incidents in the trailing 90 days, the longest a 16-minute Cardano Blockchain Indexer outage on 29 June and the rest between two and five minutes; the Cardano Blockchain Indexer (the only Cardano component monitored) reads 99.986%, Bitcoin components between 99.997% and 100%, and the web properties 100%. That is a good record, stated by the vendor itself, in public. Two footnotes for precision: marketing materials cite 99.993% uptime and 5,000 calls/second per customer (from the institutional launch post ), which is above what the status page itself measures for the API components, and no published SLA percentage or credit terms exist on any self-serve tier; SLA language is Enterprise-custom. Nexus publishes a public status page with per-service uptime and incident history, and a changelog with a 30-day deprecation notice rule. Behind it is architectural redundancy (self-hosted yaci-store indexers as the primary read path with circuit-breakered fallbacks and tip-staleness-aware routing that pulls stale-but-alive indexers out of rotation) and contractual coverage on the tiers built for it: Enterprise and Dedicated carry written SLAs, and Dedicated adds physically isolated infrastructure with a 4-hour support response. Below those tiers, the honest guidance is symmetrical for both vendors: measure during a trial. Both expose enough headers to script the measurement. ### When Maestro is the better fit - Bitcoin is your first chain, or metaprotocols are your product. Maestro's Bitcoin depth (ordinals, runes, BRC-20 indexing, mempool-aware wallet endpoints, Esplora compatibility, plus Dogecoin, Midnight GraphQL, Midl, and Arch) is unmatched in the UTXO API niche, and it is where the company is demonstrably investing. Nexus's 16 Bitcoin endpoints cover addresses, transactions, blocks, fees, mempool, inscriptions, and runes, which is real coverage, but Maestro's Bitcoin surface is broader today. - You want managed transaction lifecycle. Turbo submit, automatic monitoring, and rollback webhooks are a real operational offload that Nexus does not replicate; Nexus gives you submit and evaluate, and state tracking is yours. - One of the audited contract templates matches your product. Vesting, multisig, staking campaigns, or subscription payments as REST calls can save you a Plutus audit cycle. - You are building agent-native billing. x402 pay-per-call with no account is a genuinely novel rail; Nexus's MCP server assumes a subscription behind the key. - Vendor balance sheet weighs heavily in your procurement. Draper-backed, institutional revenue lines, audited stack. Judged purely on funding, Maestro is the safer-looking counterparty. ### When Nexus is the better fit - Cardano is your first chain and you want a vendor whose roadmap agrees with you. The observable 2026 shipping cadence on Cardano and Midnight is at Nexus; at Maestro, three Cardano platform components have sat at "Coming Soon" through the Bitcoin buildout. - You need market data deeper than OHLC and trades : order books (real and AMM-simulated), pool TVL and reserves, indicators, NFT floors and sales, top-trader analytics, across 15 venues, from $48/month total (Builder + Market Data) rather than starting at $49 for 4 endpoints. - You need wallet P&L on Cardano. Maestro simply does not have it there; its analytics live on Bitcoin. - You want to construct arbitrary transactions server-side (transfers, staking, governance, withdrawals) or ship a swap feature without integrating DEXes, signed client-side via CIP-30, keys never leaving your users. - You need live data push as streams. Maestro has no WebSocket anywhere (webhooks appear on the pricing page only as an Enterprise line item); polling a REST API against a credit meter is exactly the pattern streaming exists to kill. - You want to know your bill before you send traffic. Flat request pricing plus no-overage hard stops make the forecast a multiplication, not a reverse-engineering exercise against a private credit table. - You need governance reads (DReps, delegations, votes) on Cardano at all. ### Bottom line Maestro is a well-funded, well-documented platform whose center of gravity has moved to Bitcoin, with two genuinely unique Cardano features (managed transaction lifecycle, audited contract templates), thin market data, no analytics, no streaming, no governance API on Cardano, and a pricing model you cannot fully see from outside. Nexus is the Cardano-first, full-stack option: deeper market data, P&L, general transaction building, swap routing, streaming, and flat arithmetic pricing, with a public status page at status.gerowallet.io and Bitcoin coverage that is real but narrower than Maestro's. Nexus is built by A.D. Labs, the team behind GeroWallet. The migration map and the short version of this comparison are on the Maestro alternative page . Run the comparison on your own traffic: Start the 7-day Builder trial , explore every endpoint in the live playground at nexus.gerowallet.io/docs , or reach us for Enterprise and Dedicated terms via the support page . ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # Maestro API Alternatives for Cardano & Bitcoin (2026): Nexus URL: https://nexus.gerowallet.io/blog/maestro-alternative-bitcoin-cardano/ Description: Five Maestro API alternatives for Cardano and Bitcoin compared on coverage, credit vs flat pricing, plus an endpoint-by-endpoint migration map. Comparison · Updated October 19, 2026 ## Maestro Alternatives for Bitcoin and Cardano If you are searching for a Maestro alternative, you are probably one of two teams. Either you are Cardano-first and you have noticed that Maestro's engineering attention has moved to Bitcoin, or you build across both UTXO chains and you want one vendor, one bill, and one set of docs instead of stitching providers together. This article compares the realistic options, sets out what to verify before you switch, and gives you an endpoint-level migration map. ### TL;DR If you need Bitcoin and Cardano from one provider, Nexus is the closest structural match to what Maestro gave you. It covers both chains plus Midnight through one account, one base URL and flat monthly pricing, and it adds market data, wallet P&L and streaming that Maestro never offered on Cardano. If you are Cardano-only and need nothing but chain data, Blockfrost is the incumbent and the cheapest, though 2026 raised ownership questions of its own, covered in Nexus vs Blockfrost . If you are Bitcoin-first and deep in Bitcoin DeFi tooling, stay with a Bitcoin specialist. Provider | Chains | Pricing | Best for | Start from | Nexus | Bitcoin, Cardano, Midnight | Flat monthly tiers | Both UTXO chains from one vendor, with a forecastable bill | From $9/mo; 7-day trial on Builder ($29) | Blockfrost | Cardano only | Free Starter, then flat euro tiers | Cardano-only teams needing chain data and nothing else | Free; paid from €29/mo | Koios | Cardano only | Free to low-cost, community-run | Experiments and cost-sensitive work without uptime obligations | Free (community) | Chainstack / GetBlock / NOWNodes | Broad, incl. both | Request units or per-request | Raw RPC when you will build the index layer yourself | Varies | Self-hosted | Whatever you run | Your infrastructure | Teams for whom infrastructure is the product | Engineering time | Migration effort: days for standard chain-data endpoints, considerably longer if you are built on Maestro's Transaction Manager or Managed Contracts. The endpoint-by-endpoint map is further down . ### Why teams start looking for an alternative None of this is speculation. It is publicly observable, and you should verify it yourself rather than take a competitor's word for it. The company's centre of gravity moved to Bitcoin. Maestro's February 2025 seed round was headlined as funding for "the Bitcoin DeFi revolution." The root domain now leads with Maestro Institutional , a Bitcoin treasury and yield business for accredited investors, with the developer platform one level down at gomaestro.org/developer . The Cardano changelog tells a different story than the Bitcoin one. Maestro's Cardano changelog tops out at v1.8.0, Conway compatibility, and the Conway era shipped in 2024. Its most recent entries are endpoint deprecations rather than new capability. The Bitcoin changelog shows sustained new-endpoint growth, and the open-source work is Bitcoin-side. Long-standing "Coming Soon" items on Cardano. Cardano Node RPC, Cardano mempool monitoring, and the Cardano Event Manager have sat as planned rather than shipped on Maestro's own platform overview for an extended period. Compute credits make budgeting hard. Maestro meters usage in compute credits with a dual throttle, a per-second rate limit plus a credit allowance, surfaced through X-RateLimit-Remaining-Second and X-Maestro-Credits-Remaining . Each call burns credits weighted by the average duration of that operation, and the per-endpoint credit table is not public: it sits behind the dashboard login. You cannot forecast a bill against a table you cannot see. To be clear about what this does and does not mean: Maestro's Cardano indexer is operational, its documentation is genuinely good, and it runs a public status page , which is more than most of the field. The signal here is roadmap direction and vendor concentration risk, which is a legitimate thing to price into an infrastructure decision, not a claim that anything is broken. ### What to verify before you switch Map your actual endpoint usage first. Pull your access logs and list the endpoints you really call, with volumes. Most teams discover they use a fraction of what they think they do, which makes migration far smaller than feared. Check the pricing model, not just the headline price. Flat request pools are forecastable. Credit and compute-unit models are not, until production traffic has run through them for a month. Confirm both chains are first-class, if you need both. A provider that treats one chain as the product and the other as a checkbox will eventually make you feel it, usually at the worst moment. Look for the capabilities you would otherwise build. Market data, wallet profit and loss, server-side transaction building, and streaming are the four things teams most often end up writing themselves after picking a data-only API. Test error semantics and rate-limit headers. How a provider behaves at the edges is a better quality signal than any benchmark on a landing page. ### The five realistic alternatives Option | Chains | What you get | Best when | Nexus | Bitcoin, Cardano, Midnight | Full data API on all three, plus optional market data, wallet analytics, Cardano transaction builder, DEX aggregator, MCP server, WebSocket streaming. Flat monthly tiers. | You want Bitcoin and Cardano from one vendor with a forecastable bill | Blockfrost | Cardano only | Well-established Cardano REST API, free Starter tier then flat euro tiers, broad SDK coverage | You are Cardano-only and need nothing beyond chain data | Koios | Cardano only | Open-source, community-run, very cheap, self-hostable | Experimentation and cost-sensitive workloads without uptime obligations | Chainstack, GetBlock, NOWNodes | Broad, including Bitcoin and Cardano | Raw RPC node access | You want nodes, and you are prepared to build the index layer yourself | Self-hosted | Whatever you run | Bitcoin Core plus txindex , an ord indexer, cardano-node plus db-sync, Ogmios | Infrastructure is your product, and you have the team for it | The gap this table exposes is real. The multi-chain generalists reach both Bitcoin and Cardano, but only as raw RPC, which leaves the index layer to you. The Cardano specialists do Cardano well and do not touch Bitcoin at all. Very few providers offer high-level data APIs across both UTXO chains, which is exactly why teams needing both end up shortlisting Maestro and Nexus against each other. ### Nexus and Maestro, side by side | Maestro | Nexus | Bitcoin data API | Yes, actively developed, plus wallet API and L2 tooling | Yes: addresses, UTXOs, blocks, chain tip, fees, mempool, ordinals, runes, broadcast | Cardano data API | Yes, changelog stalled at Conway | Yes, the deepest chain on the platform, including Conway governance and DReps | Midnight | No | Yes, transactions and DUST | Pricing model | Compute credits, per-endpoint weights not public | Flat monthly request pools with published rate limits | Market data | Thin on Cardano, on higher tiers | Optional add-on across 11 Cardano DEXes, with order books, TVL, NFT floors | Wallet profit and loss | Bitcoin only, not on Cardano | Optional add-on, FIFO, on Cardano | Transaction builder | Yes, Cardano, plus managed transaction lifecycle | Yes, Cardano, returns unsigned CBOR for client-side signing | WebSocket streaming | No, push means webhooks | Optional package | Status page | Yes, public | Yes, public at status.gerowallet.io | Two structural differences deserve more than a table row. Pricing you can forecast. Nexus publishes the request pool, the requests-per-second rate limit, and the burst depth for every tier, and returns X-RateLimit-Limit , X-RateLimit-Remaining , and X-RateLimit-Reset on metered responses so your own code can watch the quota. Your bill is a multiplication you can do before you integrate, rather than a reverse-engineering exercise afterwards. One account across chains, keys scoped per chain. Nexus gives you one account, one base URL, one auth header, and one docs site across Bitcoin, Cardano, and Midnight. Each API key is scoped to one chain and one network, so you create a key per chain and network you call, all under the same subscription and the same bill. That scoping is a deliberate blast-radius decision, documented in Authentication . ### Migration map Most of a migration is mechanical. These are the direct equivalents. Cardano What you need | Nexus endpoint | Address info and balance | GET /api/addresses/{address} | Address UTXOs | GET /api/addresses/{address}/utxos | Address transaction history | GET /api/addresses/transactions/{address} | Stake account info and delegation | GET /api/account/{stakeAddress}/info | Asset and NFT metadata | GET /api/assets/detailedInfo | Transaction details | GET /api/transactions/{txHash} | Submit a transaction | POST /api/transactions/submit | Evaluate script execution units | POST /api/transactions/evaluate | Latest block | GET /api/blocks/latest | Protocol parameters | GET /api/epoch/latest/parameters | Resolve a datum by hash | GET /api/scripts/datum/{datumHash} | Build an unsigned transaction | POST /api/tx/build | Bitcoin What you need | Nexus endpoint | Chain tip and sync state | GET /api/btc/chain/tip | Address stats across chain and mempool | GET /api/btc/addresses/{address} | Confirmed balance | GET /api/btc/addresses/{address}/balance | Spendable UTXOs | GET /api/btc/addresses/{address}/utxos | Inscriptions and rune balances at an address | GET /api/btc/addresses/{address}/ordinals | Fee estimates in sat/vB | GET /api/btc/fees | Mempool snapshot and fee histogram | GET /api/btc/mempool | Inscription metadata | GET /api/btc/ordinals/inscriptions/{id} | Rune metadata | GET /api/btc/ordinals/runes/{rune} | Transaction by txid | GET /api/btc/txs/{txid} | Broadcast a signed transaction | POST /api/btc/txs/submit | The practical sequence. Put your provider behind a thin interface if it is not already, so the swap is one implementation rather than edits scattered across your codebase. Create a Nexus key per chain and network. Run both providers in parallel against production read traffic and diff the responses for a few days, which surfaces field-shape differences before your users do. Move reads first, then writes and broadcast last. Keep the old key alive until your current billing cycle closes. Both providers are REST over HTTPS with a header-based API key, so the network layer of your client does not change. The work is field mapping and testing, and the parallel-run step is what turns a nervous migration into a boring one. ### Nexus pricing Plan | Requests per month | Rate limit | Burst | API keys | Starter, $9 | 3M | 10 req/s | 100 | 2 | Builder, $29 | 10M | 25 req/s | 250 | 4 | Growth, $79 | 30M | 50 req/s | 500 | 7 | Scale, $199 | 50M | 100 req/s | 1,000 | 13 | Enterprise, $499 | 200M | 500 req/s | 5,000 | Unlimited | Add-ons attach to any plan: market data at $19, wallet analytics at $15, the Cardano transaction builder at $19, an MCP server at $19, IPFS at $5, and WebSocket packages from $29. A Dedicated tier with isolated infrastructure is available for compliance-sensitive workloads. There is no plan at no charge; Starter at $9 is core API only, so add-ons start at Builder. There is a 7-day trial on the Builder plan, which is enough to run a real parallel test rather than a toy one. Ready to compare against your own workload? Start the 7-day Builder trial . ### Common questions Is there a drop-in replacement for the Maestro API? No provider is byte-compatible with Maestro's response shapes, so plan on field mapping. What makes it tractable is that the capability surface maps closely for standard chain data, and the migration tables above cover the endpoints most teams actually use. Can I use one provider for both Bitcoin and Cardano? Yes. Nexus covers both, plus Midnight, under one account and one bill, with a separate key per chain and network. That is the specific gap most Maestro alternatives do not fill, because the Cardano specialists are Cardano-only and the multi-chain generalists sell raw RPC. How long does a migration take? For a team using standard chain-data endpoints behind an existing provider interface, days rather than weeks, and most of that is parallel-run verification rather than code. Teams built on Maestro's Transaction Manager or Managed Contracts should budget considerably more, because those need rebuilding rather than remapping. What about ordinals and runes? Nexus indexes both. You can resolve inscriptions and rune balances by address, by outpoint, and by inscription ID or spaced rune name, using the same key as the rest of the Bitcoin surface. Do I lose market data or transaction building if I switch? On Cardano, the opposite in most cases. Market data across 11 DEXes with order books and NFT floors, FIFO wallet profit and loss, server-side transaction building, a DEX aggregator, and WebSocket streaming are available as add-ons, so capabilities teams normally build in-house become a line item. On Bitcoin, be aware Nexus is a data and broadcast API without server-side transaction construction. ### Next step Vendor changes are worth doing deliberately and worth doing early, before a deadline forces the decision. Map your endpoint usage, price both models against your real request volume, and run the two providers side by side on read traffic before you commit. Nexus is built by A.D. Labs, the team behind GeroWallet; the endpoint-level migration map lives on the Maestro alternative page and in the docs . To start that evaluation now, Start the 7-day Builder trial , then follow the Quick Start . If you want the Bitcoin side in more depth first, read Bitcoin Data Infrastructure: What Your App Actually Needs . ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # Bitcoin Data Infrastructure: Node, Indexer or API? | Nexus URL: https://nexus.gerowallet.io/blog/bitcoin-data-infrastructure/ Description: What a Bitcoin app needs for UTXOs, balances, fees, mempool, ordinals and runes, and when to run a node, add an indexer, or use an API instead. Blog · Updated November 6, 2026 ## Bitcoin Data Infrastructure: What Your App Actually Needs ### Bitcoin Data Infrastructure: What Your App Actually Needs Every Bitcoin application, from a wallet to an ordinals marketplace to a treasury dashboard, sits on top of the same small set of questions. What is the chain tip right now? Which outputs does this address control? What fee will get my transaction confirmed in three blocks? Did my broadcast actually land? Bitcoin data infrastructure is the layer that answers those questions fast, consistently, and without falling over when your traffic doubles. This guide covers what that layer has to do, where teams get it wrong, how to decide between running your own node and buying an API, and what a production Bitcoin data API looks like in practice. ### TL;DR Bitcoin data infrastructure is three layers, and most teams only price one of them. A node gives you consensus. An index gives you the lookups Bitcoin Core does not keep. An API gives you something your application can actually call. Node providers sell you the first. A Bitcoin data API sells you all three, and the gap between them is measured in months of engineering. What your app needs | Bitcoin Core alone | Node provider (RPC) | Bitcoin data API | Chain tip and reorg detection | Yes | Yes | Yes | UTXOs for an arbitrary address | No, needs indexing | Rarely | Yes | Confirmed balance vs mempool state | Partial | Partial | Yes | Fee estimates in sat/vB | Yes | Yes | Yes | Mempool size and fee histogram | Yes | Sometimes | Yes | Ordinals and runes | No, needs an ord indexer | No | Yes | Broadcast with usable error codes | Raw reject codes | Raw reject codes | Mapped to HTTP status | You operate the servers | Yes | No | No | Rule of thumb: if Bitcoin infrastructure is your product, run it yourself. If it is a dependency of your product, buy it, and pick a vendor whose roadmap points where yours does. Where Nexus fits: Bitcoin, Cardano and Midnight from one account and one base URL, flat monthly pricing from $9, with a 7-day trial on Builder, and ordinals and runes indexed alongside the standard chain data. The full endpoint list is further down . ### What "Bitcoin data infrastructure" actually means The phrase gets used for three different layers, and conflating them is the first mistake teams make. The node layer. Bitcoin Core itself. It validates blocks, holds the UTXO set, tracks the mempool, and exposes JSON-RPC. It is authoritative and it is also deliberately minimal. Bitcoin Core is not designed to answer "show me every transaction this address has ever been in" quickly. The index layer. Software that reads the chain and builds the lookups Bitcoin Core does not maintain by default: address history, an ordinals and runes index, spent-output tracking. This is where most of the operational cost lives. The API layer. The HTTP surface your application actually calls, with authentication, rate limiting, pagination, caching, and error semantics that make sense to a client developer. A Bitcoin node provider sells you the first layer. A Bitcoin data API sells you all three. The difference matters enormously for how much code you end up writing, and it is the single most common reason a provider that looked cheap turns out not to be. ### The seven things a Bitcoin data layer has to get right Chain tip and reorg handling. Your application needs the current best block, and it needs to know when the chain reorganises underneath it. A one-block reorg is routine. If your data layer reports a transaction as confirmed and then the block disappears, and your API gives you no way to detect that, you will ship a bug that only appears in production. Address UTXO sets. Bitcoin has no accounts. To spend, you need the exact list of unspent outputs an address controls, with values and outpoints. Bitcoin Core will not give you this for an arbitrary third-party address without extra indexing. Every wallet and every transaction builder depends on it. Confirmed balance separate from mempool state. A user seeing an incoming payment wants to know it exists. Your coin selection code must not spend it until it confirms. Those are two different numbers, and your data layer should expose both, distinctly. Fee estimation. Bitcoin fees move fast. You need sat/vB estimates keyed by a target confirmation window, sourced from real network conditions, or your users will overpay in quiet periods and get stuck in busy ones. Mempool visibility. Count, virtual size, and a fee histogram tell you what the current competition for block space actually looks like. This is what powers a credible "your transaction should confirm in about X" estimate and a working replace-by-fee flow. Ordinals and runes. If you touch Bitcoin NFTs or fungible tokens on Bitcoin, you need a separate ord-style index: which inscriptions and rune balances sit at an address, which are carried by a specific outpoint, and metadata by inscription ID or rune name. Getting this wrong means accidentally spending an inscription as ordinary sats, which is the most expensive bug in the category. Broadcast with honest error semantics. When you submit a signed transaction, bitcoind returns reject codes. A good API maps them to HTTP status codes you can branch on, so "already in the chain" is a different outcome from "this transaction is invalid". A bad API returns 500 for both and leaves you pattern-matching an error string. ### Run your own node, or buy an API? Both are defensible. The decision comes down to what your team should be spending its time on. Running your own stack means Bitcoin Core with txindex=1 if you need arbitrary historical transaction lookups, several hundred gigabytes of storage that grows every month, an initial block download measured in days, plus a separate ord indexer if you need inscriptions and runes. Add monitoring, alerting, an on-call rotation, and a plan for what happens when the machine dies during a fee spike. You get full control, no per-request cost, and no vendor in your dependency chain. Buying an API means you get the index layer someone else operates, a documented HTTP surface, and a support path when something breaks at 3am. You give up control and you take on vendor risk, which is real: providers change direction, reprice, or deprioritise a chain. The honest rule of thumb: if Bitcoin infrastructure is your product, run it yourself. If Bitcoin infrastructure is a dependency of your product, buy it, and pick a vendor whose roadmap points the same direction as yours. ### How to evaluate a Bitcoin data provider Work down this list before you write a line of integration code. Check the endpoint surface against your actual feature list. Not the marketing page, the API reference. If you need runes, find the runes endpoint. If you need mempool fee histograms, find that endpoint. Missing pieces become custom infrastructure you did not budget for. Read the pricing model, not the price. Flat request pools tell you your monthly bill before you sign. Compute-credit and compute-unit models weight different methods differently, so an identical workload can cost wildly different amounts across providers, and you cannot forecast until you have run for a month. Across the wider market the same call can be metered at 1 credit by one vendor and 200 by another, which is why this is the most common source of surprise infrastructure bills. Find the rate limits and the burst allowance. A monthly quota tells you nothing about whether your traffic spike gets throttled. You want requests per second and burst depth, published. Look at what happens when you exceed the plan. A hard 429, overage billing, or a degraded floor are all acceptable. Not knowing which one you get is not. Check the changelog, not the roadmap. A roadmap is a statement of intent. A changelog is a record of shipping. If the chain you care about has a changelog that stopped a year ago while another chain's is active, you have learned where the engineering effort goes. Test the errors deliberately. Submit an invalid transaction. Query a nonexistent txid. Call an endpoint your plan does not include. The quality of those three responses tells you more about a provider than any benchmark on a landing page. ### What Nexus covers on Bitcoin today Nexus exposes Bitcoin over the same REST surface, the same X-Api-Key header, and the same docs site as its Cardano and Midnight coverage. Networks are selected with a network query parameter, and Bitcoin supports bitcoin-mainnet and bitcoin-testnet4 . Area | Endpoint | What it returns | Chain | GET /api/btc/chain/tip | Chain tip plus sync metadata | Chain | GET /api/btc/chain/latest-block | Latest fully applied block | Blocks | GET /api/btc/blocks | Most recent N blocks, descending height | Blocks | GET /api/btc/blocks/{idOrHeight} | A block by hash or height | Addresses | GET /api/btc/addresses/{address} | Address statistics across chain and mempool | Addresses | GET /api/btc/addresses/{address}/balance | Confirmed satoshi balance | Addresses | GET /api/btc/addresses/{address}/utxos | Unspent outputs for the address | Addresses | GET /api/btc/addresses/{address}/ordinals | Inscription IDs and rune balances held | Fees | GET /api/btc/fees | sat/vB estimates keyed by target block count | Mempool | GET /api/btc/mempool | Count, virtual size, and fee histogram | Ordinals | GET /api/btc/ordinals/inscriptions/{id} | Inscription metadata | Ordinals | GET /api/btc/ordinals/runes/{rune} | Rune metadata by ID or spaced name | Ordinals | GET /api/btc/ordinals/outputs/{outpoint} | Inscriptions and runes carried by an outpoint | Transactions | GET /api/btc/txs/{txid} | Transaction by txid | Transactions | GET /api/btc/txs/{txid}/hex | Raw transaction hex | Transactions | POST /api/btc/txs/submit | Broadcast a signed transaction | Two details are worth calling out, because they are exactly the sharp edges described above. The address endpoints separate confirmed balance from combined chain-and-mempool statistics, so your coin selection logic and your user-facing balance can deliberately use different sources. And the submit endpoint maps bitcoind reject codes onto HTTP status codes, so codes -22, -25, and -26 come back as 400 while -27, already in the chain, comes back as 409. You branch on the status instead of parsing an error string. Being straight about the boundaries: this is a Bitcoin data and broadcast API. Nexus does not do server-side Bitcoin transaction construction (the transaction builder is a Cardano add-on), and it does not run Bitcoin L2 or DeFi-specific tooling. If those are your requirements, weigh a Bitcoin-specialist platform. The full reference, with a live playground on every endpoint, is at nexus.gerowallet.io/docs . ### Your first Bitcoin call Create an account, generate a key scoped to Bitcoin mainnet, and read the chain tip. const res = await fetch( 'https://nexus.gerowallet.io/api/btc/chain/tip?network=bitcoin-mainnet', { headers: { 'X-Api-Key': 'nxs_your_api_key_here' } } ); const tip = await res.json(); console.log(tip); One thing to know before you start: each Nexus API key is scoped to one chain and one network. If you are building across Bitcoin and Cardano you create a key for each, under the same account, the same base URL, and the same billing. The scoping rule, and the error you get when a request and a key disagree, are documented in Authentication . ### Pricing, quotas, and rate limits Nexus prices in flat monthly tiers with published request pools and rate limits, so you can model your infrastructure cost before you integrate. Plan | Requests per month | Rate limit | Burst | API keys | Starter, $9 | 3M | 10 req/s | 100 | 2 | Builder, $29 | 10M | 25 req/s | 250 | 4 | Growth, $79 | 30M | 50 req/s | 500 | 7 | Scale, $199 | 50M | 100 req/s | 1,000 | 13 | Enterprise, $499 | 200M | 500 req/s | 5,000 | Unlimited | Metered responses carry X-RateLimit-Limit , X-RateLimit-Remaining , and X-RateLimit-Reset headers, so you can track your monthly quota from inside your own application rather than from a dashboard. Optional add-ons cover market data, wallet analytics, server-side transaction building for Cardano, a DEX aggregator, an MCP server for AI agents, and IPFS. A Dedicated tier with isolated infrastructure exists for compliance-sensitive workloads. Every plan is paid, with a 7-day trial on the Builder plan, which is enough to run a real integration rather than a toy one. Start building: get a key and start the 7-day Builder trial . ### Common questions Do I need my own Bitcoin node if I use a data API? No, for the large majority of applications. You need your own node when you require full validation guarantees with no third party in the trust path, or when your query volume makes per-request pricing more expensive than operating hardware. What is the difference between a Bitcoin node provider and a Bitcoin data API? A node provider hands you JSON-RPC access to Bitcoin Core. A data API adds the index layer on top, which is where address history, ordinals, runes, and mempool analytics live. If a provider only offers RPC, plan to build and operate that index layer yourself. How do I handle reorgs safely? Track block height and hash together, never height alone. Re-verify recent confirmations against the chain tip before treating them as final, and choose a confirmation threshold that matches the value at risk. Can I query ordinals and runes through the same API as regular Bitcoin data? With Nexus, yes. The ordinals endpoints resolve inscriptions and rune balances by address, by outpoint, and by inscription ID or spaced rune name, using the same key and the same base URL as the rest of the Bitcoin surface. Does Nexus support chains other than Bitcoin? Yes. Cardano has the deepest coverage, including stake pools, assets, scripts, Conway-era governance, and a server-side transaction builder. Midnight covers transactions and DUST. See Inside the Nexus API for the full platform surface. ### Where to go next Bitcoin data infrastructure is not a single product decision. It is a set of guarantees your application will quietly depend on for as long as it exists. Pick the layer you actually need, read the changelog before you read the landing page, and prefer pricing you can forecast over pricing you have to reverse-engineer. If you are moving off an existing provider rather than starting fresh, the endpoint-level migration map in Maestro Alternatives for Bitcoin and Cardano covers the mechanics. To evaluate Nexus against your own workload, the fastest path is a real call against real data. Get a key and start the 7-day Builder trial , work through the Quick Start , and point it at an address whose answer you already know. ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # Cardano Market Data API: 11 DEXes, One Platform | Nexus URL: https://nexus.gerowallet.io/blog/cardano-market-data-api/ Description: Token prices, OHLCV candles, DEX pools, order books, swap history, and NFT stats across all 11 Cardano DEXes through one REST API. Start a 7-day trial. Platform · Updated October 19, 2026 ## Cardano Market Data API: Prices, Candles, and Order Books Across All 11 DEXes ### Cardano Market Data API: Prices, Candles, and Order Books Across All 11 DEXes Cardano's liquidity is fragmented by design: Minswap V1 and V2, SundaeSwap V1 and V3, WingRiders V1 and V2, VyFi, Splash, TeddySwap, MuesliSwap, and CSwap all hold pieces of it. Any product that shows a token price, a wallet, a portfolio tracker, a trading tool, an analytics dashboard, has to answer an awkward question: whose price? Indexing one DEX gives you a partial answer; indexing all of them yourself means decoding each protocol's on-chain activity and keeping that pipeline current forever. The Nexus Market Data API does that aggregation for you. One REST surface, one X-Api-Key header, all 11 Cardano DEXes. ### What you can query Prices and history. Current ADA/USD market info, all tracked token prices or a single asset, a token's price across every DEX individually, top tokens by 24h volume or TVL, historical prices including price-at-timestamp lookups, OHLCV candles at 15m, 1h, 1D, and 1W resolutions for tokens and ADA/fiat, and an RSI(14) technical indicator. Token metadata, name, ticker, logo, decimals, comes from the same surface. DEX activity. Liquidity pools with TVL, reserves, and fees (all pools, by DEX, by pair, or by token), real limit order books plus AMM-simulated order books per pool, open orders by DEX, owner, or token, buy and sell quotes, recent swaps globally or per token, and top-trader rankings for any token. NFT markets. Tracked collections with statistics, floor prices, recent sales, and last-sale price per individual NFT, sourced from jpg.store activity. Ecosystem extras. Registered dApp blueprints with persisted event querying, a leaderboard of wallets ranked by LP TVL, and an indexer sync-status endpoint so you can verify data freshness programmatically. ### How it works Plain REST over HTTPS. No proprietary SDK required, the HTTP client built into Node, the JDK, Python, Go, Rust, or your shell is enough: curl "https://nexus.gerowallet.io/api/market/prices/top-volume" \ -H "X-Api-Key: nxs_your_api_key_here" A machine-readable OpenAPI 3.1 spec is published at /v3/api-docs with a live playground at /docs , so you can generate a typed client for 50+ languages with one openapi-generator command. Behind the surface, requests fan out across multiple providers with automatic failover, and hot data is served from cache. ### What teams build with it - Wallets and portfolio apps price user holdings accurately by aggregating across venues instead of trusting one pool's ratio. - Trading tools combine candles, RSI, order books, and per-DEX prices to power charts and route decisions. - Analytics products track pool TVL, swap flows, and top traders without running an indexer per DEX. - NFT platforms surface floor prices and sales history alongside token data from the same subscription. If you need the data pushed rather than pulled, pair this add-on with WebSocket streaming for live price and swap events instead of polling. ### Pricing Market Data is a $19/month add-on on the Builder ($29), Growth ($79), and Scale ($199) tiers (not on the $9 Starter tier), and is included in Enterprise ($499). REST add-ons share your tier's unified request pool, one number to track, no compute-unit weighting. ### Try it on your own tokens The 7-day Builder trial includes the full API surface, so you can compare Nexus prices, candles, and order books against whatever you use today. Get your key at nexus.gerowallet.io and make your first call in minutes. ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # Cardano MCP Server for Claude & Cursor: 25 Tools | Nexus URL: https://nexus.gerowallet.io/blog/nexus-mcp-server/ Description: Point Claude Desktop, Claude Code or Cursor at one MCP endpoint and get 25 blockchain tools: Cardano data, DEX prices, Bitcoin, Midnight, tx building. Platform · Updated October 19, 2026 ## Nexus MCP Server: Connect Claude and AI Agents to Cardano Data ### Nexus MCP Server: Connect Claude and AI Agents to Cardano Data AI agents are becoming a real interface to software, and the Model Context Protocol (MCP) is how they call external systems as native tools. If you are building agent workflows that need blockchain data, or you simply want Claude to answer "what is this wallet holding?" with live chain data instead of guesses, the missing piece is an MCP server that speaks Cardano. Nexus hosts one. Point Claude Desktop, Claude Code, Cursor, or any MCP-compatible client at https://nexus.gerowallet.io/mcp/ , authenticate with your Nexus API key, and the agent gains 25 tools across six domains. ### What your agent can do - Cardano (8 tools): account info and history, address info, asset info, block info, epoch info, stake pool info, and transaction lookups. - Market data (4 tools): token prices, OHLCV candles, pair listings, and top-token rankings from the same engine that indexes all 11 Cardano DEXes. - Bitcoin (4 tools): balances, transaction info, fee estimates, and UTXO sets. - Midnight (4 tools): network info, DUST status, unshielded transaction building, and submission. - Transaction building (2 tools): build unsigned Cardano transactions and preview them before anything is signed, signing stays with you, and no private keys ever touch Nexus. - Account (3 tools): inspect your own Nexus subscription, API keys, and profile from inside the conversation. In practice that means an agent can research a token's price history, inspect a whale wallet, check a stake pool's performance, and draft an unsigned delegation transaction, all in one conversation, all against live data. ### Setup in one config block { "mcpServers": { "nexus": { "url": "https://nexus.gerowallet.io/mcp/", "headers": { "X-Api-Key": "nxs_your_api_key_here" } } } } That is the whole integration for Claude Desktop or Claude Code. A health check lives at GET /mcp/health , authentication is per API key, and every tool call is audit-logged and counted against your plan's normal request quota, governance your security team can reason about. ### Why this beats teaching an agent your REST calls You can always hand an LLM a REST spec and hope. MCP tools are the robust version: typed, named operations the agent discovers and calls natively, with authentication handled at the transport. One add-on unlocks the full tool set, the MCP tools for market data and transaction building work even without those REST add-ons on your plan. ### What teams build with it - Research assistants that answer token, wallet, and pool questions with live on-chain and market data. - Operations copilots that monitor addresses and draft transactions for human sign-off. - Agent products that need a managed, authenticated blockchain backend instead of scraping or self-hosted indexers. - Internal tooling where "ask the agent" replaces writing one-off scripts against the chain. ### Pricing The MCP Server is a $19/month add-on on Builder ($29), Growth ($79), and Scale ($199), not on the $9 Starter tier, included in Enterprise ($499). Nexus is the only Cardano data platform with a hosted MCP endpoint today; for the full capability map, see the platform overview . ### Give your agent the chain Start the 7-day Builder trial at nexus.gerowallet.io , add the MCP Server add-on, paste the config block above, and ask your agent something only live data can answer. ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # Blockfrost vs Nexus: Pricing, Rate Limits & Features URL: https://nexus.gerowallet.io/blog/nexus-vs-blockfrost/ Description: Blockfrost vs Nexus compared layer by layer: API surface, rate limits, pricing math at real request volumes, reliability, and data beyond chain reads. Comparison · Updated October 19, 2026 ## Nexus vs Blockfrost: A Full-Stack Data API Compared to the Cardano Incumbent ### Nexus or Blockfrost for your Cardano data layer? If you build on Cardano, Blockfrost is probably the first API you ever called. It has been the default hosted gateway to the chain since 2020, it is open source top to bottom, and its OpenAPI spec is the closest thing Cardano has to a de facto data standard. Nexus is a younger, broader platform: the same on-chain reads, plus aggregated DEX market data, FIFO wallet P&L, server-side transaction building, a DEX aggregator, and WebSocket streaming, behind one REST surface. The two products overlap on maybe a third of their endpoints and diverge completely on the rest, so this comparison goes layer by layer: API surface, architecture and consistency, rate limiting mechanics, pricing math, reliability posture, and the strategic question hanging over Blockfrost in mid-2026. Everything here was verified against primary sources in July 2026; links are inline so you can check our work. ### The 2026 elephant: Blockfrost's ownership question Before the feature tables, you should know what is happening to Blockfrost right now, because it affects any long-term vendor decision. In July 2026, an on-chain governance action proposed to transform Blockfrost into a free, community-governed, not-for-profit public good. The treasury ask is about 9.8M ADA. The plan, per the proposal page , was one public API free for everyone with no paid tier operated by the entity, commercial SLAs pushed out to independent partners, source code and trademarks transferred to a not-for-profit with a community-elected board, and a 99% monthly uptime commitment during the transition. IOG, which took over Blockfrost via a strategic investment in January 2024 (the site footer today reads "IOG Singapore Pte. Ltd."), would have stepped back to a non-voting advisory role. That question is now settled: the vote closed at the end of July 2026 well short of the 66.67% threshold, and on-chain the action shows as expired without ratification (epoch 646). Blockfrost's commercial tiers continue as they are. The episode still belongs in your risk model, because you are buying from a vendor whose own owner proposed to stop operating it commercially, and the community declined to fund the alternative. That is not disqualifying, but it is not nothing either. Nexus, for contrast, is a commercial product operated by Gero Labs (the GeroWallet team) with a conventional subscription model and no ownership questions in flight. ### API surface, endpoint by endpoint Both products are REST-first with a published OpenAPI spec (Blockfrost 0.1.90 , June 2026; Nexus on OpenAPI 3.1, live at nexus.gerowallet.io ). Blockfrost's merged spec contains about 128 paths; the Nexus docs cover about 130. But the composition is very different. Capability | Blockfrost | Nexus | Blocks, epochs, txs, addresses, accounts, assets, pools | Yes, mature (about 80 endpoints) | Yes (about 35 endpoints, plus batch CBOR fetch) | Conway governance (DReps, proposals, committee) | Yes, 19 endpoints, updated through June 2026 | Partial: DRep list, detail, delegators, votes | Mempool inspection (Cardano) | Yes (3 endpoints) | No | Script and datum queries | Yes, incl. CIP-33 reference script UTxOs | Yes (script by hash, datum by hash) | Transaction evaluate (ex-units) | Yes (Ogmios-backed) | Yes | Transaction submit | Yes, plus priority "premium submit" on Developer+ | Yes | Transaction building (server-side, unsigned CBOR out) | No, delegated to client libraries | Yes: 6 builders + a max-ADA helper | DEX market data (prices, OHLCV, order books, TVL) | No | Yes (about 48 endpoints) | DEX aggregator (quote, build, submit swaps) | No | Yes (7 endpoints, 15 routable venues) | Wallet P&L / portfolio analytics | No | Yes (FIFO, single and multi-wallet) | NFT market data (floor, sales) | No | Yes | WebSocket streaming (Cardano) | No (webhooks instead) | Yes (SockJS + STOMP) | Webhooks | Yes (beta, tier-gated) | No | IPFS | Yes, bundled per tier + Filecoin quotas | Yes, $5 add-on (gateway, IPNS, per-key pinning) | MCP server for AI agents | No | Yes, 25 tools, $19 add-on | Bitcoin | No | Yes: 16 endpoints incl. ordinals and runes | Midnight | Yes (beta): GraphQL indexer, GraphQL WS, node RPC | Yes: 12 REST endpoints incl. DUST and tx building | Three honest observations from that table. Blockfrost is deeper where they overlap. On pure chain data, Blockfrost has more endpoints, more filters, and six years of accumulated edge-case handling. Its Conway governance group (19 endpoints covering DReps, proposals with CIP-129 addressing, and the constitutional committee, with additions as recent as June 2026 ) is substantially deeper than Nexus's current DRep set. It also has Cardano mempool endpoints, which Nexus does not. Nexus is wider everywhere else. Market data, P&L, transaction construction, swap routing, and streaming simply do not exist in Blockfrost's spec, by design. A Blockfrost-based product that needs token prices typically adds TapTools or a custom indexer; needs P&L, builds FIFO accounting in-house; needs live prices, polls. Each of those is another vendor or another internal system to operate. The multi-chain stories differ in kind. Blockfrost added hosted Midnight infrastructure in April 2026 : a GraphQL indexer, GraphQL WebSocket subscriptions, and node JSON-RPC, all beta, bundled on every tier. Nexus serves Midnight over the same REST surface as its other chains, and goes further on the transaction side: DUST tracking, NIGHT/DUST registration builders, unshielded transaction building and submission. Nexus also runs live Bitcoin endpoints (self-hosted bitcoind plus an ord indexer for ordinals and runes) and Apex Fusion networks. Blockfrost has no Bitcoin story. One nuance to plan around: Nexus API keys are scoped per chain and network, so multi-chain means multiple keys under one account and one bill, not a single key everywhere. ### Architecture and the consistency question Blockfrost's hosted API and its self-hostable twin ( blockfrost-backend-ryo ) are a Fastify service reading from cardano-db-sync's PostgreSQL, with Ogmios handling transaction evaluation. That architecture has one documented, still-open consequence: issue #86 , filed by the cardano-transaction-lib team, describes how db-sync and Ogmios sit at different chain tips, so the UTxO view and the evaluation view can disagree. The maintainer's on-record position is that absolute consistency between the two tools is not achievable. In practice this bites chained-transaction flows: a transaction you just evaluated or submitted may not yet be visible to /addresses/{address}/utxos when you build the next one. The issue has been open since 2022 and db-sync remains the data layer, so it is still a real edge case in 2026, and client-side retry logic remains the standard workaround. Nexus runs a different topology: a Java 21 / Spring Boot service in front of a prioritized provider chain per network. Reads are served by Nexus's self-hosted yaci-store indexers first, with Koios and, yes, Blockfrost itself as circuit-breakered fallbacks (Resilience4j per provider). The interesting part for this discussion is the health model: a tip-staleness check removes an indexer from routing when it is alive but serving stale data, rather than only when it is down. That does not make read-your-writes magically guaranteed across a distributed system, and we will not claim it does, but it is an architecture that treats "responding with old data" as a failure mode, which is precisely the failure mode behind issue #86. If chained transactions are your workload, test both against your flow during a trial; it is a 30-minute experiment. Being transparent about that provider chain also tells you something else: Nexus depends on Blockfrost as a tertiary fallback for Cardano reads. We think disclosing that is more useful to you than pretending otherwise. ### Rate limiting mechanics The two systems throttle differently, and the difference matters at scale. Blockfrost allows 10 requests/second per IP with a burst of 500 , refilling at 10/s (a drained burst takes about 50 seconds to recover), on every tier; only Enterprise gets custom limits. Quotas are per day (50k on the free Starter, 300k on Hobby, 1M on Developer), reset at midnight UTC. The error ladder is specific: HTTP 429 for rate, 402 for exhausted daily quota, and 418 as an auto-ban if you keep hammering after a 429/402. One-day "boost" purchases add 300k or 1M requests when you blow the cap. Nexus meters per key on two independent axes: a monthly request pool and a per-second token bucket whose depth is the burst. Both scale with tier: Builder gets 25 req/s with a 250-token burst, Growth 50/500, Scale 100/1,000, Enterprise 500/5,000, with per-key overrides available on Enterprise. Monthly-quota state is exposed on every metered response via X-RateLimit-Limit , X-RateLimit-Remaining , and X-RateLimit-Reset , and the two 429 variants are distinguishable (the monthly one carries the quota headers and a reset_at body; the per-second one just sends Retry-After: 1 ). Add-on and subscription gating uses HTTP 402 with a machine-readable addon field. Hot GET endpoints support ETag/304 revalidation, and revalidated responses still count against quota, so caching never silently changes your bill. Structural differences to note: Blockfrost's paid tiers still share the flat 10 req/s ceiling, while Nexus's throughput grows with tier; Blockfrost resets daily, Nexus monthly; Blockfrost sells overage relief by the day, Nexus has no overage billing at all and simply returns 429 at the cap until you upgrade. Predictable, but a hard stop; size your tier accordingly. ### Pricing math Both vendors use flat subscription tiers, which makes them directly comparable, and honesty requires leading with this: on raw request volume per dollar, Blockfrost is cheaper, and its STARTER plan costs nothing while Nexus has no plan at no charge. - Blockfrost ( pricing ): Starter is free forever at 50k requests/day (about 1.5M/month), one project. Hobby is €29/month for 300k/day (about 9M/month). Developer is €79/month for 1M/day (about 30M/month), with 15% off annually. Enterprise is custom. There is also a pay-as-you-go mode, payable in ADA natively or by card, and IPFS plus Filecoin storage is bundled into every tier. - Nexus : Starter $9/month for 3M requests/month (2 keys, core API only, no add-ons, no trial). Builder $29/month for 10M requests/month (4 keys, 7-day trial, the only trial mechanism; there is no plan at no charge). Growth $79 for 30M. Scale $199 for 50M with streaming included. Enterprise $499 for 200M with every add-on and unlimited WebSocket bundled. Dedicated from $2,000 for isolated infrastructure. Add-ons: Market Data $19, Wallet Analytics $15, Transaction Builder $19, MCP $19, IPFS $5. WebSocket packages for Builder/Growth: $29, $59, $99. So a maxed-out Nexus Builder with every add-on is about $106/month against Hobby's €29, for roughly a quarter of Blockfrost's monthly request volume. If your workload is on-chain reads and nothing else, Blockfrost wins that arithmetic outright, and you should use it. The comparison inverts when you price the whole stack. The Blockfrost-era architecture for a trading tool or portfolio product is Blockfrost (chain reads) plus a market data vendor plus an in-house FIFO P&L pipeline plus a polling layer or custom streaming. The Nexus equivalent is one subscription where a request is a request across all of it. Whether $106 beats €29-plus-two-more-vendors-plus-an-indexer-on-call depends entirely on whether you need the upper layers. That is the actual decision, not the sticker prices. One more Blockfrost pricing virtue worth naming: paying in ADA via pay-as-you-go is genuinely useful for DAOs and treasuries that hold ADA. Nexus bills conventionally (PayPal rails today) and offers a GERO-holder discount ladder instead. ### Reliability posture Blockfrost publishes a status page showing 100% component uptime over the trailing 90 days as of this writing, markets 99.9% uptime and 100M+ requests/day, and reserves contractual SLAs for Enterprise. That is a solid public record, and we will not pretend otherwise. Nexus publishes a public status page with per-service uptime and incident history, and a changelog with a 30-day deprecation notice rule. It does not yet publish a third-party uptime figure, and we will not invent one here. Its reliability story is architectural (the multi-provider fallback and tip-staleness routing described above) and contractual: SLAs exist where a written agreement exists, on Enterprise and Dedicated, with Dedicated adding physically isolated infrastructure (own cluster and database), a negotiated SLA, and a 4-hour support response over a dedicated channel. For everything below that, the honest instruction is: run the 7-day trial against your production traffic pattern and measure. The rate-limit headers make it easy to script. ### When Blockfrost is the better fit Being specific, because several of these are decisive: - Your workload is pure on-chain reads. Blockfrost is cheaper per request, deeper on chain-data endpoints, and battle-tested. Nothing in Nexus's upper stack helps you if you never call it. - You want a plan that costs nothing. Blockfrost STARTER is 50k requests/day at no charge, forever, no card. Nexus's 7-day trial is an evaluation window, not a home for a hobby project. - You need Cardano mempool access. Blockfrost's mempool group has no Nexus equivalent today. Governance stopped being a gap in August 2026: Nexus serves DReps, proposals, votes, the committee and the constitution natively. - You want to self-host or need an exit hatch. The entire Blockfrost stack is open source, with two self-host paths (the full RYO stack and the lighter Dolos-based Blockfrost Platform 1.0 , which shipped in May 2026 with Hydra support). Nexus is a hosted product, full stop. - You lean on SDK breadth or framework defaults. Blockfrost has first-party SDKs in 15+ languages (about five actively maintained, led by blockfrost-js at ~23k weekly downloads) and first-class provider slots in MeshJS and Lucid Evolution. Nexus currently ships an OpenAPI spec, a live docs playground, and an MCP server, but no official SDKs and no MeshJS/Lucid provider, so with those frameworks Blockfrost is the path of least resistance today. - You need webhooks or push-based tx notifications and prefer them to managing a WebSocket connection. ### When Nexus is the better fit - Your product touches prices, P&L, swaps, or live data. That is the entire upper half of the surface table. One subscription replaces a two-or-three-vendor stack plus in-house accounting code. - You want transaction building as an API. Six server-side builders returning unsigned CBOR (transfers, delegation, stake registration with optional reward withdrawal, DRep registration, vote delegation with Trezor-compatible certificate encoding, withdrawals), signed client-side via CIP-30; keys never leave your side. With Blockfrost you bring your own builder library. - You want a swap feature without DEX integrations. The aggregator quotes and routes across 15 venues (live-verified July 2026: Minswap V1/V2, SundaeSwap V1/V3, WingRiders V1/V2, VyFi, Splash, TeddySwap, MuesliSwap, CSwap, Genius Yield, SaturnSwap, ShadowBook, SnekFun) and builds the swap server-side, non-custodially, at a 0.10% fee (0.05% for GERO holders). There is even an embeddable widget with a partner revenue share. - You need streaming on Cardano. SockJS/STOMP topics for prices, per-asset feeds, and executed swaps, snapshot-then-updates, so no polling loop against your rate limit. - You want UTXO chains beyond Cardano from one vendor, today. Bitcoin (with ordinals and runes), Midnight (with transaction building), and Apex Fusion are live now, alongside Cardano. - Your compliance posture requires isolated infrastructure with a negotiated contractual SLA, which is the Dedicated tier's entire reason to exist. ### Bottom line Blockfrost is the better pure chain-data API: cheaper per request, deeper on core endpoints, open source, self-hostable, and ubiquitous, with the caveat of an unresolved dual-tip consistency edge case and an unusual amount of 2026 strategic uncertainty. Nexus is the better platform the moment your requirements climb above raw chain reads, because the climb is where Blockfrost stops entirely. Comparing more than these two? Maestro Alternatives for Bitcoin and Cardano walks the wider field, including the options for teams that also need Bitcoin coverage, and carries an endpoint-level migration map. Nexus is built by A.D. Labs, the team behind GeroWallet. The short version of this comparison, with the migration path, is on the Blockfrost alternative page . Evaluate it against your own traffic: Start the 7-day Builder trial , browse the full endpoint reference and live playground at nexus.gerowallet.io/docs , or talk to us about Enterprise and Dedicated via the support page . ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # Cardano Transaction Builder API: Unsigned CBOR | Nexus URL: https://nexus.gerowallet.io/blog/cardano-transaction-builder-api/ Description: Build Cardano transactions server-side: UTXO selection, fees, delegation, governance, and DEX swaps returned as unsigned CBOR. Keys stay client-side. Platform · Updated October 19, 2026 ## Cardano Transaction Builder API: Intent In, Unsigned CBOR Out ### Cardano Transaction Builder API: Intent In, Unsigned CBOR Out Building a valid Cardano transaction means solving UTXO selection, calculating fees, handling change outputs, respecting min-UTXO rules, and serializing it all to CBOR. Libraries help, but you still own the logic, the edge cases, and the maintenance as the protocol evolves through eras. For teams whose product is not "a transaction library," that is undifferentiated heavy lifting. The Nexus Transaction Builder inverts it: you send intent, Nexus returns an unsigned transaction. Your keys never leave your side. ### The flow, in three steps - Build. POST your intent, recipient and amount, a pool to delegate to, a governance action, to a builder endpoint. Nexus handles UTXO selection, fee calculation, and change outputs, and returns unsigned transaction CBOR. - Sign. Sign the CBOR client-side with your wallet, CIP-30 connector, or key material. Nexus never sees private keys; there is nothing on its servers to steal. - Submit. POST the signed CBOR to the submit endpoint. Done. ### What you can build Six operation families cover the transactions real Cardano products actually send: - Transfers , ADA and native-token payments, including multi-output sends. - Stake delegation , delegate to a pool. - Stake key registration , register or deregister a stake key. - DRep registration , register or deregister as a delegated representative (Conway era). - Vote delegation , delegate governance voting power. - Reward withdrawal , withdraw staking rewards. A utility endpoint also computes the maximum sendable ADA for an address after fees and min-UTXO requirements, the exact number wallet UIs need for a "Max" button. And swaps. The builder includes a DEX aggregator flow: list swappable tokens, quote a route across Cardano DEXes, build the unsigned swap transaction, and submit the signed result. That is a swap feature for your product in four REST calls. ### How it works # 1. Build an unsigned transfer curl -X POST "https://nexus.gerowallet.io/api/tx/build" \ -H "X-Api-Key: nxs_your_api_key_here" \ -H "Content-Type: application/json" \ -d '{ "sender": "addr1q9...", "outputs": [{ "address": "addr1qx...", "lovelace": "5000000" }] }' # → { "cbor": "84a400818258...", ... } # 2. Sign client-side (wallet / CIP-30) # 3. Submit the signed transaction curl -X POST "https://nexus.gerowallet.io/api/transactions/submit" \ -H "X-Api-Key: nxs_your_api_key_here" \ -H "Content-Type: application/cbor" \ --data-binary @signed-tx.cbor Because reads are consistent, a submitted transaction is queryable immediately, chained flows (build a second transaction spending the first one's output) behave predictably. ### What teams build with it - Wallets and dApps ship send, stake, vote, and swap features without maintaining a transaction-construction stack. - Exchanges and fintechs add Cardano withdrawals and delegation with server-side building and client-side signing, keeping keys inside their existing custody boundary. - Governance tools register DReps and delegate votes programmatically as Conway-era participation grows. - Backends in any language get CBOR-correct transactions from plain JSON over REST, with no Cardano-specific library required. ### Pricing Transaction Builder is a $19/month add-on on Builder ($29), Growth ($79), and Scale ($199), not on the $9 Starter tier, included in Enterprise ($499), drawing from your tier's unified request pool. The DEX aggregator swap flow is included with it. ### Build one today The 7-day Builder trial includes the full API surface. Get your key at nexus.gerowallet.io , build an unsigned transaction against preprod, and see the whole flow work before you commit a dollar. Transaction building is one of six products on the Nexus Cardano API . ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # Cardano Wallet Analytics API: FIFO P&L, Holdings | Nexus URL: https://nexus.gerowallet.io/blog/cardano-wallet-analytics-api/ Description: Query holdings with USD valuation, wallet value over time, and FIFO profit-and-loss for any Cardano stake address through one REST API. 7-day trial. Platform · Updated October 19, 2026 ## Cardano Wallet Analytics API: Holdings, History, and FIFO P&L for Any Stake Address ### Cardano Wallet Analytics API: Holdings, History, and FIFO P&L for Any Stake Address Raw chain data tells you what a wallet did. It does not tell you what the wallet is worth, how that value has moved, or whether the owner is up or down on any given token. That second layer, holdings valuation, value history, and profit-and-loss, is derived data, and deriving it is real work: you have to reconstruct positions over time, match every disposal against prior acquisitions, and mark remaining holdings to current market prices. Portfolio trackers, tax tools, and institutional reporting products all need this layer, and most end up building it in-house on top of a raw chain API. The Nexus Wallet Analytics add-on provides it as an endpoint. ### What you can query Everything keys off a Cardano stake address: - Current holdings , every asset a wallet holds, including ADA, with USD valuation. - Value history , the wallet's total value over time, ready to chart. - Single-wallet P&L , realized and unrealized gains and losses per token. - Multi-wallet P&L , FIFO profit-and-loss for a batch of stake addresses in one POST request, for products tracking many wallets at once. ### How the P&L is computed The accounting model matters, so it is worth stating precisely: P&L is computed FIFO (first-in, first-out). Each disposal is matched against the earliest acquisitions to derive cost basis and realized gains; holdings still in the wallet are marked to current market price for unrealized P&L. FIFO is the cost-basis convention most tax regimes and reporting standards expect, which is exactly why it is the wrong thing to improvise in-house. ### How it works # Single-wallet P&L curl "https://nexus.gerowallet.io/api/wallet/stake1u9.../pnl" \ -H "X-Api-Key: nxs_your_api_key_here" # Multi-wallet P&L in one request curl -X POST "https://nexus.gerowallet.io/api/wallet/pnl" \ -H "X-Api-Key: nxs_your_api_key_here" \ -H "Content-Type: application/json" \ -d '{ "stakeAddresses": ["stake1u9...", "stake1uy..."] }' Plain REST, the same X-Api-Key header as every other Nexus endpoint, full schemas in the API reference . Valuations lean on the same market data layer that indexes all 11 Cardano DEXes, so prices reflect real aggregate liquidity rather than a single pool. ### What teams build with it - Portfolio trackers render holdings, value charts, and per-token P&L without building a position engine. - Tax and accounting tools get FIFO cost-basis numbers aligned with what reporting standards expect. - Wallets add a "your performance" view that most Cardano wallets simply do not have. - Funds and institutional desks monitor fleets of addresses through the multi-wallet endpoint instead of iterating one by one. ### Pricing Wallet Analytics is a $15/month add-on on Builder ($29), Growth ($79), and Scale ($199), not on the $9 Starter tier, included in Enterprise ($499), sharing your tier's unified request pool. Nexus is the only Cardano data API that offers wallet P&L as an endpoint today. ### Point it at a real wallet The most direct evaluation is to run your own stake address through it. The 7-day Builder trial includes the full API surface: get your key at nexus.gerowallet.io and see what your wallet's FIFO P&L actually looks like. Wallet analytics is one of six products on the Nexus Cardano API . ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # Cardano WebSocket API: Real-Time Prices & Swaps | Nexus URL: https://nexus.gerowallet.io/blog/cardano-websocket-api/ Description: Stream live Cardano token prices, DEX swap events, and dApp events over STOMP WebSockets instead of polling. Snapshot on subscribe, then live updates. Platform · Updated July 29, 2026 ## Cardano WebSocket API: Live Prices, Swaps, and dApp Events Without Polling ### Cardano WebSocket API: Live Prices, Swaps, and dApp Events Without Polling Polling is the tax you pay for not having a stream: request quota burned asking "anything new?", latency equal to your polling interval, and rate limits shaping your product's responsiveness. For live charts, trading interfaces, alerting, and dashboards, push beats pull. Nexus exposes a real-time WebSocket at wss://nexus.gerowallet.io/ws/market , SockJS transport, STOMP protocol, authenticated with the same API key as the REST surface. ### What you can subscribe to Topic | What streams | /topic/market/prices | All token prices, a current snapshot on subscribe, then live updates | /topic/market/prices/{assetId} | One token's price, snapshot first, then updates | /topic/swaps | Global DEX swap events: executed swaps, cancellations, limit-order fills | /topic/dapp/{id}/events | Events for a registered dApp blueprint | The snapshot-then-updates pattern matters in practice: your UI renders immediately with current state and then stays current, with no separate "initial load" REST call to reconcile. ### How it works import SockJS from 'sockjs-client'; import { Client } from '@stomp/stompjs'; const client = new Client({ webSocketFactory: () => new SockJS('https://nexus.gerowallet.io/ws/market?access_token=nxs_your_api_key_here'), onConnect: () => { client.subscribe('/topic/market/prices/lovelace', (msg) => console.log('price', JSON.parse(msg.body)), ); client.subscribe('/topic/swaps', (msg) => console.log('swap', JSON.parse(msg.body)), ); }, }); client.activate(); Authentication happens at the handshake via an access_token query parameter or a bearer header. Each delivered message counts toward your monthly message quota, and an unsubscribe control ( /app/market/unsubscribe ) lets you drop per-token streams you no longer need, subscribe to what you use, not everything. ### What teams build with it - Trading UIs and charts update tick-by-tick from the price topics instead of hammering a REST endpoint on an interval. - Alerting and bots react to executed swaps and limit-order fills from the global swap feed as they happen. - dApp backends consume their own blueprint event stream rather than re-scanning the chain. - Dashboards stay live all day on one persistent connection instead of thousands of polls. The streams pair naturally with the Market Data add-on : REST for history and depth, WebSocket for now. ### Pricing and access Scale ($199) and Enterprise ($499) plans include WebSocket streaming with the plan's own connection and message limits; Enterprise includes WS Unlimited. On Builder and Growth, attach a package per API key: Package | Concurrent connections | Messages / month | Price | WS Starter | 2 | 100,000 | $29/mo | WS Pro | 10 | 2,000,000 | $59/mo | WS Unlimited | Unlimited | Unlimited | $99/mo | If real-time market data matters to your product, Nexus is currently the only managed way to stream it on Cardano. ### Open a connection today The 7-day Builder trial plus a WS package gets you a live stream in an afternoon. Get your key at nexus.gerowallet.io , subscribe to a price topic, and watch the updates arrive. WebSocket streaming is one of six products on the Nexus Cardano API . ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # Nexus API: Full-Stack Cardano Data on One Platform URL: https://nexus.gerowallet.io/blog/nexus-api-overview/ Description: What the Nexus API includes: market data across 11 Cardano DEXes, FIFO wallet analytics, a transaction builder, WebSocket streaming, and an MCP server. Platform · Updated November 3, 2026 ## Inside the Nexus API: Market Data, Wallet Analytics, Transactions, and Streaming on One Platform ### Inside the Nexus API: Every Capability on One Platform Most Cardano data providers answer one question: "what happened on chain?" Real products need more, what a token is worth, what a wallet has earned, how to construct the next transaction, and what is happening right now. Nexus answers all of them through a single API, over plain REST with an OpenAPI 3.1 spec, so the whole protocol is HTTPS plus an X-Api-Key header. This post is the map of what that key unlocks. ### The platform in one paragraph Nexus is a managed, full-stack data and transaction API for UTXO chains. Cardano has the deepest coverage, and Bitcoin and Midnight are live behind the same account and auth header. The Bitcoin surface, chain data, fees, mempool, ordinals and runes, gets a full walkthrough in Bitcoin Data Infrastructure: What Your App Actually Needs . Every request fans out across multiple providers, Yaci, Koios, Blockfrost, and Nexus's own indexers, with per-provider health checks routing around degraded upstreams, and hot data served from cache. You integrate once and inherit the redundancy. ### Market Data: prices, candles, pools, and order books The Market Data add-on aggregates all 11 Cardano DEXes (Minswap V1/V2, SundaeSwap V1/V3, WingRiders V1/V2, VyFi, Splash, TeddySwap, MuesliSwap, CSwap) into one surface: current and historical token prices, OHLCV candles (15m, 1h, 1D, 1W), an RSI(14) technical indicator, pool TVL and reserves, real and AMM-simulated order books, recent swaps, top-trader rankings, and NFT collection stats including floor prices and sales from jpg.store. ### Wallet Analytics: holdings, history, and FIFO P&L Point the API at any Cardano stake address and get current holdings with USD valuation, wallet value over time, and realized plus unrealized profit-and-loss computed on a FIFO cost basis, single wallet or multi-wallet in one request. This is the layer portfolio trackers, tax tooling, and reporting products otherwise have to build themselves. ### Transaction Builder: intent in, unsigned CBOR out Send intent, recipient and amount, a delegation, a governance vote, and Nexus returns an unsigned transaction CBOR with UTXO selection, fee calculation, and change outputs handled server-side. You sign client-side and submit; private keys never touch Nexus servers. Builders cover transfers, stake delegation, stake key registration, DRep registration, vote delegation, and reward withdrawal. ### DEX Aggregator: best-route swaps as an API The Nexus DEX aggregator turns a token swap into four REST calls: list the swappable tokens, quote the best route across Cardano's DEXes, build the unsigned swap transaction, and submit the signed result. Routing, price impact, and CBOR construction happen server-side; signing stays entirely with your users. It ships as part of the Transaction Builder add-on, so a full swap feature for your wallet, bot, or dApp goes live without a single line of DEX-specific integration code. ### WebSocket Streaming: live data without polling A SockJS + STOMP endpoint streams live token prices, executed DEX swaps, and dApp events. Subscribe to a topic and receive a snapshot plus updates instead of polling on a loop. Enterprise includes streaming; on Builder, Growth, and Scale, the WS Starter, WS Pro, and WS Unlimited packages add it. ### MCP Server: your AI agents, connected to the chain Nexus hosts a Model Context Protocol endpoint that turns the platform into native tools for Claude, Cursor, and any MCP-compatible agent, 25 tools across Cardano, Bitcoin, Midnight, market data, transaction building, and account management, authenticated with the same API key. ### Pricing that reads like a menu, not a formula Every plan is a flat monthly price with a request pool. A request is a request: no compute-unit weighting, no per-method credit taxes, no surprise bills at month end. #### Base tiers Tier | Price | Requests / month | Highlights | Starter | $9/mo | 3,000,000 | Core API only, no add-ons, 2 API keys | Builder | $29/mo | 10,000,000 | 7-day trial, 4 API keys | Growth | $79/mo | 30,000,000 | 7 API keys | Scale | $199/mo | 50,000,000 | 13 API keys, priority support | Enterprise | $499/mo | 200,000,000 | Unlimited API keys, every add-on bundled, WS Unlimited included | Dedicated | from $2,000/mo | negotiated | Isolated infrastructure, contractual SLA, dedicated support channel | #### Add-ons Pick only what you need; REST add-ons share your tier's request pool, so there is one number to track. Add-on | Price | What it adds | Market Data | +$19/mo | Prices, candles, pools, order books, and NFT sales across all 11 Cardano DEXes | Wallet Analytics | +$15/mo | Holdings, value history, and FIFO P&L per stake address | Transaction Builder | +$19/mo | Server-side transaction building, including the DEX aggregator swap flow | MCP Server | +$19/mo | Hosted MCP endpoint for Claude, Cursor, and other AI agents | IPFS | +$5/mo | Gateway fetch, content inspection, IPNS, and per-key pinning | #### WebSocket streaming Included with Enterprise. On Builder, Growth, and Scale, add a package: Package | Price | Concurrent connections | Messages / month | WS Starter | $29/mo | 2 | 100,000 | WS Pro | $59/mo | 10 | 2,000,000 | WS Unlimited | $99/mo | Unlimited | Unlimited | On top of all of it, holding $GERO unlocks a sliding subscription discount of up to 20%. ### Start building The 7-day Builder trial exposes the full surface, so you can validate data quality and latency against your own workload before committing budget. Get your API key at nexus.gerowallet.io , or explore every endpoint with the live playground at nexus.gerowallet.io/docs . For Enterprise and Dedicated plans, reach out via the Nexus support page . ### Build with Nexus One Cardano integration for market data, wallet analytics, transactions, and streaming. Get started free Read the API docs --- # Cardano & Bitcoin API Guides: Nexus Blockchain API URL: https://nexus.gerowallet.io/blog/ Description: Guides, comparisons, and deep dives on building with Cardano data APIs - market data, wallet analytics, transactions, and streaming - from the Nexus team. ## Blog Guides, comparisons, and deep dives on building with Cardano data APIs. Latest · November 2, 2026 ### Solada Markets, Powered by Nexus: How a Cardano Launchpad Added Best-Price Swaps Solada and GeroWallet are now partners. Solada Markets runs on the Nexus swap widget and market kit, and Nexus Market Data indexes Solada launchpad tokens from the curve to the pool. Read article - November 2, 2026 ### Cardano API Providers Compared: How to Choose a Data and Transaction Layer A practical guide to Cardano API providers after Maestro's exit: what Blockfrost, Koios and Nexus each cover, how they price, and how to choose a data layer for production. Read article - October 15, 2026 ### Bitcoin Runes and Ordinals API: Inscriptions, Rune Balances and Safe UTXOs How to read Bitcoin runes balances, ordinals inscriptions and inscription-aware UTXOs through an API, with endpoint examples and the one mistake that burns inscriptions. Read article - October 15, 2026 ### TapTools API Alternative: Cardano Market Data After the Wind-Down TapTools wound down in June 2026 and its API no longer responds. Here are the realistic options for Cardano token prices, candles, DEX and NFT data, with an endpoint migration map. Read article - September 29, 2026 ### Onboarding to a Cardano Data API: From Signup to First Call What onboarding to a Cardano data API involves, what to evaluate before you commit, and the exact steps from Nexus signup to your first authenticated call. Read article - September 29, 2026 ### Nexus vs Koios: Managed Full-Stack API or Community-Run Endpoint? Nexus vs Koios, compared by engineers who run both: query model, cluster architecture, tiers, timeouts, SLAs and price. Re-verified September 2026. Read article - September 14, 2026 ### Nexus vs Maestro: Cardano-First Data API or Bitcoin-First dApp Platform? A deep technical comparison of Nexus and Maestro: Cardano API surface, credit-based vs flat pricing, reliability data, and the Bitcoin pivot, verified September 2026. Read article - August 19, 2026 ### Maestro Alternatives for Bitcoin and Cardano Looking for a Maestro alternative? Five realistic options for Bitcoin and Cardano APIs compared, what to verify before you switch, and an endpoint-level migration map. Read article - August 19, 2026 ### Bitcoin Data Infrastructure: What Your App Actually Needs A builder's guide to Bitcoin data infrastructure: chain tip and reorgs, UTXO sets, fee estimation, mempool, ordinals and runes, and how to choose between running a node and buying an API. Read article - August 10, 2026 ### Cardano Market Data API: Prices, Candles, and Order Books Across All 11 DEXes Token prices, OHLCV candles, DEX pools, order books, swap history, and NFT stats across all 11 Cardano DEXes through one REST API. Start a 7-day trial. Read article - August 1, 2026 ### Nexus MCP Server: Connect Claude and AI Agents to Cardano Data Give Claude, Cursor, and any MCP agent 25 native blockchain tools: Cardano data, market prices, Bitcoin, Midnight, and transaction building via one platform. Read article - July 30, 2026 ### Nexus vs Blockfrost: A Full-Stack Data API Compared to the Cardano Incumbent A deep technical comparison of Nexus and Blockfrost: API surface, architecture, rate limits, pricing math, and reliability, verified July 2026. Read article - July 23, 2026 ### Cardano Transaction Builder API: Intent In, Unsigned CBOR Out Build Cardano transactions server-side: UTXO selection, fees, delegation, governance, and DEX swaps returned as unsigned CBOR. Keys stay client-side. Read article - July 9, 2026 ### Cardano Wallet Analytics API: Holdings, History, and FIFO P&L for Any Stake Address Query holdings with USD valuation, wallet value over time, and FIFO profit-and-loss for any Cardano stake address through one REST API. 7-day trial. Read article - July 7, 2026 ### Cardano WebSocket API: Live Prices, Swaps, and dApp Events Without Polling Stream live Cardano token prices, DEX swap events, and dApp events over STOMP WebSockets instead of polling. Snapshot on subscribe, then live updates. Read article - July 5, 2026 ### Inside the Nexus API: Market Data, Wallet Analytics, Transactions, and Streaming on One Platform What the Nexus API includes: market data across 11 Cardano DEXes, FIFO wallet analytics, a transaction builder, WebSocket streaming, and an MCP server. Read article --- # Nexus: Multi-chain Blockchain Data & Transaction API URL: https://nexus.gerowallet.io/ Description: Nexus, by A.D. Labs, is a managed multi-chain data API for Cardano, Midnight, and Bitcoin: multi-provider failover, OpenAPI 3.1, one account across chains. CARDANO BITCOIN MIDNIGHT ## Three chains. One API surface. Chain data, market data and transactions for Cardano, Bitcoin and Midnight, on one surface. Get an API key Price your plan From $ 9 a month. 7 -day free trial on Builder. Or read the docs . BITCOIN block 921,455 CARDANO epoch 646 · 13,768,412 MIDNIGHT block 1,204,338 NEXUS one endpoint, every primitive Chain API REST GET /api/blocks/latest 13,768,412 GET /api/btc/chain/tip 921,455 GET /api/midnight/…/info 1,204,338 200 OK · p50 41 ms · failover on Streaming WSS block 13768412 0.4s tx 4f9c…d21a mempool utxo shielded +1 tx 5c81…7ad2 confirmed block 13768412 0.4s tx 4f9c…d21a mempool utxo shielded +1 tx 5c81…7ad2 confirmed blocks, txs, mempool · 3 chains MCP Server AGENTS ▸ nexus.btc_address_ordinals address: bc1q…8f4z → 3 inscriptions · 2 runes tool call · 24 ms DEX Routing QUOTE 1,000 ₳ → $GERO Minswap 111,640 Splash 111,205 impact 0.31% min out 111,082 Ordinals & Runes BTC GET /addresses/ {a} /ordinals #82,441,907 +2 UNCOMMON•GOODS 12,400 3 inscriptions · 2 runes Fees & Mempool BTC 3.2 fast 2.1 med 1.4 slow sat/vB mempool 14,208 tx · 8.4 vMB Dust Generation MIDNIGHT 12,000 NIGHT 5 DUST / NIGHT 49,400 / 60,000 DUST 7d to capacity registered · shielded fees Shielded UTXOs MIDNIGHT UNSHIELDED mn_shield…9fzk 4,200 SHIELDED hidden DUST REG intent 3f81…9c2 yes zswap · proof verified · 41 ms CARDANO BITCOIN MIDNIGHT Three chains. One API surface. Chain data, market data and transactions for Cardano, Bitcoin and Midnight, on one surface. Get an API key Price your plan From $ 9 a month. 7 -day free trial on Builder. Or read the docs . NEXUS one endpoint, every primitive Chain API REST GET /api/blocks/latest 13,768,412 GET /api/btc/chain/tip 921,455 GET /api/midnight/…/info 1,204,338 200 OK · p50 41 ms · failover on Streaming WSS block 13768412 0.4s tx 4f9c…d21a mempool utxo shielded +1 tx 5c81…7ad2 confirmed block 13768412 0.4s tx 4f9c…d21a mempool utxo shielded +1 tx 5c81…7ad2 confirmed blocks, txs, mempool · 3 chains MCP Server AGENTS ▸ nexus.btc_address_ordinals address: bc1q…8f4z → 3 inscriptions · 2 runes tool call · 24 ms DEX Routing QUOTE 1,000 ₳ → $GERO Minswap 111,640 Splash 111,205 impact 0.31% min out 111,082 Ordinals & Runes BTC GET /addresses/ {a} /ordinals #82,441,907 +2 UNCOMMON•GOODS 12,400 3 inscriptions · 2 runes Fees & Mempool BTC 3.2 fast 2.1 med 1.4 slow sat/vB mempool 14,208 tx · 8.4 vMB Dust Generation MIDNIGHT 12,000 NIGHT 5 DUST / NIGHT 49,400 / 60,000 DUST 7d to capacity registered · shielded fees Shielded UTXOs MIDNIGHT UNSHIELDED mn_shield…9fzk 4,200 SHIELDED hidden DUST REG intent 3f81…9c2 yes zswap · proof verified · 41 ms Nexus vs Blockfrost, Cardano mainnet ### New Cardano blocks reach you 6.7 x sooner In an August 2026 test, Nexus served each new Cardano block a median 575 ms after its timestamp. Blockfrost took 3,845 ms . Both APIs were polled side by side, from one machine, at the same rate. Your dApp sees a new block about 3 seconds sooner. Switch from Blockfrost in one line Read the full Blockfrost comparison Time from block timestamp to served, median Nexus 575 ms Blockfrost 3,845 ms 0 s 1 s 2 s 3 s 4 s - 102 of 107 contested blocks Nexus served first - 3.0 s median lead when Nexus was first - 119 blocks raced over 45 minutes, 2 polls a second each Measured 14 August 2026 from a single client in Frankfurt against both APIs over the public internet, 119 blocks over 45 minutes at matched request rates. Method and raw data available on request. ### Six products on one API One base URL and one auth header across Cardano, Midnight, and Bitcoin. Each API key is scoped to a single chain and network, and market data, wallet analytics, transaction building, and MCP are add-ons, sold alone or in bundles. #### Blockchain API Blocks, txs, addresses & assets Ten endpoint groups, accounts to governance, plus submit and evaluate. #### WebSocket Streaming Live blocks & txs, pushed to you Push, not poll: market data on a 10 second cadence, Blueprints with REST backfill. #### Transaction Building Build & submit on-chain Transfers, staking, and Conway governance built server-side. Unsigned CBOR out; keys never touch Nexus. #### DEX Aggregator Best-price swap routing Best-price routing across Minswap, WingRiders, Splash, and SaturnSwap. You sign every swap. #### MCP Server Nexus data for AI agents A hosted MCP endpoint: AI agents query Cardano, Bitcoin, and Midnight with your own key. #### Market Data Prices, pools & tokens See it live on Cardano Market → Prices, candles, pools, order books, and NFT sales across all 11 indexed DEXes. ### Partners, customers, and design partners - Design partner - Open-source partner - Network partner - SongMarketCap Integration partner - Integration partner - Community integration partner Pricing ### Build your Nexus plan and see the price Nexus plans cost $ 9 to $ 499 a month, flat, with no per-call metering. Pick a tier, add only what you use, and the total updates as you go. - Starter from $9/mo - 7-day free trial on Builder - Add-ons on every tier - Cancel anytime #### Base Tier Select your plan tier. Starter $ 9 /mo 3M req/mo · 2 API keys 10 req/s · burst 100 Builder $ 29 /mo 10M req/mo · 4 API keys 25 req/s · burst 250 Growth $ 79 /mo 30M req/mo · 7 API keys 50 req/s · burst 500 Scale $ 199 /mo 50M req/mo · 13 API keys 100 req/s · burst 1,000 Enterprise $ 499 /mo 200M req/mo · Unlimited API keys 500 req/s · burst 5,000 #### Bundles Add-ons that work together, for less. One bundle per plan. Data Market Data + Wallet Analytics +$ 19 /mo $ 34 Build + AI Transaction Builder + MCP Server +$ 19 /mo $ 38 Complete Market Data + Wallet Analytics + Transaction Builder + MCP Server +$ 29 /mo $ 72 #### Add-Ons REST add-ons share your tier's unified request pool, one number to track. Market Data Prices, OHLCV candles, DEX pools, order books, and NFT sales across all 11 Cardano DEXes. +$19/mo Wallet Analytics Holdings, transaction history, and FIFO-based P&L per wallet. +$15/mo Transaction Builder Server-side UTXO selection, fee calc, and unsigned CBOR for transfers, staking, and governance. +$19/mo MCP Server Model Context Protocol endpoint: connect Claude and other AI agents directly to Nexus data + tools. +$19/mo IPFS Resolve, inspect, and pin IPFS content through Nexus’ self-hosted node: gateway fetch, stat/ls, IPNS resolve, and per-key pinning. +$5/mo #### WebSocket Streaming Live market data via STOMP. Pick a package or skip entirely. No WebSocket REST only. Add streaming later if needed. Free WS Starter 2 concurrent connections · 100,000 messages / month +$29/mo WS Pro 10 concurrent connections · 2,000,000 messages / month +$59/mo WS Unlimited Unlimited concurrent connections and messages +$99/mo Growth monthly total $ 79.00 Continue → #### Price Summary Growth tier $ 79.00 Monthly Total $ 79.00 Annual Total (×12) $ 948.00 /yr Continue to Billing → #### $GERO staking discount Hold $GERO to save up to 20% Hold $GERO GeroWallet's native Cardano token. Holding $GERO in any Cardano wallet automatically unlocks Nexus API discounts, Gero Card fee waivers, and on-chain governance voting. to unlock a sliding discount on your Nexus subscription, from 5% at $50 staked up to 20% at $1,000+. Connect your Cardano wallet to preview your qualifying tier now. Connect Cardano Wallet → #### Dedicated infrastructure Your own cluster, physical data isolation and a contractual SLA. From $2,000 a month. Contact us → #### Every plan side by side Limits, add-on details and the pricing FAQ. Compare every Nexus plan → ### Three chains, one account Each API key is scoped to one chain and one network. Same base URL, same auth header. #### Cardano The deepest surface: chain data, DEX market data, wallet P&L, transaction building, and WebSocket streaming. Explore the Cardano API #### Midnight Network info, unshielded transaction build and submit, and DUST registration, live on the same account. Explore the Midnight API #### Bitcoin Chain data including ordinals, runes, and mempool, live on the same account. Explore the Bitcoin API ### Enterprise-grade Cardano data infrastructure , extended to Bitcoin & Midnight Provider redundancy, aggressive caching, and a unified API surface across every chain we support. Building on Cardano? See the full Cardano API surface. #### One endpoint, several upstreams Every request is served behind Yaci, Koios, Blockfrost, and our own indexers. Per-provider health checks pick a healthy upstream for each call, so a degraded source is routed around instead of reaching your app. See live provider status #### Aggressive Caching Hot blockchain data is served from cache so repeat queries are fast and your provider quotas last. #### Usage analytics Per-key request counts, allowed versus rejected breakdowns, and usage history in the dashboard. #### GERO Token Benefits Hold GERO tokens for discounts and enhanced API limits. #### Comprehensive Data Access blockchain, DeFi, NFT, and market data through unified APIs. #### Non-custodial by design Nexus never holds private keys: transactions are built unsigned and signed client-side. See the privacy policy for how account and usage data is handled. ### One platform for every chain and every capability Market data, wallet analytics, transactions, and WebSocket streaming. Official TypeScript SDK, plain REST for every other language, OpenAPI 3.1 spec for the rest. TypeScript SDK cURL JavaScript Java Python // npm install @adlabs/nexus (official SDK, zero runtime dependencies) import { NexusClient } from "@adlabs/nexus"; const nexus = new NexusClient({ apiKey: process.env.NEXUS_API_KEY! }); // Cardano chain data const utxos = await nexus.cardano.addresses.utxos("addr1..."); const pool = await nexus.cardano.pools.byId("pool1..."); // Cardano market data (mainnet) const prices = await nexus.cardano.market.prices(); // Bitcoin and Midnight, same client const tip = await nexus.bitcoin.chain.tip(); const info = await nexus.midnight.info.get("undeployed"); // Typed end to end: request + response types are generated // from the live Nexus OpenAPI spec and ship with the package. ##### Official TypeScript SDK → @adlabs/nexus on npm: typed, zero dependencies, MIT. Cardano, Bitcoin, and Midnight in one client. #### Why Choose Nexus? ##### Official TypeScript SDK npm install @adlabs/nexus: a typed, zero-dependency client for Cardano chain and market data, Bitcoin, and Midnight. Types are generated from the live OpenAPI spec. MIT, open source on GitHub. ##### Plain REST, any language HTTPS + an X-Api-Key header is the whole protocol. Works with the HTTP client built into Node, the JDK, Python, Go, Rust, or your shell. No SDK required. ##### OpenAPI 3.1 spec included A full machine-readable spec is published at /v3/api-docs and rendered with a live playground at /docs. Generate a typed client for 50+ languages with one openapi-generator command. ##### Multi-provider failover Every request is served behind Yaci, Koios, Blockfrost, and our own indexers, with health checks routing around degraded upstreams. When one goes down, your app keeps serving. ##### One account, every chain Each API key is scoped to one chain and one network (Cardano, Bitcoin, and Midnight), all under the same base URL and the same Nexus account. One dashboard, one bill, no separate providers to juggle. ##### Read the full reference → Every endpoint, parameter, and response shape, with a live playground built into each page. Built by the GeroWallet team ### The platform behind GeroWallet Nexus is built and run by A.D. Labs LTD , the team behind GeroWallet, the non-custodial Cardano and Midnight wallet. The wallet's market data, swap routing and transaction building run on this API in production, so the endpoints you integrate are the ones we depend on ourselves. Who builds Nexus → GeroWallet Runs on Nexus in production See GeroWallet - Swap routing GeroWallet's DEX aggregator quotes and builds every swap through the Nexus swap API. - Market data The wallet’s Market tab reads prices, candles and order books from the same Nexus feed you get on a Cardano key. - Transaction building Transfers and swaps in the wallet are built server-side by the Nexus transaction builder. ### Frequently asked questions Everything you need to know about the Nexus API. What is Nexus? Nexus is a managed multi-chain data and transaction API. Each API key is scoped to one chain and one network, and every chain runs on one account, one base URL, and one auth header. On Cardano that surface covers chain data, with add-ons that enable market data across all 11 DEXes, FIFO wallet analytics, and a transaction builder. Live WebSocket streaming is a separate package. Everything is plain REST with an OpenAPI 3.1 spec, so you never have to run blockchain infrastructure yourself. Which blockchains does Nexus support? Cardano, Bitcoin, and Midnight are all live today. Cardano has the deepest coverage: chain data, DEX market data, wallet analytics, transaction building, and streaming. Bitcoin covers addresses, blocks, fees, mempool, ordinals inscriptions and runes, and transaction submit. Midnight covers network info, unshielded transaction build and submit, and DUST registration. Each API key is scoped to one chain and one network, so you integrate once and add chains without re-architecting. How is Nexus different from Blockfrost, Maestro, or Koios? Those APIs focus on raw Cardano chain queries. Nexus adds a full stack on the same Cardano API surface: DEX market data, FIFO profit-and-loss wallet analytics, and a server-side transaction builder as opt-in add-ons, with live WebSocket streaming as its own package. All of it sits behind multi-provider failover for redundancy and flat, predictable pricing. In an August 2026 test from a single client in Frankfurt, Nexus served new Cardano blocks a median 575 ms after their timestamp, against 3,845 ms on Blockfrost. Who builds Nexus? Nexus is built and operated by A.D. Labs LTD, the team behind GeroWallet, the non-custodial Cardano and Midnight wallet. GeroWallet runs on Nexus in production: its market data, swap routing, and transaction building all go through this API. Nexus is a separate product with its own plans, and you do not need the wallet to use it. How much does Nexus cost? Flat monthly plans, no per-call metering. Starter is $9 for 3M requests a month, Builder $29 for 10M with a 7-day trial, Growth $79 for 30M, Scale $199 for 50M, and Enterprise $499 for 200M with every add-on included. Add-ons start at $5, and bundles cover several for $19 or $29. --- # Cardano API for Chain Data, Markets & Transactions: Nexus URL: https://nexus.gerowallet.io/cardano/ Description: Full-stack Cardano REST API by A.D. Labs: chain data with failover, DEX market data, wallet P&L, tx building, and WebSocket streaming. 7-day trial. CARDANO ## The full-stack Cardano API chain data, market data, and transactions on one surface Get an API key Read the docs CARDANO NODE 13,768,41 2 3 4 5 2 epoch 646 · slot 193,760,112 NEXUS one endpoint, every primitive Chain API REST GET /api/blocks/latest { "height" : 13768412 , "epoch" : 646 , "slot" : 193760112 , "tx_count" : 27 } 200 OK · provider failover on Streaming WSS block 13768412 0.4s tx 9f3a…c21e mempool tx 5c81…7ad2 confirmed block 13768413 0.6s block 13768412 0.4s tx 9f3a…c21e mempool tx 5c81…7ad2 confirmed block 13768413 0.6s subscribed: blocks, txs, mempool Tx Builder UTXO ₳ 420.11 ₳ 89.40 ₳ 500.00 ₳ 9.34 change fee ₳ 0.17 | 2 in, 2 out | balanced DEX Routing QUOTE 1,000 ₳ → $GERO Minswap 111,640 Splash 111,205 SundaeSwap 110,870 impact 0.31% · fee 0.10% min out 111,082 MCP Server AGENTS ▸ nexus.address_utxos address: addr1q…9fzk → 14 utxos · ₳ 512.40 tool call · 21 ms Market Data LIVE $GERO $0.004281 ▲ 3.1% 1h candles vol ₳ 182K CARDANO The full-stack Cardano API chain data, market data, and transactions on one surface Get an API key Read the docs CARDANO NODE 13,768,41 2 3 4 5 2 epoch 646 · slot 193,760,112 NEXUS one endpoint, every primitive Chain API REST GET /api/blocks/latest { "height" : 13768412 , "epoch" : 646 , "slot" : 193760112 , "tx_count" : 27 } 200 OK · provider failover on Streaming WSS block 13768412 0.4s tx 9f3a…c21e mempool tx 5c81…7ad2 confirmed block 13768413 0.6s block 13768412 0.4s tx 9f3a…c21e mempool tx 5c81…7ad2 confirmed block 13768413 0.6s subscribed: blocks, txs, mempool Tx Builder UTXO ₳ 420.11 ₳ 89.40 ₳ 500.00 ₳ 9.34 change fee ₳ 0.17 | 2 in, 2 out | balanced DEX Routing QUOTE 1,000 ₳ → $GERO Minswap 111,640 Splash 111,205 SundaeSwap 110,870 impact 0.31% · fee 0.10% min out 111,082 MCP Server AGENTS ▸ nexus.address_utxos address: addr1q…9fzk → 14 utxos · ₳ 512.40 tool call · 21 ms Market Data LIVE $GERO $0.004281 ▲ 3.1% 1h candles vol ₳ 182K ### Six products on one API Each API key is scoped to one chain and one network. Market data, wallet analytics, transaction building, and MCP are add-ons, sold alone or in bundles. #### Blockchain API Blocks, txs, addresses & assets Ten endpoint groups, accounts to governance, plus submit and evaluate. #### WebSocket Streaming Live blocks & txs, pushed to you Push, not poll: market data on a 10 second cadence, Blueprints with REST backfill. #### Transaction Building Build & submit on-chain Transfers, staking, and Conway governance built server-side. Unsigned CBOR out; keys never touch Nexus. #### DEX Aggregator Best-price swap routing Best-price routing across Minswap, WingRiders, Splash, and SaturnSwap. You sign every swap. #### MCP Server Nexus data for AI agents A hosted MCP endpoint: AI agents query Cardano, Bitcoin, and Midnight with your own key. #### Market Data Prices, pools & tokens See it live on Cardano Market → Prices, candles, pools, order books, and NFT sales across all 11 indexed DEXes. ### Nexus Cardano API at a glance 11 Cardano DEXes indexed for first-party market data 3 Cardano networks on the same endpoints: mainnet, preprod, preview Multi-provider failover across Yaci, Koios, Blockfrost, and our own indexers OpenAPI 3.1 machine-readable spec published at /v3/api-docs Public status page with live health for core subsystems ### Cardano chain data: every endpoint group on one REST API A Cardano REST API over plain HTTPS, with an official TypeScript SDK (@adlabs/nexus) and an OpenAPI 3.1 spec that generates typed clients for every other language. Ten endpoint groups cover the chain end to end. The same endpoints serve mainnet, preprod, and preview, each with its own scoped key. # Transaction history for a Cardano address, mainnet BASE="https://nexus.gerowallet.io/api" ADDR="addr1q9x2..." curl "$BASE/addresses/$ADDR/transactions/history?network=mainnet" \ -H "X-Api-Key: nxs_your_api_key_here" One auth header, one ?network= parameter: mainnet, preprod, and preview on the same endpoints. Each key is scoped to one chain and one network. #### Accounts Stake accounts, rewards history, and delegation state per stake address. View in docs → #### Addresses Balances, UTXOs, and full transaction history, including payment-credential and slot-window queries. View in docs → #### Assets and holders Native tokens and NFTs with metadata, mint history, and holder lists. View in docs → #### Blocks Block by hash or height, the latest block, and the transactions inside it. View in docs → #### Epochs and parameters Epoch summaries and the live protocol parameters that price your transactions. View in docs → #### Pools, enriched Stake pool queries with ticker, ROS, and metadata from a dedicated chain-data pipeline. View in docs → #### DReps and governance DReps, governance proposals, votes, the constitutional committee, and the constitution. View in docs → #### Scripts and datums Plutus and native scripts, script CBOR, and datum lookups by hash. View in docs → #### Transactions A rich single-call transaction object, batch endpoints, and raw CBOR when you need the bytes. View in docs → #### Submit and evaluate Broadcast signed transactions and evaluate execution units before you spend. View in docs → ### Cardano WebSocket API : live streaming and Blueprints Subscribe over WebSocket for live chain and market events, on the same account and the same base URL as your chain reads. #### WebSocket streaming Push, not poll. One connection Hold a single socket instead of firing thousands of requests. 10 second cadence Market-data topics broadcast on a fixed interval. Capacity of its own Connection and message allowances come as WebSocket packages you attach to a plan, so streaming scales independently of your REST quota. #### Blueprints Describe what to watch. Nexus delivers the matching events. Self-serve On-chain event streams you define yourself. UTXO or TRANSACTION Pick the granularity your consumer actually needs. REST backfill on every stream Reconnect and replay exactly the events you missed, instead of resyncing from scratch. Streaming pipelines break on reconnect, not on the happy path. Backfill is what makes an event stream safe to build settlement logic on. Streaming endpoints and Blueprint schemas are documented in the API reference . ### First-party Cardano market data on the same API Chain-data APIs like Blockfrost and Koios do not serve DEX market data. The market-data specialists we know of do not serve chain data. Nexus serves both. One base URL, one auth header: read a UTXO, then read the candle chart for the token inside it. Market Data add-on: 11 Cardano DEXes indexed first-party, normalized into one surface. See it live on Cardano Market → #### Prices and OHLCV candles Spot prices and candle history for tokens on every indexed DEX. #### Pools, TVL, and reserves Liquidity pool state, total value locked, and reserve balances per pair. #### Orderbooks and swaps Order flow and executed swaps, normalized across venues. #### Top traders Most active addresses per token and per pool. #### NFT collections and sales Collections, floor prices, and individual sales. #### ADA/USD candles Fiat reference candles so charts and P&L resolve to dollars. #### FIFO wallet P&L, built in The Wallet Analytics add-on turns any Cardano address into holdings, transaction history, and FIFO cost-basis P&L. Portfolio views and tax-season exports come from the API, not from an indexer you build and babysit. Comparing providers? See the Nexus vs Blockfrost comparison , or browse the market data and wallet endpoints in the API reference . ### Cardano transaction builder API : build and submit server-side Nexus builds the transaction. Your users sign it with their own keys. Non-custodial by construction: private keys never reach Nexus. #### Build Three transaction families, assembled server-side. Transfers ADA and native tokens, with UTXO selection and fee calculation server-side. Staking Pool delegation and reward withdrawals, as standard certificates. Governance Conway DRep delegation and votes, not just reading governance state. #### Sign and submit Your users sign. Nexus broadcasts. Returns Unsigned CBOR, ready for any wallet to sign. Submit Broadcast the signed transaction through the same API. Evaluate Script execution units, before you commit to fees. Request and response shapes for every builder endpoint are in the API reference . ### Conway governance coverage: DReps, proposals, votes Cardano governance is on-chain state like any other, and Nexus treats it that way: read governance state and act on it through the same API. The read side covers the full Conway surface. The write side adds builder support for the two governance actions most apps need. #### Read governance state - DReps: list, detail, delegators, and voting history - Governance proposals and their lifecycle - Votes, by proposal and by voter - The constitutional committee - The constitution itself #### Act on it - DRep delegation certificates, built server-side as unsigned CBOR - Governance votes, ready for your wallet flow to sign and submit A governance dashboard, a DRep explorer, or a wallet voting flow can run its reads and its writes against one provider, one base URL, and one spec. ### Cardano data infrastructure built for production One endpoint in front of every upstream. Per-provider health checks send each request to a healthy source, so one provider's incident does not become your outage. #### Multi-provider failover Redundancy is the architecture, not an add-on. - Our own indexers - Yaci - Koios - Blockfrost Health checks pick a healthy upstream per request. #### Keys scoped per chain and network Promoting from testnet swaps the key and one parameter, not your code. Scope One chain, one network per key Networks mainnet, preprod, preview Switch ?network= on the same endpoints #### Public status page Live health for our core subsystems, published for everyone. Check the status page any time. #### Add-ons for Cardano builders - Hosted MCP server. Connects Claude and other AI agents to Nexus data and tools. - IPFS. Resolve, inspect, and pin content through our self-hosted node. GeroWallet, our own Cardano wallet, runs its swaps, market data and transactions on Nexus ### Flat Cardano API pricing Flat monthly plans instead of per-call metering, so the bill does not spike with your traffic. Plans start at $ 9 on Starter , Builder comes with a 7-day trial, and every price is on the pricing page before you sign up. #### Starter $ 9 /mo - 3M requests / month - 10 req/s - 2 API keys 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. Bundles: Data $19, Build + AI $19, Complete $29 . WebSocket packages start at $ 29 per month. Start the 7-day Builder trial See full pricing → ### Cardano API questions, answered What developers ask before putting Nexus behind a Cardano app. What is a Cardano data API? A Cardano data API is a hosted service that indexes the Cardano blockchain and exposes its state (addresses, transactions, assets, pools, governance) over REST endpoints, so you do not run cardano-node and db-sync yourself. Nexus goes further than chain data: the same Cardano endpoints and auth header also serve first-party DEX market data, FIFO wallet P&L, and a server-side transaction builder as opt-in add-ons, plus live WebSocket streaming. Can I query Cardano without running a node? Yes. That is the job of a hosted Cardano API: Nexus operates the indexing infrastructure, with multi-provider failover across our own indexers, Yaci, Koios, and Blockfrost, and you read the chain over plain HTTPS with an nxs_ API key in the X-Api-Key header. No cardano-node to run, no db-sync to keep in sync. For TypeScript there is an official SDK, @adlabs/nexus on npm; the OpenAPI 3.1 spec at /v3/api-docs generates typed clients for other languages. What Cardano endpoints does Nexus cover? Chain data covers accounts, addresses, assets and holders, blocks, epochs and protocol parameters, enriched stake pools, DReps and governance, scripts and datums, rich transaction objects, and transaction submit plus evaluate. On top of that, the same base URL and auth header serve DEX market data across 11 DEXes, NFT sales, wallet P&L, and transaction building as opt-in add-ons, with WebSocket streaming as its own package. The full reference with request and response shapes lives at /docs. How is Nexus different from Blockfrost, Koios, or Maestro on Cardano? Those providers cover on-chain Cardano data well. Nexus adds first-party DEX market data across 11 DEXes, NFT sales data, FIFO wallet P&L, a server-side transaction builder, and WebSocket streaming on the same API surface, behind multi-provider failover and flat monthly pricing. Nexus has its own API surface rather than mirroring Blockfrost's, so migrating means mapping endpoint paths (config-level work, not a rewrite); the official TypeScript SDK catches the differences at compile time, and a migration guide is planned. Read the full Blockfrost comparison. Which Cardano networks does Nexus support? Mainnet, preprod, and preview, all on the same endpoints and selected with the ?network= query parameter. Each API key is scoped to one chain and one network, so you issue a preview or preprod key for development and a mainnet key for production, both from the same account and the same dashboard. Promoting means swapping the key and the parameter, not rewriting your data layer. Does Nexus cover Conway governance data? Yes. On the read side: DReps, governance proposals, votes, the constitutional committee, and the constitution. On the write side, the transaction builder produces unsigned CBOR for DRep delegation and governance votes, so an application can read governance state and act on it through the same API. How much does the Nexus Cardano API cost? Plans are flat monthly prices, not per-call metering: Starter $9 (3M requests/month, 10 req/s), Builder $29 (10M, 25 req/s), Growth $79 (30M, 50 req/s), Scale $199 (50M, 100 req/s), and Enterprise $499 (200M, 500 req/s). There is no free tier; Builder comes with a 7-day trial. Add-ons such as Market Data ($19/mo) and Wallet Analytics ($15/mo), and bundles such as Data ($19/mo for both), are itemized on the pricing page before you sign up. Is there a free Cardano API? Yes. Koios is a free, community-run query layer, Blockfrost has a free STARTER tier of 50,000 requests per day, and Iagon has announced Insight, a free API expected in Q3 2026 covering a roughly 25-endpoint chain-data subset. Nexus is paid only: plans start at Starter, $9 per month for 3M requests, Builder comes with a 7-day trial, and every plan can add first-party DEX market data, FIFO wallet P&L, transaction building, and WebSocket streaming, which those chain-data services do not offer. ### Ship your Cardano app on one integration Chain data, market data, wallet P&L, transaction building, and streaming: one account, one bill, multi-provider failover underneath. Plans from $9 a month. Start the 7-day Builder trial Talk to us about Enterprise or Dedicated Dedicated infrastructure starts at $2,000 per month. A contractual SLA is available on Dedicated: contact sales. --- # Midnight API for DUST, Transactions & Indexer: Nexus URL: https://nexus.gerowallet.io/midnight/ Description: Build on Midnight without running a node. Check DUST registration, build and submit transactions, and query the indexer over REST. 7-day Builder trial. MIDNIGHT CARDANO BITCOIN ## The Midnight API for builders DUST status, transaction building and submission, and indexer queries for Midnight mainnet and preprod. REST over HTTPS, OpenAPI 3.1, no node to run. Start the 7-day Builder trial Read the Midnight docs CARDANO same account MIDNIGHT block 1,204,338 · mainnet BITCOIN same account NEXUS one endpoint, every primitive Dust Generation MIDNIGHT 12,000 NIGHT 5 DUST / NIGHT 49,400 / 60,000 DUST 7d to capacity registered · shielded fees Prove where you want MIDNIGHT POST /tx/submit proof: nexus POST /tx/prove-and-submit proof: nexus POST /tx/submit-proven proof: yours bind · submit · txHash back Shielded UTXOs MIDNIGHT UNSHIELDED mn_shield…9fzk 4,200 SHIELDED hidden DUST REG intent 3f81…9c2 yes zswap · proof verified · 41 ms Indexer GRAPHQL POST /indexer/graphql { block { height hash } } height 1,204,338 indexer · ws relay · info MIDNIGHT CARDANO BITCOIN The Midnight API for builders DUST status, transaction building and submission, and indexer queries for Midnight mainnet and preprod. REST over HTTPS, OpenAPI 3.1, no node to run. Start the 7-day Builder trial Read the Midnight docs NEXUS one endpoint, every primitive Dust Generation MIDNIGHT 12,000 NIGHT 5 DUST / NIGHT 49,400 / 60,000 DUST 7d to capacity registered · shielded fees Prove where you want MIDNIGHT POST /tx/submit proof: nexus POST /tx/prove-and-submit proof: nexus POST /tx/submit-proven proof: yours bind · submit · txHash back Shielded UTXOs MIDNIGHT UNSHIELDED mn_shield…9fzk 4,200 SHIELDED hidden DUST REG intent 3f81…9c2 yes zswap · proof verified · 41 ms Indexer GRAPHQL POST /indexer/graphql { block { height hash } } height 1,204,338 indexer · ws relay · info ### Nexus Midnight API at a glance Mainnet + preprod every endpoint on both networks, plus Preview reads on ledger 9; stagenet is being retired DUST registration status, account state, and registration transactions over REST Your prover or ours submit signed, already proven, or prove-and-submit on Nexus OpenAPI 3.1 machine-readable spec published at /v3/api-docs Public 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 docs → #### DUST registrations Build the Cardano-side registration, update, and deregistration transactions, and list live registrations. View in docs → #### DUST account state The Midnight-side DUST account for an address, and a state snapshot for sync. View in docs → #### Transactions Build an unshielded NIGHT transfer, then submit it signed, already proven, or prove-and-submit on Nexus. View in docs → #### Transaction UTXOs The unshielded UTXO view of any Midnight transaction: created and spent outputs by hash. View in docs → #### Network info and indexer Indexer, prover, and node endpoints plus the current era, and a GraphQL passthrough to the Midnight indexer. View in docs → ### DUST 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. - 1 #### Build the registration POST /dust/build-registration-tx returns the Cardano transaction ( tx_cbor ) that maps a reward address holding NIGHT to a DUST address. Your wallet signs it. - 2 #### Submit it on Cardano The registration is an ordinary Cardano transaction, so any Cardano submit path works, including the Nexus Cardano API. - 3 #### Read the status GET /dust/status returns registered , night_balance , generation_rate , current_capacity and max_capacity , so your app can show when DUST is ready to spend. GET /dust/status 200 OK 12,000 NIGHT registered 82% 49,400 / 60,000 DUST regenerates toward capacity cardano_reward_address "stake1u9x2…" dust_address "mn_dust…9fzk" registered true night_balance "12000000000" generation_rate "5 DUST / NIGHT" current_capacity "49400" max_capacity "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. Call /dust/status with a trial key → ### 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 POST /tx/submit Nexus proves Send the signed, unproven transaction. Nexus proves, binds, and submits it. The default for unshielded NIGHT transfers built with /tx/build-unshielded. POST /tx/prove-and-submit Nexus proves For shielded transactions your app built with the Midnight SDK: Nexus runs the proof and submits. POST /tx/submit-proven You proved it You already ran the proof against your own prover. Nexus only submits, no proving on our side. Every route returns the transaction hash. When Nexus proves, your unproven transaction and its private witness data reach Nexus for the proof; /tx/submit-proven keeps them on your machine. 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. GeroWallet DUST generation built in, live on mainnet Public status page ### Partners, customers, and design partners - Design partner - Open-source partner - Network partner - SongMarketCap Integration partner - Integration partner - Community integration partner ### 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 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. Bundles: Data $19, Build + AI $19, Complete $29 . WebSocket packages start at $ 29 per month. Start the 7-day Builder trial See full pricing → ### 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, and Preview for reads. Midnight relaunched Preview in November 2026 on ledger 9, the ledger mainnet runs; its transaction routes open once testing is done. Stagenet still runs on a separate ledger-9 toolchain but is being retired, so move to Preview. Use the test networks with faucet tokens only. The network is part of the URL: /api/midnight/midnight-mainnet, /api/midnight/midnight-preprod, /api/midnight/midnight-preview, /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. Proving on Nexus means the unproven transaction, including its private witness data (the DUST fee spend, and the spent notes on a shielded send), reaches Nexus for the length of the proof; Nexus does not log or store it. To keep that data on your machine, run your own prover and submit with /tx/submit-proven, which never proves. The proving routes are rate-limited per caller and answer 503 with Retry-After when the provers are busy. 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. Start the 7-day Builder trial Talk to us about Enterprise or Dedicated Dedicated infrastructure starts at $2,000 per month. A contractual SLA is available on Dedicated: contact sales. --- # Bitcoin API: UTXOs, Fees, Ordinals & Runes: Nexus URL: https://nexus.gerowallet.io/bitcoin/ Description: Bitcoin API for developers: address UTXOs and balances, fee estimates in sat/vB, mempool, ordinals, runes, and transaction broadcast. 7-day trial. BITCOIN CARDANO MIDNIGHT ## Bitcoin API for UTXOs, fees, ordinals, and runes Addresses, mempool, and broadcast over REST. No node to run. Start the 7-day Builder trial Read the Bitcoin docs CARDANO same account BITCOIN block 973,822 · mainnet MIDNIGHT same account NEXUS one endpoint, every primitive Addresses & UTXOs BTC GET /addresses/{a}/balance 58,942 sats GET /addresses/{a}/utxos 3 unspent GET /addresses/{a}/txs 2,020 txs confirmed + mempool · paged by height Fees & Mempool BTC 3.2 fast 2.1 med 1.4 slow sat/vB mempool 14,208 tx · 8.4 vMB Ordinals & Runes BTC GET /addresses/ {a} /ordinals #82,441,907 +2 UNCOMMON•GOODS 12,400 3 inscriptions · 2 runes Broadcast REST POST /txs/submit { "rawTxHex": "0200…" } txid 4f9c…d21a 400 rejected · 409 already in chain BITCOIN CARDANO MIDNIGHT Bitcoin API for UTXOs, fees, ordinals, and runes Addresses, mempool, and broadcast over REST. No node to run. Start the 7-day Builder trial Read the Bitcoin docs NEXUS one endpoint, every primitive Addresses & UTXOs BTC GET /addresses/{a}/balance 58,942 sats GET /addresses/{a}/utxos 3 unspent GET /addresses/{a}/txs 2,020 txs confirmed + mempool · paged by height Fees & Mempool BTC 3.2 fast 2.1 med 1.4 slow sat/vB mempool 14,208 tx · 8.4 vMB Ordinals & Runes BTC GET /addresses/ {a} /ordinals #82,441,907 +2 UNCOMMON•GOODS 12,400 3 inscriptions · 2 runes Broadcast REST POST /txs/submit { "rawTxHex": "0200…" } txid 4f9c…d21a 400 rejected · 409 already in chain ### Nexus Bitcoin API at a glance Mainnet + testnet4 the same endpoints on both networks, each with its own scoped key bitcoind + electrs + ord node, address index, and ordinals index, run by us so you do not have to sat/vB fee estimates keyed by confirmation target, from 1 block to 1,008 OpenAPI 3.1 machine-readable spec published at /v3/api-docs Public status page with live health for core subsystems ### Bitcoin chain access: UTXOs, fees, ordinals, and runes over REST Nexus is a hosted Bitcoin data API: REST over plain HTTPS on top of bitcoind, electrs, and ord, so you query addresses, fees, ordinals, and runes without running a node. The same base URL and X-Api-Key header as Cardano and Midnight, with an OpenAPI 3.1 spec that generates typed clients. Six endpoint groups cover what a Bitcoin app reads and writes. The same endpoints serve mainnet and testnet4, each with its own scoped key. # Confirmed balance and UTXOs for a Bitcoin address BASE="https://nexus.gerowallet.io/api/btc" ADDR="bc1p..." curl "$BASE/addresses/$ADDR/utxos" \ -H "X-Api-Key: nxs_your_api_key_here" The key decides the network: a mainnet key reads mainnet, a testnet4 key reads testnet4. Each key is scoped to one chain and one network. #### Addresses Chain and mempool stats, confirmed balance in sats, UTXOs (full or paged by height), and transaction history. View in docs → #### Transactions Look up a transaction by txid, fetch its raw hex, batch lookups, and broadcast a signed transaction. View in docs → #### Blocks and chain tip Recent blocks, a block by hash or height, the chain tip, and the latest block. View in docs → #### Fees and mempool Fee-rate estimates in sat/vB by confirmation target, and a mempool snapshot with count, vsize, and fee histogram. View in docs → #### Ordinals Inscription metadata by ID, and the inscriptions held at an address with their UTXO context. View in docs → #### Runes Rune metadata by ID or spaced name, and rune balances by address, by outpoint, or for up to 250 outpoints in one call. View in docs → ### The four calls most Bitcoin apps make Read what an address holds, price the fee, broadcast, and see what is inscribed. Each one is a single request. #### Get the UTXOs for a Bitcoin address As a Bitcoin UTXO API, GET /addresses/{address}/utxos returns every unspent output with its txid, vout, value in sats, and confirmation status, mempool outputs included. For wallets that sync incrementally, /utxos/page pages the same set by block height and returns the tip it read, so you store one watermark and never miss a block. /balance gives the confirmed balance in sats on its own. curl "$BASE/addresses/$ADDR/utxos" -H "X-Api-Key: nxs_your_api_key_here" # [{"txid":"c1e9…66de","vout":0,"value":546, # "status":{"confirmed":true,"blockHeight":897931}}] View in docs #### Estimate Bitcoin fees in sat/vB GET /fees returns fee-rate estimates in sat/vB keyed by how many blocks you are willing to wait, from 1 to 1,008. Pick the target that matches your urgency. For a view of the queue itself, the mempool API (GET /mempool) returns the transaction count, total vsize, total fees, and a fee histogram. curl "$BASE/fees" -H "X-Api-Key: nxs_your_api_key_here" # {"estimates":{"1":1.07,"3":1.0,"6":0.12,"144":0.12}} View in docs #### Broadcast a signed Bitcoin transaction POST /txs/submit takes the signed transaction as hex and broadcasts it through our bitcoind, returning the txid. Node rejections come back as clear HTTP errors: an invalid or rejected transaction is a 400, and one already in the chain is a 409. Your keys never leave your app; Nexus only relays the signed bytes. curl -X POST "$BASE/txs/submit" -H "X-Api-Key: nxs_your_api_key_here" \ -H "Content-Type: application/json" \ -d '{"rawTxHex":"0200000001…"}' # {"txid":"4f9c…d21a"} View in docs #### Read ordinals inscriptions and rune balances GET /addresses/{address}/ordinals returns the inscription IDs and rune balances held at an address, straight from our ord index, so one ordinals and runes API covers both. /ordinals/inscriptions/{id} returns an inscription's number, content type, and current location, and /ordinals/runes/{rune} takes a rune ID or its spaced name, such as UNCOMMON•GOODS. curl "$BASE/addresses/$ADDR/ordinals" -H "X-Api-Key: nxs_your_api_key_here" # {"address":"bc1q…","inscriptions":["71fc…1ad6i0", …], # "runesBalances":[…],"satBalance":37442392} View in docs Further reading: Bitcoin data infrastructure: node, indexer or API? · Bitcoin runes and ordinals API ### Partners, customers, and design partners - Design partner - Open-source partner - Network partner - SongMarketCap Integration partner - Integration partner - Community integration partner ### Flat Bitcoin 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 Bitcoin 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 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. Bundles: Data $19, Build + AI $19, Complete $29 . WebSocket packages start at $ 29 per month. Start the 7-day Builder trial See full pricing → ### Bitcoin API questions, answered What developers ask before putting Nexus behind a Bitcoin app. What is the Nexus Bitcoin API? A hosted Bitcoin blockchain API over REST. Instead of running bitcoind, an address index, and an ordinals index yourself, you call Nexus endpoints for address balances and UTXOs, transactions, blocks, fee estimates, the mempool, ordinals inscriptions, and runes, and you broadcast signed transactions through the same API. Authentication is an nxs_ API key in the X-Api-Key header, the same as Nexus's Cardano and Midnight APIs. Which Bitcoin networks does Nexus support? Mainnet and testnet4, with the same endpoints on both. Each network runs its own bitcoind and electrs. The network comes from the API key: a mainnet key reads mainnet and a testnet4 key reads testnet4, so you issue one key per network from the same account. Do you index ordinals and runes? Yes. Nexus runs the ord indexer, so you can read an inscription by ID, list the inscriptions and rune balances held at an address, look up a rune by ID or spaced name, and check which inscriptions and runes sit on a given UTXO, for up to 250 outpoints in one call. Can I broadcast Bitcoin transactions? Yes. POST /api/btc/txs/submit takes a signed transaction as hex and broadcasts it through our node, returning the txid. You sign in your own app; Nexus never sees a private key. Rejections from the node come back as HTTP errors with the reason: 400 for an invalid or rejected transaction, 409 if it is already in the chain. How do keys work across Bitcoin, Cardano, and Midnight? One account, one dashboard, one bill, with a key per chain and network. A team that already uses Nexus for Cardano adds Bitcoin by issuing a Bitcoin key; the base URL and the X-Api-Key header stay the same. Every key counts toward the plan's key allowance. How much does the Bitcoin 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. Dedicated infrastructure is available on request. ### Ship your Bitcoin app without running a node UTXOs, fees, the mempool, ordinals, runes, and broadcast, with a key for each network. Plans from $9 a month. Start the 7-day Builder trial Talk to us about Enterprise or Dedicated Dedicated infrastructure starts at $2,000 per month. A contractual SLA is available on Dedicated: contact sales. --- # Nexus Pricing: Cardano, Bitcoin & Midnight API Plans URL: https://nexus.gerowallet.io/pricing/ Description: Flat monthly plans for the Nexus API, with add-ons priced up front and no compute-unit multipliers. Start with a 7-day Builder trial. ## Nexus API pricing for Cardano, Bitcoin and Midnight Flat monthly plans, and Builder comes with a 7 -day trial. Every add-on is priced on this page: no compute units, no per-method credits, and you can forecast next month's bill before you write a line of code. Keys are scoped to one chain and one network, and every plan covers Cardano, Bitcoin, and Midnight. Start the 7 -day Builder trial Compare the plans below cardano-mainnet midnight-mainnet bitcoin-mainnet Growth plan · $79/mo + Data bundle · $19/mo = $98/mo, flat · no per-call overage ### Simple, scalable Nexus pricing Start on the core API for $ 9 , then add a bundle or only the add-ons you need. Live in minutes: upgrade, downgrade, or cancel anytime. #### Starter Prototypes and hobby projects. $ 9 /mo - 3,000,000 requests / month - 10 req/s sustained · burst 100 - 2 API keys - Full blockchain API - Preprod + mainnet access - Add-ons, bundles, and WebSocket streaming Get Starter #### Builder Indie devs and side projects. $ 29 /mo - 10,000,000 requests / month - 25 req/s sustained · burst 250 - 4 API keys - Everything in Starter Start 7-day trial #### Growth Startups and DApp teams. $ 79 /mo - 30,000,000 requests / month - 50 req/s sustained · burst 500 - 7 API keys - Everything in Builder Start Growth #### Scale Production applications. $ 199 /mo - 50,000,000 requests / month - 100 req/s sustained · burst 1,000 - 13 API keys - Everything in Growth - Priority support Start Scale #### For exchanges, institutional, and regulated teams Higher volumes, bundled add-ons, and isolated infrastructure with a contractual SLA. #### Enterprise Exchanges, aggregators, and institutional users. $499 /mo Everything in Scale, plus all add-ons bundled and per-API-key rate limit overrides for mixed workloads. - 200,000,000 requests / month - 500 req/s sustained · burst 5,000 - Unlimited API keys - Market Data, Wallet Analytics, Transaction Builder, MCP Server, and WS Unlimited included - Per-API-key rate limit overrides - Email support · 48h response Talk to sales #### Dedicated For compliance, data residency, and custom SLAs. From $2,000 /mo Your own isolated infrastructure. Negotiated request volumes, rate limits, SLA, and support channels. - Dedicated GKE cluster + postgres - Physical data isolation - Contractual SLA (negotiable) - Dedicated Slack/Teams · 4h response - Custom endpoints and filtered streams - On-premise option available Contact us #### Bundles and add-ons Bundle the capabilities you use together and pay less, or add them one at a time. REST add-ons share your tier's unified request pool, one number to track. WebSocket has its own connection and message limits. ##### Data +$ 19 /mo $ 34 separately · save $ 15 For dashboards, portfolio apps and trading tools. - Market Data $ 19 - Wallet Analytics $ 15 Starter, Builder, Growth, Scale · included in Enterprise ##### Build + AI +$ 19 /mo $ 38 separately · save $ 19 For wallets, dApps and AI agents that build transactions. - Transaction Builder $ 19 - MCP Server $ 19 Starter, Builder, Growth, Scale · included in Enterprise ##### Complete +$ 29 /mo $ 72 separately · save $ 43 Data and Build + AI together, for less than both. - Market Data $ 19 - Wallet Analytics $ 15 - Transaction Builder $ 19 - MCP Server $ 19 Starter, Builder, Growth, Scale · included in Enterprise One bundle per plan. IPFS and WebSocket packages are sold separately. Every self-serve plan can add bundles, add-ons and WebSocket streaming. ##### Market Data +$ 19 /mo Prices, OHLCV candles, DEX pools, order books, and NFT sales across all 11 Cardano DEXes. - Prices across all 11 DEXes (Minswap, SundaeSwap, WingRiders, VyFi, Splash, TeddySwap, MuesliSwap, CSwap) - OHLCV candles: 15m, 1h, 1D, 1W - DEX pool TVL, reserves, fees - Order books: AMM-simulated + MuesliSwap, GeniusYield - NFT marketplace sales (jpg.store V2/V3) - Token metadata: name, ticker, logo, decimals Starter, Builder, Growth, Scale · included in Enterprise · in the Data and Complete bundles ##### Wallet Analytics +$ 15 /mo Holdings, transaction history, and FIFO-based P&L per wallet. - Current holdings with USD valuation - Full send/receive transaction history - FIFO-based P&L calculation per token Starter, Builder, Growth, Scale · included in Enterprise · in the Data and Complete bundles ##### Transaction Builder +$ 19 /mo Server-side UTXO selection, fee calc, and unsigned CBOR for transfers, staking, and governance. - UTXO selection, fee calc, change outputs - ADA + native token transfers - Staking: pool delegation, key (de)registration - Governance (Conway): DRep delegation, votes - Reward withdrawal Starter, Builder, Growth, Scale · included in Enterprise · in the Build + AI and Complete bundles ##### MCP Server +$ 19 /mo Model Context Protocol endpoint: connect Claude and other AI agents directly to Nexus data + tools. - Hosted Model Context Protocol endpoint - Connect Claude, Cursor, and other MCP-compatible AI agents - 25+ tools: Cardano, Bitcoin, Midnight, market data - Balances, tx info, and unsigned tx building from chat - Per-API-key authentication Starter, Builder, Growth, Scale · included in Enterprise · in the Build + AI and Complete bundles ##### IPFS +$ 5 /mo Resolve, inspect, and pin IPFS content through Nexus’ self-hosted node: gateway fetch, stat/ls, IPNS resolve, and per-key pinning. - Self-hosted IPFS node: resolve any reachable CID via the DHT - Gateway fetch with HTTP range + HEAD support - Content metadata: stat (size/type) and directory ls - IPNS name resolution - Per-API-key pinning (pin / list / unpin), tenant-isolated Starter, Builder, Growth, Scale · included in Enterprise ##### WebSocket Streaming Live market data via STOMP-over-SockJS. Subscribe to price updates, trade events, and pool changes with a 10-second broadcast interval. WS Unlimited included in Enterprise WS Starter $ 29 /mo 2 concurrent 100,000 / mo WS Pro $ 59 /mo 10 concurrent 2,000,000 / mo WS Unlimited $ 99 /mo Unlimited Unlimited ### Configure Your Plan Pick a base tier, add a bundle or the add-ons you need, and preview your $GERO staking discount. #### Base Tier Select your plan tier. Starter $ 9 /mo 3M req/mo · 2 API keys 10 req/s · burst 100 Builder $ 29 /mo 10M req/mo · 4 API keys 25 req/s · burst 250 Growth $ 79 /mo 30M req/mo · 7 API keys 50 req/s · burst 500 Scale $ 199 /mo 50M req/mo · 13 API keys 100 req/s · burst 1,000 Enterprise $ 499 /mo 200M req/mo · Unlimited API keys 500 req/s · burst 5,000 #### Bundles Add-ons that work together, for less. One bundle per plan. Data Market Data + Wallet Analytics +$ 19 /mo $ 34 Build + AI Transaction Builder + MCP Server +$ 19 /mo $ 38 Complete Market Data + Wallet Analytics + Transaction Builder + MCP Server +$ 29 /mo $ 72 #### Add-Ons REST add-ons share your tier's unified request pool, one number to track. Market Data Prices, OHLCV candles, DEX pools, order books, and NFT sales across all 11 Cardano DEXes. +$19/mo Wallet Analytics Holdings, transaction history, and FIFO-based P&L per wallet. +$15/mo Transaction Builder Server-side UTXO selection, fee calc, and unsigned CBOR for transfers, staking, and governance. +$19/mo MCP Server Model Context Protocol endpoint: connect Claude and other AI agents directly to Nexus data + tools. +$19/mo IPFS Resolve, inspect, and pin IPFS content through Nexus’ self-hosted node: gateway fetch, stat/ls, IPNS resolve, and per-key pinning. +$5/mo #### WebSocket Streaming Live market data via STOMP. Pick a package or skip entirely. No WebSocket REST only. Add streaming later if needed. Free WS Starter 2 concurrent connections · 100,000 messages / month +$29/mo WS Pro 10 concurrent connections · 2,000,000 messages / month +$59/mo WS Unlimited Unlimited concurrent connections and messages +$99/mo Growth monthly total $ 79.00 Continue → #### Price Summary Growth tier $ 79.00 Monthly Total $ 79.00 Annual Total (×12) $ 948.00 /yr Continue to Billing → #### $GERO staking discount Hold $GERO to save up to 20% Hold $GERO GeroWallet's native Cardano token. Holding $GERO in any Cardano wallet automatically unlocks Nexus API discounts, Gero Card fee waivers, and on-chain governance voting. to unlock a sliding discount on your Nexus subscription, from 5% at $50 staked up to 20% at $1,000+. Connect your Cardano wallet to preview your qualifying tier now. Connect Cardano Wallet → ### Compare plans The same figures as the plan cards, side by side. Add-ons and WebSocket packages are priced in the section above. Nexus plans compared by limits, keys, add-ons, support and SLA Plan | Starter $9/mo | Builder $29/mo 7 -day trial | Growth Popular $79/mo | Scale $199/mo | Enterprise $499/mo | Dedicated From $2,000/mo | Requests per month | 3M | 10M | 30M | 50M | 200M | Negotiated | Rate limit | 10 req/s | 25 req/s | 50 req/s | 100 req/s | 500 req/s | Negotiated | Burst | 100 | 250 | 500 | 1,000 | 5,000 | Negotiated | API keys | 2 API keys | 4 API keys | 7 API keys | 13 API keys | Unlimited API keys | Unlimited | Add-ons and bundles | Sold separately | Sold separately | Sold separately | Sold separately | All included | All included | WebSocket streaming | Packages from $29/mo | Packages from $29/mo | Packages from $29/mo | Packages from $29/mo | WS Unlimited included | Custom filtered streams | Support | Email | Email | Email | Priority email | Email, 48h response | Slack or Teams, 4h response | SLA | Status page | Status page | Status page | Status page | Status page | Contractual, negotiable | One bundle per plan. IPFS and WebSocket packages are sold separately. Dedicated terms are agreed per customer. ### Coming from another provider? Most Cardano APIs price by request or by compute unit and sell market data and transaction building separately, if at all. Nexus sells flat tiers with the add-ons itemized above. If you are comparing bills, start with the page for the provider you use today. #### Coming from Blockfrost Per-request plans with daily quotas, compared line by line with flat monthly tiers. Read the comparison → #### Coming from Maestro Maestro retired its API in September 2026. What maps where, and what the move costs. Read the comparison → #### Coming from Koios When a community-run free endpoint is enough, and when a managed plan pays for itself. Read the comparison → ### Pricing questions, answered What developers ask before choosing a Nexus plan. How does the 7-day Builder trial work? The trial is the Builder plan for 7 days. You sign up, create your keys, and use the plan in full; nothing is charged if you cancel before the trial ends. After the trial the subscription continues on Builder at $29 a month unless you cancel or change plan in the dashboard. The trial covers Builder only; Starter, Growth and Scale start as paid plans. What happens when I reach my plan's limits? Each plan has a per-second rate limit with a burst allowance and a monthly request allowance. Requests over the per-second limit get a 429 and succeed on retry. If you are outgrowing the monthly allowance, move up a tier from the dashboard; there is no per-call overage billing on any plan, so the bill never climbs on its own. Can I change or cancel my plan at any time? Yes. Upgrades, downgrades, add-on and bundle changes are made in the dashboard. Cancellation takes effect at the end of the current billing cycle; you keep access until then and are not charged for the next cycle. Subscription fees are otherwise non-refundable, as set out in the Terms. Read the Terms of Service. How do API keys work across chains and networks? Every key is scoped to one chain and one network, for example Cardano mainnet or Midnight preprod. Your plan's key allowance (2 API keys on Starter up to unlimited API keys on Enterprise) is shared across all chains, so a Cardano app adding Bitcoin or Midnight issues another key from the same account, and the request allowance is one pool across your keys. Which add-ons do I need for market data? Market Data ($19 a month) gives prices, OHLCV candles, DEX pools, order books and NFT sales across all 11 Cardano DEXes over REST. If you also want per-wallet holdings and P&L, the Data bundle ($19) covers Market Data and Wallet Analytics together. Live streaming of the same data is a WebSocket package, sold separately from $29. Is there an SLA? A contractual SLA is available on Dedicated, with the terms agreed as part of the contract. Enterprise includes email support with a 48-hour response; Dedicated includes a shared Slack or Teams channel with a 4-hour response. The public status page shows live health for every plan. Do you offer dedicated infrastructure? Yes. Dedicated starts at $2,000 a month and runs your own isolated cluster and database, with negotiated volumes, rate limits, support channel and SLA, custom endpoints and filtered streams, and an on-premise option. Contact sales to scope it. How do I pay? By card or PayPal, billed monthly in US dollars. Card details are handled by the payment processor and never stored on Nexus servers. Enterprise and Dedicated are arranged with sales. ### Start on a Nexus plan today Builder comes with a 7 -day trial. Enterprise and Dedicated start with a conversation. Start the 7-day Builder trial Talk to us about Enterprise or Dedicated Dedicated infrastructure starts at $2,000 per month. A contractual SLA is available on Dedicated: contact sales. --- # About Nexus: Built by A.D. Labs, the GeroWallet Team URL: https://nexus.gerowallet.io/about/ Description: Nexus is the blockchain API built by A.D. Labs LTD, the team behind GeroWallet. What we build, what we commit to, where we are active, and how to reach us. ## About Nexus, the blockchain API built by A.D. Labs Nexus is the data and transaction API for Cardano, Bitcoin, and Midnight, built and run by A.D. Labs LTD , the team behind GeroWallet. The endpoints you integrate are the ones our own wallet depends on. cardano-mainnet midnight-mainnet bitcoin-mainnet GeroWallet · runs on Nexus in production your app · same endpoints, your own keys ### Nexus at a glance 3 chains live today: Cardano, Bitcoin, and Midnight 11 Cardano DEXes indexed for first-party market data OpenAPI 3.1 machine-readable spec published at /v3/api-docs Apache 2.0 GeroWallet source, public on GitHub Public status page with live health for core subsystems ### Mission Teams building on UTXO chains have been stitching together a node, an indexer, a market-data vendor and their own transaction code, with nobody accountable for the whole. Nexus exists to be that one accountable partner: chain data, market data, wallet analytics, transaction building and streaming on one base URL, with pricing you can read before you sign up. ### What we build #### Nexus The full-stack API for Cardano, Bitcoin and Midnight: REST and WebSocket, an OpenAPI 3.1 spec, keys scoped to one chain and one network, and flat monthly plans. - Cardano API - Midnight API - Bitcoin API - Pricing #### GeroWallet The non-custodial wallet for Cardano and Midnight, with DUST generation built in and its source published under Apache 2.0. The wallet's market data, swap routing and transaction building run on Nexus in production. - gerowallet.io - Source on GitHub ### How we got here - 1 #### We built a wallet GeroWallet had to serve balances, prices, swap routes and transaction building to real users every day, and later Midnight DUST status too. - 2 #### We built the stack it needed No single provider covered all of that. The team built its own indexers, market-data pipeline and transaction builder, with failover underneath, and ran the wallet on it. - 3 #### We opened it as Nexus In July 2026 the same stack went public as Nexus, with FluidTokens as the first design partner and Cardano, Bitcoin and Midnight live from day one. ### How Nexus runs Failover under every Cardano read Our own indexers first, then Yaci, Koios and Blockfrost in order. A provider that fails or falls behind is taken out of rotation, not retried in the request path. No keys on our servers The transaction builder returns unsigned CBOR and the Midnight routes take pre-signed transactions. Signing stays in your wallet or your app. One origin, one spec The API and the site share one origin, the whole surface is described by an OpenAPI 3.1 spec, and the TypeScript SDK is generated from it. A status page, not a number Live health for the core subsystems is public. We publish that instead of an uptime percentage; contractual SLAs belong to the Dedicated tier. ### Commitment Prices you can read Flat monthly tiers with every add-on priced on the pricing page . No compute units, no per-method credits, no surprise at month end. Built in the open GeroWallet's source is public, Nexus ships an OpenAPI spec and a TypeScript SDK , and Nexus is listed in the Cardano developer portal and the Mesh SDK as a provider. Honest comparisons Our comparison pages say when the other provider is the better fit. Rival claims are checked against that project's own documentation before they are published. A reply from the people who run it Enterprise and Dedicated customers talk to the engineers operating the service, with response times written into the plan rather than a ticket queue. ### Partners, customers, and design partners - Design partner - Open-source partner - Network partner - SongMarketCap Integration partner - Integration partner - Community integration partner ### A word from our CEO We built Nexus because we needed it. GeroWallet has to show balances, prices, swap routes and Midnight DUST status to real users every day, and no single provider gave us all of that with the reliability a wallet needs. So we built the stack for ourselves, ran it in production, and then opened it to other teams. Everything you get on a Nexus key is something our own product already depends on. If it is not good enough for GeroWallet, it does not ship. Adam Cazes CEO, A.D. Labs LinkedIn X ### Build on what we run ourselves Builder comes with a 7 -day trial. Enterprise and Dedicated start with a conversation. Start the 7-day Builder trial Talk to us about Enterprise or Dedicated Dedicated infrastructure starts at $2,000 per month. A contractual SLA is available on Dedicated: contact sales. --- # Blockfrost Alternative: Nexus Full-Stack Cardano API URL: https://nexus.gerowallet.io/alternatives/blockfrost/ Description: Blockfrost alternative by A.D. Labs: Nexus runs your Blockfrost SDK with one changed line, serves 6.7x fresher blocks, and covers Cardano and Bitcoin. ## A full-stack Blockfrost alternative for Cardano, Bitcoin, and Midnight Nexus is a full-stack Blockfrost alternative: one account and one base URL cover on-chain data, DEX market data across all 11 Cardano DEXes, FIFO wallet P&L, a server-side transaction builder, WebSocket streaming, and Bitcoin and Midnight coverage. And it is a one-line migration: point your existing Blockfrost SDK at the Nexus /api/v0 endpoint and your code keeps working, same calls, same responses, fresher data. Your Blockfrost SDK, two changed lines const api = new BlockFrostAPI({ - projectId: "mainnetYourProjectId", + projectId: "nxs_your_nexus_key", + customBackend: "https://nexus.gerowallet.io/api/v0", }); That is the migration. Your SDK, your calls, your response shapes, now served by Nexus. Start the 7-day Builder trial Read the docs Nothing on Nexus is at no charge. The trial is 7 days on the Builder plan, $29/mo after. Also weighing Maestro or Koios? The Maestro page has its own map, and Koios is answered on this page under "Why not the free one". ### Five answers before you switch What breaks, what does not, how long it takes, what it costs, and how to try it without committing. In that order. - 1 #### What breaks Five compatible paths answer 503 with Retry-After while their upstream fix lands: pool detail, pool history, the extended pool list, the unfiltered asset list and the previous-epoch listing. Mempool endpoints and account-usage metrics are not served on purpose, and the account root is not served yet. - 2 #### What does not Your SDK and your code. Blocks, transactions, addresses, account sub-resources, assets by ID or policy, epochs, scripts, metadata and stake pools all answer on /api/v0 with Blockfrost response shapes and error envelopes. - 3 #### How long it takes The compatible endpoint is one changed line: customBackend plus your nxs_ key as the project id. Most teams have production reads on Nexus the same afternoon and move individual calls to the native API over the following weeks, where a paged loop becomes one request. - 4 #### What it costs Starter is $9/mo for 3M requests, Builder $29/mo for 10M, Growth $79/mo for 30M, Scale $199/mo for 50M. WebSocket streaming is a package from $29/mo, included on Enterprise. Blockfrost DEVELOPER is EUR 79/mo for 1M a day. Both APIs count per request; Nexus counts per month with no midnight reset. - 5 #### How to try it without committing Start the 7-day Builder trial, point the SDK at /api/v0, and run real traffic against both providers for a week. Card required, nothing charged before day 7, cancel from the dashboard. ### Why teams are re-evaluating their Cardano API in 2026 Four structural limits worth checking against your workload. Each one is documented in Blockfrost's own public docs. #### The throughput ceiling Every tier below Enterprise shares one per-IP limit: 10 requests per second sustained, with a 500-request burst. Upgrading raises the daily quota; the rate and the burst stay the same, so STARTER free and DEVELOPER at EUR 79 hit the same ceiling. #### Pagination multiplies requests List endpoints return at most 100 items per page. A wallet with 5,000 transactions takes 50 paged calls just to enumerate, and every page counts against the daily quota. #### Hard stops at the edges At the daily quota Blockfrost returns HTTP 402 and stops serving. Continued flooding past the rate limit triggers an HTTP 418 auto-ban. Production teams need backoff logic around both failure modes. #### A blockchain API, by design Blockfrost covers Cardano chain data, IPFS, and Midnight. DEX market data, wallet P&L, server-side transaction building, and Cardano streaming sit outside that scope, so teams add vendors or custom indexers for them. ### What Nexus is, in six products Chain data is one of them. The other five are what teams would otherwise build themselves or buy from separate vendors. #### Blockchain API Blocks, txs, addresses & assets Ten endpoint groups, accounts to governance, plus submit and evaluate. #### WebSocket Streaming Live blocks & txs, pushed to you Push, not poll: market data on a 10 second cadence, Blueprints with REST backfill. #### Transaction Building Build & submit on-chain Transfers, staking, and Conway governance built server-side. Unsigned CBOR out; keys never touch Nexus. #### DEX Aggregator Best-price swap routing Best-price routing across Minswap, WingRiders, Splash, and SaturnSwap. You sign every swap. #### MCP Server Nexus data for AI agents A hosted MCP endpoint: AI agents query Cardano, Bitcoin, and Midnight with your own key. #### Market Data Prices, pools & tokens See it live on Cardano Market → Prices, candles, pools, order books, and NFT sales across all 11 indexed DEXes. ### Blockfrost vs Nexus, value by value Nexus leads where production apps feel it: freshness, burst headroom, products, and chains. Prefer the long-form version with sources? Read the full technical comparison . One line migrates your Blockfrost SDK: customBackend to /api/v0, nxs_ key as project id 6.7x fresher 575 ms median block-to-served vs 3,845 ms, measured August 2026 6 products chain data, market data, wallet P&L, tx builder, streaming, MCP Nexus leads 12 of the 18 dimensions compared below, across performance, coverage, and developer experience. The table carries the full values. Freshness measured August 2026 from a single client in Frankfurt against both live APIs over the public internet, 119 blocks over 45 minutes at matched request rates. Method and raw data available on request. #### Burst capacity, requests admitted at peak Nexus Blockfrost Advantage: Nexus bursts scale with tier to 5,000; Blockfrost is fixed at 500 Nexus Builder $29 250 Growth $79 500 Scale $199 1,000 Enterprise $499 5,000 Blockfrost STARTER free 500 HOBBY EUR 29 500 DEVELOPER EUR 79 500 On Blockfrost, every tier below Enterprise gets the same 500-request burst at 10 req/s sustained; paying more only raises the daily quota. On Nexus both grow with the plan, from a 250 burst at 25 req/s on Builder to 5,000 at 500 req/s on Enterprise. #### Request quota, monthly Nexus Blockfrost Advantage: More requests at every paid price Nexus Starter $9 3M Builder $29 10M Growth $79 30M Scale $199 50M Enterprise $499 200M Blockfrost STARTER free 1.5M HOBBY EUR 29 9M DEVELOPER EUR 79 30M listed reachable at the tier’s rate limit listed, but beyond what 10 req/s can serve (25.9M/mo max) Builder’s 10M a month beats HOBBY’s 300k a day at the same sticker price, and Growth’s 30M matches DEVELOPER’s listed 1M a day, which 10 req/s sustained caps at 864k. Nexus quotas ship with the throughput to spend them. Want to verify the surface first? Browse the full API reference with a live playground on every endpoint. Nexus leads 12 of 18 Blockfrost leads 2 ; 4 are judgment calls. Feature and pricing comparison between Blockfrost and Nexus Dimension | Blockfrost (verified 2026-09-06) | Nexus | Performance and limits | Rate-limit model | 10 req/s sustained per IP with a 500-request burst, on every tier below Enterprise. Higher tiers raise the daily quota; the rate and burst stay the same. | Advantage: Nexus Both scale with tier: Builder 25 req/s (burst 250), Growth 50 req/s (burst 500), Scale 100 req/s (burst 1,000), Enterprise 500 req/s (burst 5,000). | Data freshness | Median 3,845 ms from block timestamp to served, measured August 2026 over the public internet. | Advantage: Nexus Median 575 ms in the same run, 6.7x fresher, and first to serve the new block on 102 of 107 contested blocks with a median lead of 3.0 seconds. Methodology in the footnote below. | Request quota | Daily: 50,000 free (STARTER), 300,000 (HOBBY, EUR 29/mo), 1M (DEVELOPER, EUR 79/mo), Enterprise custom. | Advantage: Nexus Monthly: 3M (Starter, $9), 10M (Builder, $29), 30M (Growth, $79), 50M (Scale, $199), 200M (Enterprise, $499), Dedicated custom. | Over-quota behavior | Hard HTTP 402 cutoff at the daily quota; HTTP 418 auto-ban for continued flooding. | Advantage: Nexus HTTP 429 with X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, and Retry-After headers plus a reset_at JSON body. No auto-ban. | Calls per job | 100 items per page on all list endpoints, and detail requires per-item calls: a wallet page (address plus 20 transactions with detail) takes 42 calls. | Advantage: Nexus The same wallet page is one native call, so it spends 1/42nd of the quota. Batch endpoints (bulk UTXO resolve, bulk CBOR) replace per-item loops. | Pricing | Pricing model | EUR flat tiers, plus Pay-As-You-Go paid in ADA (about 0.0000171 ADA per request). | USD flat tiers, plus opt-in add-ons: Market Data $19, Wallet Analytics $15, Transaction Builder $19, MCP Server $19, IPFS $5; bundles Data $19, Build + AI $19, Complete $29; WebSocket packages $29/$59/$99. | No-cost plan / trial | Advantage: Blockfrost STARTER plan at no charge: 50,000 requests per day. | No plan at no charge. Nexus Starter is $9/mo for 3M requests; 7-day trial on the Builder plan. | Enterprise | Custom plans, contact Blockfrost. | Enterprise $499/mo (200M requests, 500 req/s). Dedicated from $2,000/mo: your own cluster and a contractual SLA, contact sales. | Coverage and products | Chains | Cardano, plus IPFS and Midnight (launched April 2026). | Advantage: Nexus Cardano (deepest coverage), Bitcoin (including ordinals, runes, and mempool), Midnight (including transaction build and DUST); IPFS as a $5 add-on. | Market data | Not offered. | Advantage: Nexus First-party across all 11 Cardano DEXes: prices, OHLCV candles, pools, order books, NFT floor and sales. | Wallet analytics | Not offered. | Advantage: Nexus Holdings, transaction history, and FIFO-based P&L per wallet. | Transaction building | Client-side, via the official SDKs. | Advantage: Nexus Server-side builder for transfers, staking, and Conway governance operations. Returns unsigned CBOR; keys never touch Nexus servers. | Streaming | No Cardano streaming; activity monitoring means polling on a timer. | Advantage: Nexus WebSocket streaming plus Blueprints on-chain event streams. Blockfrost lets you ask 10 times a second; Nexus tells you the moment it happens. | AI agents | Not offered. | Advantage: Nexus Hosted MCP server add-on: connect Claude and other AI agents to Nexus data and tools. | Developer experience | Blockfrost API compatibility | Native. | Blockfrost-compatible endpoint at /api/v0 : point your existing SDK at it with an nxs_ key as the project id and your code keeps working, same response shapes, same error envelopes. | SDKs | Advantage: Blockfrost 15 official SDKs; the default provider in Lucid, Mesh, PyCardano, and cardano-client-lib. | Official TypeScript SDK (@adlabs/nexus on npm, MIT), plus the /api/v0 endpoint runs the official Blockfrost SDKs unmodified. A NexusProvider is merged in Mesh, a Lucid Evolution provider PR is open, and the OpenAPI 3.1 spec generates typed clients. | Auth | Per-network tokens; HTTP 403 on network mismatch. | A key per chain and network, sent as an X-Api-Key header. | Provider architecture | Single provider. | Advantage: Nexus Multi-provider failover behind one endpoint. | Blockfrost figures verified 2026-09-06 from public Blockfrost documentation and pricing. Nexus figures reflect current plans; see the pricing page for detail. Spot an error? Email nexus@gerowallet.io and we will fix it. Start the 7-day Builder trial ### What the compatible endpoint serves today Direct equivalents, guarded paths, and the ones with no equivalent. Read it here, not in production. #### Served, same shapes - Blocks and transactions - Addresses - Accounts, through the stake-address sub-resources - Assets by asset ID and by policy ID - Epochs and scripts - Transaction metadata - Stake pools: the list, retired, retiring, and per-pool metadata, relays, updates, blocks, votes and delegators #### Guarded: 503 with Retry-After - /pools/{pool_id} Pool detail - /pools/{pool_id}/history Per-epoch pool history - /pools/extended Pool list with per-pool enrichment - /assets The unfiltered asset list. /assets/{asset} and /assets/policy/{policy_id} are served - /epochs/{number}/previous Preceding-epoch listing Each is released on its own as the matching upstream indexer fix lands. #### No equivalent - Mempool endpoints Blockfrost product surface, not chain data. Not served, by design - Account-usage metrics Same reason. Quota headers on every Nexus response replace them - /accounts/{stake_address} The account root is an upstream gap, not a decision. Every sub-resource under it is served The endpoint-by-endpoint list, error envelopes and quota rules are in the Blockfrost compatibility reference . ### What Nexus adds beyond a blockchain API Compatibility gets you in the door. The larger win is fewer vendors: the data stack most Cardano teams assemble from three or four services, behind one integration. Chain reads run behind our own indexers plus Yaci, Koios, and Blockfrost, with per-provider health checks routing around any degraded upstream, including Blockfrost itself. The Nexus team also maintains the stack it runs on: six merged pull requests in bloxbean/yaci-store , the open-source Cardano indexer, fixing performance and correctness issues upstream. #### The full stack on one integration One Cardano integration covers chain data, first-party market data across all 11 Cardano DEXes, FIFO wallet P&L, a server-side transaction builder, and WebSocket streaming with Blueprints, as opt-in add-ons on one base URL and one auth header. #### Rate limits that scale with your tier Builder gets 25 req/s, Growth 50, Scale 100, and Enterprise 500, with bursts from 250 up to 5,000. Paying more buys real throughput, not just a bigger daily counter. #### UTXO-native multi-chain Cardano with the deepest coverage, Bitcoin including ordinals, runes, and mempool data, and Midnight including unshielded transaction build and DUST registration. A key per chain and network, one account. #### Flat, predictable pricing Flat monthly tiers from $9 to $499, with opt-in add-ons: Market Data $19, Wallet Analytics $15, Transaction Builder $19, MCP Server $19, IPFS $5, bundles from $19, WebSocket packages $29 to $99. Bills do not spike with traffic. Want the endpoint-level view of the Cardano surface? See the Nexus Cardano API page. #### Running an exchange or aggregator? Enterprise is $499/mo for 200M requests at 500 req/s. Dedicated starts at $2,000/mo with your own cluster and a contractual SLA. Talk to us about Dedicated infrastructure ### Who should stay on Blockfrost Not every workload should move. Blockfrost is the better choice for: #### Projects inside STARTER Hobby and pre-revenue projects comfortably under 50,000 requests per day. Blockfrost's STARTER plan covers them at no charge, and Nexus has no plan at no charge. #### Mempool-dependent pipelines Stacks that watch the mempool through Blockfrost's mempool endpoints. The Nexus Blockfrost-compatible endpoint does not serve them, so that path stays on Blockfrost today. #### Low-throughput workloads Workloads that stay under 10 req/s sustained and inside the daily quota. The shared ceiling only matters if you hit it. ### Migrating from Blockfrost to Nexus The migration is one changed line: Nexus serves a Blockfrost-compatible endpoint, so your existing SDK reads from Nexus before you touch anything else. Run both side by side on the trial, then adopt the native API where it pays. - #### 1. Point your SDK at Nexus Set customBackend to https://nexus.gerowallet.io/api/v0 and use your nxs_ key as the project id. Your code keeps working, with response shapes and error envelopes matching Blockfrost's; the compatibility reference covers the full surface. - #### 2. Run both side by side Use the 7-day Builder trial to run Nexus next to Blockfrost against production traffic, compare responses, and cut over only when the numbers match. - #### 3. Adopt native endpoints where they pay The native Cardano API cuts request counts: the wallet page that takes 42 paged Blockfrost-style calls is one call, and batch UTXO and CBOR endpoints replace per-item loops. WebSocket streams push events instead of polling. - #### 4. Add what Blockfrost does not offer DEX market data, FIFO wallet P&L, the server-side transaction builder, and Blueprints event streams sit on the same key as opt-in add-ons. TypeScript teams install @adlabs/nexus ; other languages generate typed clients from the OpenAPI 3.1 spec. # The native API (step 3): the wallet page # that takes 42 paged calls is one request. BASE="https://nexus.gerowallet.io/api" ADDR="addr1qx..." curl "$BASE/addresses/$ADDR/transactions/history" \ -H "X-Api-Key: nxs_your_api_key_here" # Over quota? You get HTTP 429 plus headers, # never an auto-ban: # X-RateLimit-Limit # X-RateLimit-Remaining # X-RateLimit-Reset # Retry-After # { "reset_at": "..." } in the body Rate-limit and over-quota behavior verified 2026-09-06 . Full request and response shapes live in the docs . Start migrating on the 7-day trial Migrating something non-trivial? Email nexus@gerowallet.io and we will map your endpoint list with you. ### Why not the free one ? Blockfrost STARTER and Koios both cost nothing. For Cardano-only reads under 50,000 requests a day, at 10 requests a second, either is a good answer. Here is where each stops. Blockfrost STARTER and Koios compared with Nexus Starter and Builder Dimension | Blockfrost STARTER | Koios | Nexus Starter / Builder | Price | No charge | No charge (Pro ~$29.99/mo, Premium ~$74.99/mo) | Starter $9/mo. Builder $29/mo after a 7-day trial | Requests | 50,000 a day, reset at midnight UTC | 5,000 a day public, 50,000 with a registered key | 3M a month on Starter, 10M on Builder, no daily reset | Rate limit | 10 req/s per IP, 500 burst | 100 requests per 10 seconds | 25 req/s with a 250 burst on Builder | Over the limit | HTTP 402 at the quota, 418 auto-ban after flooding | HTTP 429 for 60 seconds, 504 after 30 seconds of query time | HTTP 429 with reset headers, no ban | Chains | Cardano, Midnight (beta), IPFS | Cardano only | Cardano, Bitcoin and Midnight on one account | Beyond chain reads | Webhooks, IPFS storage | Chain data only | Market data across 11 DEXes, streaming, transaction builder, wallet analytics, MCP server | Support | Community and docs | Community-run node operators, best effort | A.D. Labs, the GeroWallet team, with a named engineer on your migration | Blockfrost figures from blockfrost.io and docs.blockfrost.io, Koios from koios.rest/tiers.html , both checked September 2026. Koios and Blockfrost are also fallback providers behind Nexus chain reads, so choosing Nexus keeps both in the path. ### Blockfrost alternative FAQ Short answers to the questions migrating teams ask most. Is Nexus a drop-in replacement for Blockfrost? Yes. Nexus serves a Blockfrost-compatible endpoint at https://nexus.gerowallet.io/api/v0: point your existing Blockfrost SDK at it with customBackend, use your nxs_ key as the project id, and your code keeps working with matching response shapes and error envelopes. The native Nexus API then adds DEX market data, wallet P&L, transaction building, and streaming beyond the Blockfrost surface. The endpoint-by-endpoint list is in the Blockfrost compatibility reference at https://nexus.gerowallet.io/docs/blockfrost-compatibility . Does Nexus have a no-cost plan like Blockfrost STARTER? No. Nexus plans start at Starter, $9 per month for 3M requests with no daily reset. Builder, $29 per month for 10M requests, comes with a 7-day trial. How do Nexus rate limits compare to Blockfrost's? Blockfrost applies 10 req/s sustained per IP with a 500-request burst on every tier below Enterprise; paying more raises the daily quota, not the rate. On Nexus both the rate and the burst scale with tier: 25 req/s with a 250 burst on Builder, up to 500 req/s with a 5,000 burst on Enterprise. How fresh is Nexus data compared to Blockfrost? In an August 2026 measurement, Nexus served new blocks at a 575 ms median from block timestamp against 3,845 ms on Blockfrost, and served the new block first on 102 of 107 contested blocks with a median lead of 3.0 seconds. Measured from a single client in Frankfurt against both live APIs over the public internet, 119 blocks over 45 minutes at matched request rates. Method and raw data available on request. Does Nexus support Midnight? Yes: network info, unshielded transaction build and submit, and DUST registration. Blockfrost also offers Midnight support (launched April 2026), so compare depth for your use case. Can I keep using Blockfrost SDKs with Nexus? Yes, for the compatible surface: official Blockfrost SDKs accept a custom backend URL, so pointing customBackend at https://nexus.gerowallet.io/api/v0 with an nxs_ key keeps your existing code running. For the native Nexus surface, TypeScript teams install @adlabs/nexus from npm, and other languages generate typed clients from the OpenAPI 3.1 spec. Mesh has merged a NexusProvider, and a Lucid Evolution provider PR is open. What happened with Blockfrost's governance proposal? Blockfrost proposed transitioning to a community-governed free public good, funded from the Cardano treasury. The vote concluded in July 2026 and the proposal did not pass, so Blockfrost continues to operate as a commercial provider. This page compares the two services as they operate today. ### Run Nexus next to Blockfrost for a week Point your SDK at the compatible endpoint, run real traffic against both providers, and keep whichever fits. The trial is 7 days on the Builder plan, $29/mo after. Start the 7-day Builder trial Read the docs See pricing Check live status Explore the Cardano API --- # Maestro Alternative: Nexus API for Cardano and Bitcoin URL: https://nexus.gerowallet.io/alternatives/maestro/ Description: Maestro's developer API retires September 18, 2026. Nexus keeps Bitcoin and Cardano on one API: flat request pricing and an endpoint-level migration map. Maestro's developer API retires Sep 18, 2026 ## The Maestro alternative for Cardano and Bitcoin Keep both chains on one API. Flat monthly pricing, requests instead of credits, and an endpoint-level migration map that gets you moved before your keys stop working. Start the 7-day Builder trial See the migration map 7-day trial on Builder, then $29/mo. Card required, nothing charged before day 7. Live status page OpenAPI 3.1 In production with paying teams By A.D. Labs, the GeroWallet team maestro · retiring bitcoin-mainnet cardano-mainnet Maestro keys retire Sep 18, 2026 maestro · retiring bitcoin-mainnet cardano-mainnet Maestro keys retire Sep 18, 2026 ### Five answers before you switch What breaks, what does not, how long it takes, what it costs, and how to try it without committing. In that order. - 1 #### What breaks Four mechanical things: the base URL, the auth header (X-Api-Key with an nxs_ key replaces api-key), cursor paging on the newer reads (an opaque nextCursor you send back as cursor), and anything built on Transaction Manager webhooks or Managed Contracts, which have no Nexus counterpart. - 2 #### What does not Every endpoint concept. Accounts, addresses, assets, pools, scripts, datums, transactions and submit all have a Nexus route, and Bitcoin UTXOs, ordinals, runes and submit do too. Blockfrost SDKs keep working unchanged against /api/v0. - 3 #### How long it takes Chain-data reads move in a day or two with the map on this page. Submit is a same-day change. Both APIs run side by side, so you switch reads over one at a time and never go dark. - 4 #### What it costs Starter is $9/mo for 3M requests, Builder $29/mo for 10M, Growth $79/mo for 30M, Scale $199/mo for 50M. WebSocket streaming is a package from $29/mo, included on Enterprise. A request is a request, with no credit weights to model. Market data is a $19/mo add-on on any plan. - 5 #### How to try it without committing Start the 7-day Builder trial. Card required, nothing charged before day 7, cancel from the dashboard. Point one read at Nexus, compare the payloads, then move the rest. ### What Maestro's announcement means for you Their words, not ours. Three facts from the Sep 18 retirement notice, and what each one means for your integration. #### On Sep 18, every endpoint is retired Bitcoin, Cardano and Dogecoin. API keys stop working the same day. There is no grace period after the date. #### Until then, everything runs as normal Which means you can migrate calmly this week instead of during the panic days before the cutoff. Both APIs can run side by side while you switch reads over. #### Open-sourcing comes after the cutoff Their Cardano stack is promised as open source "in the coming months", after your keys are already dead. Self-hosting later is an option; it is not a migration plan for September. ### The endpoint migration map Every Maestro endpoint you call today, mapped to its Nexus destination. Swap the base URL and the auth header, keep shipping. Sample mapping of Maestro endpoints to their Nexus equivalents Maestro endpoint | | Nexus endpoint | /addresses/{addr}/utxos | → | /api/addresses/{address}/utxos | /addresses/{addr}/transactions | → | /api/addresses/{address}/transactions/history | /transactions/{tx_hash} | → | /api/transactions/{txHash} | /txmanager (submit) | → | /api/transactions/submit | /assets/{asset} | → | /api/assets/detailedInfo?assetPolicy=&assetName= | /pools/{pool_id}/info | → | /api/pools/{poolId} | /datums/{datum_hash} | → | /api/scripts/datum/{datumHash} | btc /addresses/{addr}/utxos | → | /api/btc/addresses/{address}/utxos | btc inscriptions by address | → | /api/btc/addresses/{address}/ordinals | btc tx submit | → | /api/btc/txs/submit | A sample of the full map, which covers every Cardano and Bitcoin endpoint group. See the complete migration map or browse the API reference with a live playground on every endpoint. Following Maestro's pointer to Blockfrost? Nexus speaks the Blockfrost API too: point any Blockfrost SDK at /api/v0 and your code keeps working. Compare Nexus and Blockfrost ### What differs, and what has no equivalent The map above is the direct matches. These two lists are the rest, so you find them here and not in production. #### Same data, different shape - Auth and base URL X-Api-Key: nxs_... on https://nexus.gerowallet.io, no /v1 segment. Network is a query parameter, not a host. - Paging on newer reads cursor and limit with an opaque nextCursor. The older reads keep page and pageSize. Never carry a Maestro cursor across. - Address utxo_refs No reference-only route. Read /utxos and project {txHash, outputIndex} client-side. - Address decode The address moves to the end of the path: /api/addresses/decode/{address}. Byron addresses report no credentials. - Confirmation tracking Submit returns and you poll /api/transactions/{txHash}, or subscribe over WebSocket streaming where your plan includes it. - Bitcoin inscription fields satOffset, vout and txid are parsed out of the satpoint. runes[].runeId replaces rune_id. - Bitcoin mempool UTXOs Delete the second call. Unconfirmed UTXOs arrive in the main response with status.confirmed=false. #### No Nexus equivalent today - GET /policy/{policy} summary root Every sub-resource (assets, utxos, mints, addresses, accounts, transactions) is mapped. Only the one aggregate document is not. - GET /pools/{pool_id}/delegators/{epoch_no} Only the newest stake snapshot is readable. Historical delegator lists are not available. - Transaction Manager: turbosubmit, state, history, webhooks POST /txmanager maps to /api/transactions/submit. The rest does not exist on Nexus. - Managed Contracts (vesting, direct swap, staking, multisig) Application logic, not chain data. There is no surface to migrate it onto. - Bitcoin utxo_block_height and utxo_confirmations Not returned on inscription listings. Need one of these? Email nexus@gerowallet.io before you migrate and we will tell you the date or the workaround. ### Maestro vs Nexus at a glance Same chains, simpler math. Flat requests instead of credit weights, and a platform that is still here after Sep 18. Feature and pricing comparison between Maestro and Nexus Dimension | Maestro (retiring) | Nexus | Metering | Compute credits, per-endpoint weights unpublished | Requests. One request is one request, even the big ones | Entry paid plan | Conductor $49, 4M credits/mo | Starter $9, 3M requests/mo. Builder $29, 10M requests/mo | Production tier | Virtuoso $199, 16M credits/mo | Scale $199, 50M requests/mo at 100 req/s | Rate limits | 100 req/s on Conductor | 25 req/s with a 250-request burst on Builder. Growth and Scale run 50 and 100 req/s, bursts 500 and 1,000 | Chains | Bitcoin, Cardano, Dogecoin | Bitcoin, Cardano and Midnight, live today | Push data | Webhooks | WebSocket streaming, snapshot first, then live updates | After Sep 18 | All endpoints retired | In production, with a public status page at status.gerowallet.io | Maestro figures from their last published pricing page. Nexus figures reflect current plans; see the pricing page for detail, including add-ons. Spot an error? Email nexus@gerowallet.io and we will fix it. Start the 7-day Builder trial ### Why not the free one ? Koios is a community-run Cardano API and it is genuinely free. For Cardano-only reads under 50,000 requests a day, with best-effort uptime, it is a good answer. Here is where it stops. Koios tiers compared with Nexus plans Dimension | Koios | Nexus | Price | Public and registered plans at $0. Pro ~$29.99/mo, Premium ~$74.99/mo | Starter $9/mo, Builder $29/mo, Growth $79/mo, Scale $199/mo | Daily requests | 5,000 public, 50,000 Free with a key, 500,000 Pro, 1.2M Premium | 3M, 10M, 30M and 50M per month, no daily reset | Rate limit | 100 requests per 10 seconds on public and Free, 250 on Pro, 500 on Premium | 25 req/s on Builder, 50 on Growth, 100 on Scale, with bursts | Query timeout | 30 seconds on public and Free, then HTTP 504 | Per-endpoint timeouts behind our own indexers plus Yaci, Koios and Blockfrost as fallbacks | Chains | Cardano only | Cardano, Bitcoin and Midnight on the same account | Beyond chain reads | Chain data. No market data, streaming, transaction builder or wallet analytics | Market data across 11 DEXes, WebSocket streaming, transaction builder, wallet analytics, MCP server | Who runs it | A community of node operators, open source, best-effort support | A.D. Labs, the GeroWallet team, with a named engineer on your migration | Koios figures from koios.rest/tiers.html , checked September 2026. Koios is also one of the fallback providers behind Nexus chain reads, so choosing Nexus does not mean leaving it behind. ### Migration questions, answered How long does migrating from Maestro take? For chain-data reads, most teams finish in a day or two using the endpoint map above: same concepts, different paths and auth header. Transaction submission is a same-day change. If you want help, ask for an engineer on the migration and you will get a named person, not a ticket queue. What replaces MaestroProvider in my code? The official TypeScript SDK, @adlabs/nexus on npm, covers Cardano, Bitcoin and Midnight over REST. Mesh has a merged NexusProvider, a Lucid Evolution provider PR is open, and code written against Blockfrost SDKs points at the Blockfrost-compatible endpoint at https://nexus.gerowallet.io/api/v0. What happens to my Maestro keys on Sep 18? Per Maestro's own announcement, every endpoint is retired and keys stop working that day, across Bitcoin, Cardano and Dogecoin. Nothing on your side survives the date. Anything still calling their API on Sep 19 fails. Is Nexus free to use? No. Nexus is paid infrastructure, from $9/mo on Starter, with a 7-day trial on Builder, card required. Every plan covers Cardano, Bitcoin and Midnight on the same account, and each key is scoped to a single chain and network. ### Move before the panic week Both APIs run side by side until Sep 18. Start the trial today, switch reads over with the map, and be done while everyone else is still opening tickets. Start the 7-day Builder trial keys retire Sep 18, 2026 Read the docs See pricing Check live status Nexus vs Blockfrost Full migration guide --- # Get Started: Nexus Blockchain API URL: https://nexus.gerowallet.io/get-started/ Description: Create your Nexus account or sign in to access blockchain data APIs, manage API keys, and start building with Cardano, Midnight, and Bitcoin. ## Get started with Nexus Create your account or sign in to get API keys for Cardano, Bitcoin and Midnight data, market data and transactions. --- # Support: Nexus Blockchain API URL: https://nexus.gerowallet.io/support/ Description: Get help with Nexus: reach the team, browse API documentation, check service status, and find answers about our Cardano, Midnight, and Bitcoin data API. Support ## How can we help? Pick a channel below or browse the FAQ. We typically reply within one business day. ### Email support Direct line to the Nexus team for technical and billing questions. Typical reply within one business day. nexus@gerowallet.io ### API documentation Every endpoint, request shape, and response model, with a built-in try-it console on each page. Open docs ### Community & status Join the Discord for real-time help, peer support, and API status updates. Join the Discord ### Frequently asked questions I just subscribed but I don't see a dashboard yet. PayPal subscriptions activate in seconds; AllPay can take up to a minute for the webhook to confirm payment. Refresh the dashboard, or if it persists past 5 minutes, email us with your account email. How do I generate or rotate API keys? Dashboard → API Keys. Click "Create key", choose the network, and copy the key (it is shown only once). Existing keys can be revoked from the same page; replacements are issued immediately. What happens when I hit my rate limit? Requests above your plan limit return HTTP 429 with a Retry-After header. Upgrade from Dashboard → Subscription to take effect on the next request, with no downtime. Can I cancel anytime? Yes. Dashboard → Billing → "Cancel subscription". Access continues until the end of the current billing period. For trial users, no charge is made if you cancel before the trial ends. My swap did not go through, but I paid fees. Do I get them back? If a Minswap V2 market swap built by Nexus or the Gero swap widget is returned unfilled because the price moved past its slippage limit, we refund the aggregator fee, the partner fee and the batcher fee the DEX kept, to the wallet the swap was returned to. You do not need to ask. Network fees are not refunded. The refund arrives in a transaction tagged "Gero swap fee refund". If you think we missed one, email nexus@gerowallet.io with the swap's transaction hash. Still stuck? Email the team Follow us - - - - - - - --- # Privacy Policy: Nexus Blockchain API URL: https://nexus.gerowallet.io/privacy/ Description: How Nexus collects, uses, stores, and protects your personal information. The privacy policy for our multi-chain data API, operated by A.D. Labs LTD. ## Privacy Policy Last updated 30 October 2026 This Privacy Policy describes how A.D. Labs LTD, company number 517029245 (“Gero”, “we”, “us”, “our”), a company incorporated and registered in Israel with its registered address at Balfur, Bat Yam, Israel, collects, uses, stores, and protects personal information when you use the Gero Nexus service at https://nexus.gerowallet.io and any associated dashboards, APIs, and documentation (the “Service”). By using the Service you acknowledge that you have read and understood this Policy. If you do not agree with this Policy, please do not use the Service. ### 1. What we collect #### 1.1 Information you provide - Account registration data: name, email address, password (stored only as a salted hash), and where applicable organisation name and billing address. - Subscription and billing data: plan selected, add-ons enabled, subscription status, and invoice history. Full payment-card numbers and bank-account credentials are submitted directly to our payment processors (PayPal, AllPay) and are not stored on our servers. - Communications: the content of support requests, bug reports, and any other correspondence you send us. - Optional profile data: display name and other fields you choose to add to your Nexus account. #### 1.2 Information collected automatically - API usage logs: timestamps, endpoint paths, API-key identifiers, response codes, response times, and aggregated request volumes. These are used to enforce plan quotas and rate limits, to detect abuse, to bill correctly, and to operate and improve the Service. Logs may include the IP address from which a request was sent. - Web analytics: aggregated, mostly anonymised information about visits to nexus.gerowallet.io, including pages viewed, referral source, and approximate geographic region. - Authentication and security events: sign-in attempts, password-reset events, email-verification events, and suspicious-activity flags. These are used for account security and fraud prevention. - Cookies: see Section 8 below. #### 1.3 Information we do not collect - We do not custody crypto-currency balances, private keys, or seed phrases. Nexus is a data-API service; it does not hold or move funds. - We do not collect biometric data. - We do not collect end-users' personal data on behalf of your application. If your application sends us identifiers belonging to your end-users, that data flows through our infrastructure as part of your API request — we treat it as Customer Data under the Terms of Service and do not use it for our own purposes. ### 2. How we use your information We use the information described in Section 1 to: - provide, operate, and maintain the Service; - authenticate your account and authorise API requests; - meter usage, enforce plan quotas, and produce invoices; - process subscription payments through PayPal and AllPay; - communicate with you about your account, security, billing, and material changes to the Service; - respond to support requests; - detect, investigate, and prevent fraud, abuse, and security incidents; - comply with applicable laws, including tax, sanctions, and anti-money-laundering obligations; - improve the Service through aggregated analytics and product research. ### 3. Legal bases for processing We process personal data under the Israeli Privacy Protection Law, 5741-1981, as most recently amended by Amendment 13 (in force from August 2025), and, where applicable, under the EU General Data Protection Regulation (Regulation (EU) 2016/679) and the UK GDPR. If you are located in the European Economic Area or the United Kingdom, the legal bases on which we process your personal data are: - performance of a contract — to provide the Service you have subscribed to; - legitimate interests — to operate, secure, and improve the Service, prevent fraud, and develop our business, where those interests are not overridden by your rights; - compliance with a legal obligation — for example, retaining transaction records for tax purposes; - consent — for any optional processing for which we ask your consent (such as marketing communications), which you may withdraw at any time. ### 4. Sub-processors and third parties We share personal data with the following categories of third parties strictly to the extent needed for them to perform their function: - Payment processors — PayPal and AllPay. They receive payment-card or account data necessary to charge your subscription, plus minimal account identifiers (email, customer ID). Their handling of that data is governed by their own privacy policies. - Cloud hosting and infrastructure — providers that host the Nexus application, database, and logs. They process Customer Data only to the extent necessary to operate the underlying compute and storage on our behalf. - Email and communication services — providers used to deliver transactional email (sign-up confirmation, email verification, billing notices, security alerts) and support correspondence. - Analytics — providers used to measure aggregated traffic on nexus.gerowallet.io. Where possible we configure these in a privacy-preserving way (IP anonymisation, no advertising cookies). - Professional advisers — lawyers, accountants, and auditors, where strictly necessary and under confidentiality obligations. - Authorities — where compelled by valid legal process or to protect the rights, property, or safety of Gero, our Customers, or the public. We do not sell personal data. ### 5. International data transfers We are based in Israel, which has been recognised by the European Commission as providing an adequate level of data protection. Some of our sub-processors are located outside Israel and the EEA. Where data is transferred outside the EEA or UK to a country without an adequacy decision, we use Standard Contractual Clauses or other lawful transfer mechanisms. ### 6. Data retention - Account data — retained for as long as your Nexus account is active, plus a reasonable period after closure for record-keeping, dispute resolution, and compliance (typically up to seven years for billing records, as required by tax law). - API usage logs — retained at full granularity for an operational window (typically up to ninety (90) days), after which they are aggregated or deleted. Aggregated, non-personal usage statistics may be retained indefinitely. - Support correspondence — retained for as long as needed to handle the inquiry and a reasonable period thereafter for quality assurance. - Billing records — retained as long as required by applicable tax and accounting law. ### 7. Security We implement appropriate technical and organisational measures to protect personal data, including: - HTTPS/TLS encryption for all data in transit between you and the Service; - encryption at rest for sensitive fields, including hashed passwords and API-key secrets; - access controls limiting which personnel can access production systems; - regular security review of dependencies and infrastructure; - strict scoping of API keys to the account that issued them. No system is perfectly secure. If you suspect your account or an API key has been compromised, contact us immediately at support@nexus.gerowallet.io and rotate the affected API key from the dashboard. ### 8. Cookies and similar technologies We use cookies and similar technologies on nexus.gerowallet.io for: - strictly necessary purposes — keeping you signed in (HttpOnly access and refresh tokens), maintaining a non-sensitive session marker readable by the dashboard, and operating the site. These cannot be disabled without breaking the site. - analytics — measuring aggregated visit patterns to improve the site. Where local law requires, we ask for your consent before setting analytics cookies. - referral attribution: when you follow a partner's referral link, we set a first-party cookie named nexus_ref that holds the partner's referral code, so that we can credit the partner who referred you if you then create an account. It is kept for 90 days. It is used for nothing else: not for advertising, and not to follow you to other sites. We do not use cookies for advertising or for cross-site tracking. ### 9. Your rights Depending on your location you may have some or all of the following rights: - access — request a copy of the personal data we hold about you; - rectification — correct inaccurate or incomplete data; - erasure — request deletion of your data, subject to legal retention obligations; - restriction — ask us to limit how we process your data; - portability — receive your data in a structured, machine-readable format; - objection — object to processing based on legitimate interests, including for direct marketing; - withdraw consent — at any time, where processing is based on consent; - lodge a complaint — with the data-protection authority in your country of residence (in Israel, the Privacy Protection Authority). To exercise these rights, contact support@nexus.gerowallet.io . We will respond within the timeframes required by applicable law. ### 10. Children The Service is not directed to children under the age of eighteen (18) and we do not knowingly collect personal data from children. If you believe a child has provided us with personal data, contact us and we will delete it. ### 11. Changes to this Policy We may update this Policy from time to time. The “Last updated” date at the top of the page reflects the most recent revision. For material changes we will use reasonable efforts to notify you in advance — for example, by email or by a notice on the Nexus dashboard. ### 12. Contact A.D. Labs LTD Company number 517029245 Attn: Privacy / Legal Department Balfur, Bat Yam, Israel support@nexus.gerowallet.io ← Back to home --- # Terms of Service: Nexus Blockchain API URL: https://nexus.gerowallet.io/terms/ Description: Terms of Service for Nexus, the managed multi-chain blockchain data API for Cardano, Midnight, and Bitcoin, operated by A.D. Labs LTD. ## Terms of Service Last updated 14 October 2026 Welcome to Gero Nexus. These Terms of Service (“Terms”) form a binding agreement between you (“you”, “Customer”, “Developer”) and A.D. Labs LTD, company number 517029245, a company incorporated and registered in Israel with its registered address at Balfur, Bat Yam, Israel (“Gero”, “we”, “us”, “our”). These Terms govern your access to and use of the Gero Nexus service available at https://nexus.gerowallet.io and any associated dashboards, APIs, SDKs, and documentation (collectively, the “Service”). By creating a Nexus account, generating an API key, or otherwise accessing the Service, you confirm that you have read, understood, and agreed to these Terms, including the dispute-resolution clause in Section 13. We may update these Terms from time to time. The “Last updated” date above reflects the most recent revision. Where changes are material we will use reasonable efforts to notify you in advance, for example by email to the address on your account or by a prominent notice in the Nexus dashboard. Continued use of the Service after an update takes effect constitutes acceptance of the updated Terms. ### 1. Eligibility and Account Registration 1.1 You must be at least eighteen (18) years old, or the age of majority in your country of residence (whichever is higher), and legally capable of entering into binding contracts. If you register on behalf of a company or other legal entity, you represent that you have authority to bind that entity, in which case “you” refers to that entity. 1.2 To use the Service you must register a Nexus account and provide accurate, current, and complete information, including a valid email address. You agree to keep your account information up to date and to notify us promptly of any changes. 1.3 You are responsible for all activity that occurs under your account, including activity by employees, contractors, or any other persons to whom you grant access. You must keep your account credentials and API keys confidential and must not share them publicly, commit them to source control, or expose them in client-side code. 1.4 We may refuse to open an account, limit the number of accounts you may hold, or suspend or terminate any account, in our reasonable discretion, including where we suspect fraud, abuse, or breach of these Terms. ### 2. The Service 2.1 Gero Nexus is a developer-facing API gateway that aggregates blockchain data from multiple networks (currently including Cardano, Midnight, and Bitcoin) and exposes it through a unified HTTP and WebSocket interface. Specific endpoints, data categories, and features are described in our published documentation and may change from time to time. 2.2 The Service is sold on a subscription basis under the plans described on our pricing page (currently Starter, Builder, Growth, and Scale self-serve tiers, plus Enterprise and Dedicated tiers). Each plan specifies a monthly request quota, rate-limit ceiling, API-key allowance, and feature set. Optional add-ons (such as Market Data, Wallet Analytics, Transaction Builder, and WebSocket Streaming packages) may be enabled separately on the plans that offer them, individually or as bundles. Plans, prices, quotas, add-ons, and features may change; we will give reasonable advance notice of material changes that affect your existing subscription. 2.3 A free trial may be offered on selected plans (for example, the Builder plan) for the duration stated on the pricing page. Trials may be discontinued or modified at any time and are subject to fair and reasonable use. 2.4 Nexus is a service for accessing blockchain data through our infrastructure. It is not itself a wallet, custody service, broker, exchange, or money-transmission business. We do not custody Customer funds, hold private keys, or execute trades on behalf of Customers. Where data returned by the Service originates from public blockchain networks, we do not warrant the accuracy or finality of that data — see Section 8. ### 3. API Keys and Acceptable Use 3.1 Each Nexus account may generate one or more API keys, up to the limit specified by your plan. API keys authenticate your requests to the Service and are used to enforce your plan's quota and rate limits. You must treat API keys as confidential credentials. You must not share them with third parties, embed them in unprotected client-side applications, or permit any party unauthorised by you to use them. 3.2 You agree not to: - use the Service in violation of applicable law, including sanctions administered by the European Union, United Nations, United Kingdom, United States (including OFAC), or Israel; - attempt to bypass, disable, or interfere with rate limits, quota enforcement, authentication, or any other security feature of the Service; - reverse-engineer, decompile, or attempt to derive the source code of the Service, except to the extent expressly permitted by applicable law; - resell, sublicense, or redistribute the Service or the data it returns as a stand-alone product or as a meaningful part of a product whose primary value is the data we provide, without our prior written consent; - use the Service to build a product that competes directly with the Service; - use the Service to send spam, conduct denial-of-service attacks, distribute malware, or harass others; - make systematic queries to the Service for the purpose of extracting, replicating, or training a substitute product on the underlying data, models, or indexes that power the Service; or - use the Service to facilitate or engage in any activity prohibited by Appendix A (Prohibited Use) below. 3.3 We may monitor your use of the Service for compliance with these Terms and to maintain service quality. We may suspend, throttle, or terminate access without notice where we reasonably believe your use threatens the stability or security of the Service or the rights or safety of others. ### 4. Plans, Fees, Billing, and Payment Processors 4.1 Subscription fees are charged in advance on a monthly cycle in US dollars (USD), unless another currency is expressly agreed for your plan. The renewal date for each billing cycle is the same calendar day each month as the date you first subscribed (or the last day of the month if a given month is shorter). All fees are exclusive of applicable taxes, which you are responsible for paying. 4.2 We process payments through authorised third-party payment processors, currently PayPal (for payments funded from a PayPal balance or linked bank account) and AllPay (for card, Apple Pay, and Google Pay payments). By submitting payment information you authorise the relevant processor to charge your chosen payment method, and you agree to that processor's terms of service and privacy policy in addition to these Terms. We do not store full payment-card numbers or bank-account credentials on our servers; that data is held by the relevant payment processor under its own PCI-DSS-compliant infrastructure. 4.3 Cancellation. You may cancel your subscription at any time through the Nexus dashboard. Cancellation takes effect at the end of the then-current billing cycle; you will retain access to your plan's features until that date and will not be charged for the next cycle. 4.4 Refunds. Subscription fees are non-refundable except where required by applicable law. This refund policy is published as part of these Terms so that customers may review it before purchase. If you believe you have been charged in error, contact us at support@nexus.gerowallet.io within thirty (30) days of the charge and we will investigate in good faith. Where we determine an error has been made, we will refund the affected charge to the original payment method. 4.5 EEA / UK consumer right of withdrawal. If you are a consumer (acting outside your trade, business, craft, or profession) and you are resident in the European Economic Area or the United Kingdom, you have the right to withdraw from the subscription contract within fourteen (14) days of its conclusion, without giving any reason. To exercise this right, send a clear statement of withdrawal to support@nexus.gerowallet.io before the 14-day period expires. Where you have begun using the Service during the withdrawal period, you may be charged an amount proportionate to the use you have made of the Service up to the point of withdrawal, and the balance (if any) will be refunded to your original payment method. This right does not apply to subscriptions purchased on behalf of a business or other legal entity. 4.6 Failed payments. If a scheduled payment fails we may retry the charge, suspend the account, or downgrade the plan. We will send a reminder to the email address on your account before suspending or downgrading. 4.7 Chargebacks. Initiating a chargeback for a legitimate charge, instead of contacting us first to resolve a billing dispute, is a breach of these Terms. Where a chargeback is initiated for a charge we determine to be legitimate, we may suspend or terminate the affected account, recover the disputed amount and any associated fees, and we will not re-attempt the charge against the cardholder where doing so would breach the payment-processor or card-network rules. ### 5. Service Availability, Quality, and Support 5.1 We aim to maintain high service availability but do not guarantee that the Service will be uninterrupted, error-free, or perfectly accurate. The Service may be subject to scheduled maintenance, unscheduled outages, or degradation caused by upstream blockchain-network conditions, third-party providers, or force-majeure events. 5.2 Where a written service-level agreement (SLA) has been agreed for your plan (for example, certain Enterprise or Dedicated engagements), the specific service-level commitments and remedies for that plan are set out in that SLA. In the absence of an explicit SLA, the Service is provided on a commercially reasonable best-efforts basis. 5.3 Standard support is available via email at support@nexus.gerowallet.io . Higher-tier plans may include priority or dedicated support as described on the pricing page. ### 6. Customer Data and Confidentiality 6.1 “Customer Data” means any data you submit to the Service, including request parameters, account metadata, and any content embedded in your applications that calls the Service. You retain ownership of Customer Data. 6.2 You grant us a limited, non-exclusive, worldwide, royalty-free licence to host, process, and transmit Customer Data solely as necessary to operate, maintain, and improve the Service for you, to enforce these Terms, and to comply with applicable law. 6.3 We treat your account information and any non-public Customer Data as confidential. We will not sell Customer Data and will not disclose it except: (a) to authorised sub-processors as described in our Privacy Policy; (b) where required by law, court order, or binding regulator request; or (c) with your consent. 6.4 Public blockchain data is, by its nature, not confidential. The Service returns data sourced from public ledgers; nothing in these Terms restricts the return of such public data to other Customers in response to their own requests. ### 7. Intellectual Property 7.1 We and our licensors own all right, title, and interest in and to the Service, including the underlying software, infrastructure, documentation, and the “Gero”, “Gero Nexus”, and related logos and trade dress. We grant you a limited, non-exclusive, non-transferable, revocable licence to access and use the Service for your internal business purposes during your subscription, subject to these Terms. 7.2 Feedback you voluntarily provide about the Service (suggestions, ideas, bug reports) is non-confidential, and you grant us a perpetual, irrevocable, royalty-free licence to use it for any purpose without obligation to you. 7.3 Open source. Portions of the Service may include open source components made available under their respective licences; those licences govern your use of those components. ### 8. Disclaimers 8.1 The Service is provided “as is” and “as available” without warranties of any kind, express or implied, to the maximum extent permitted by applicable law, including implied warranties of merchantability, fitness for a particular purpose, accuracy of data, non-infringement, and quiet enjoyment. 8.2 Blockchain data risk. The Service surfaces data from public blockchain networks. We do not control those networks. Network forks, re-orgs, indexer lag, mempool volatility, and protocol-level changes may cause the data we return to differ from on-chain truth at any moment. You are solely responsible for any decision you make based on data returned by the Service. 8.3 Third-party providers. The Service relies on upstream data and infrastructure providers (including but not limited to Cardano, Midnight, and Bitcoin node operators, public indexers, cloud-hosting providers, and other ecosystem participants). We are not responsible for the acts, omissions, or availability of those providers. 8.4 No financial, investment, tax, or legal advice is given by the Service or by us. 8.5 Derived and market data. Some data the Service provides is computed or derived by us from underlying blockchain sources, including token prices, weighted or aggregated prices, market-data metrics, historical candles, and analytics. This derived data is provided for general informational purposes only. It may be delayed, incomplete, or inaccurate, and may be corrected or restated at any time. It is not a price feed, oracle, index, valuation, or benchmark, and must not be relied upon as the sole basis for any financial decision, including lending, collateral valuation, liquidation, trading, settlement, or risk management. You are solely responsible for independently verifying any data before acting on it and for any loss arising from your reliance on it. Sections 8.1, 9, and 10 apply in full to derived and market data. ### 9. Limitation of Liability 9.1 To the maximum extent permitted by applicable law, in no event will we, our affiliates, or our directors, employees, or agents be liable to you or any third party for any indirect, consequential, incidental, special, exemplary, or punitive damages, including lost profits, lost data, or business-interruption damages, arising out of or relating to the Service or these Terms, even if we have been advised of the possibility of such damages. 9.2 Our total aggregate liability for any cause whatsoever, regardless of the form of action, is limited to the greater of (a) the fees you paid us for the Service in the twelve (12) months immediately preceding the event giving rise to the claim, or (b) one hundred US dollars (US$100). 9.3 Nothing in these Terms limits or excludes liability for: (i) death or personal injury caused by negligence; (ii) fraud or fraudulent misrepresentation; or (iii) any liability that cannot be limited or excluded under applicable law. ### 10. Indemnity You agree to indemnify and hold harmless A.D. Labs LTD, its affiliates, and their respective directors, officers, employees, and agents from and against any claim, demand, loss, liability, damage, or expense (including reasonable legal fees) arising out of or relating to: (a) your use of the Service in breach of these Terms; (b) your violation of any law or the rights of any third party; or (c) any product or service you build using the Service. ### 11. Term, Suspension, and Termination 11.1 These Terms apply for as long as you use the Service. 11.2 You may terminate at any time by cancelling your subscription and discontinuing use of the Service. Cancellation rules are described in Section 4.3, and the EEA / UK 14-day right of withdrawal is described in Section 4.5. 11.3 We may suspend or terminate your account, with or without notice, where: (a) you have materially breached these Terms; (b) we are required to do so by law, court order, or sanctions programme; (c) we reasonably believe continued service poses a security or stability risk; or (d) you have failed to pay applicable fees. 11.4 On termination, your right to access the Service ends immediately and we may delete API keys and account-level configuration. Sections that by their nature should survive termination — including Sections 6 (Confidentiality), 7 (Intellectual Property), 8 (Disclaimers), 9 (Limitation of Liability), 10 (Indemnity), 13 (Dispute Resolution), and any unpaid-fee obligations — survive termination. ### 12. Electronic Communications By creating a Nexus account, you consent to receive electronically all notices, disclosures, and other communications we provide in connection with your account and the Service, including communications about changes to these Terms, billing, security, and service updates. You may withdraw this consent by closing your account; withdrawing consent without closing your account is not practical given the electronic-only nature of the Service. ### 13. Governing Law and Dispute Resolution 13.1 These Terms and any non-contractual obligations arising out of or in connection with them are governed by the laws of the State of Israel, without regard to its conflict-of-laws rules. This choice of law does not deprive consumers of mandatory protections of the law of their habitual residence. 13.2 Informal resolution. Before filing any legal claim, you agree to contact us at support@nexus.gerowallet.io and to attempt in good faith to resolve the dispute informally for at least thirty (30) days. 13.3 Forum. - For Customers located in the European Union or European Economic Area, you may bring proceedings in the courts of your country of residence; you may also use the European Commission's Online Dispute Resolution platform. - For all other Customers, including Customers located in Israel, the courts of Tel Aviv-Jaffa, Israel have exclusive jurisdiction, save for mandatory consumer-protection rules in your jurisdiction that provide otherwise. ### 14. General 14.1 Entire agreement. These Terms, together with the Privacy Policy and any plan-specific SLAs or order forms, are the entire agreement between you and us regarding the Service. 14.2 Severability. If any provision of these Terms is held to be invalid or unenforceable, it will be enforced to the maximum extent permitted by law, and the remaining provisions will remain in full force. 14.3 No waiver. Our failure to enforce any right is not a waiver of that right. 14.4 Assignment. You may not assign these Terms without our prior written consent. We may assign these Terms in connection with a merger, acquisition, sale of assets, or by operation of law, with notice to you. 14.5 Force majeure. We are not liable for delays or failures caused by events beyond our reasonable control, including acts of God, war, terrorism, pandemic, civil unrest, labour disputes, telecommunications failures, internet-service-provider failures, and governmental action. 14.6 Notices. Notices to us must be sent to support@nexus.gerowallet.io or in writing to A.D. Labs LTD, Balfur, Bat Yam, Israel, attn. Legal Department. Notices to you will be sent to the email address on your Nexus account. 14.7 Relationship. The parties are independent contractors. These Terms create no partnership, agency, joint venture, or employment relationship. ### Appendix A: Prohibited Use You may not use the Service, directly or indirectly, to: - facilitate sanctions evasion, money laundering, terrorist financing, or other financial crime; - facilitate fraud, deception, or theft against any person; - send spam, run denial-of-service attacks, or distribute malware; - infringe the intellectual-property or privacy rights of others; - operate gambling services in a jurisdiction where doing so requires a licence you do not hold; - engage in the sale of regulated products (firearms, controlled substances, etc.) in a jurisdiction where doing so requires a licence you do not hold; - harvest, scrape, or aggregate the Service's data in a manner that violates these Terms; or - act for or on behalf of any individual or entity subject to applicable sanctions. ### Contact Questions about these Terms should be sent to: A.D. Labs LTD Company number 517029245 Attn: Legal Department Balfur, Bat Yam, Israel support@nexus.gerowallet.io ← Back to home --- # API reference Every endpoint, with request and response shapes: https://nexus.gerowallet.io/docs/llms-full.txt Per-page markdown is also served, e.g. https://nexus.gerowallet.io/docs/introduction.md