Terms of Service
These terms govern your access to and use of the NodeFlare API, dashboard, and related services. By creating an account or making any API request you agree to be bound by them.
Acceptance of Terms
By registering an account, generating an API key, or otherwise accessing or using the NodeFlare platform (“Service”), you agree to these Terms of Service (“Terms”) in full. If you are agreeing on behalf of an organisation, you represent that you have the authority to bind that organisation.
If you do not agree to these Terms, you must not use the Service. Continued use of the Service after any update to these Terms constitutes acceptance of the revised Terms.
The Service
NodeFlare provides JSON-RPC access to EVM-compatible blockchain networks via HTTPS endpoints. Access is authenticated with an API key tied to your account and plan. We may add, modify, or discontinue specific chains or features at any time with reasonable notice.
The Service is provided for use in building and operating decentralised applications, blockchain tooling, and data infrastructure. Consumer-facing deployments that embed NodeFlare endpoints must not expose your API key to end users.
Acceptable Use
You may use the Service for lawful purposes only. The following are strictly prohibited:
- Reselling, sublicensing, or white-labelling API access without prior written permission from NodeFlare.
- Circumventing, disabling, or otherwise working around rate limits, usage quotas, or authentication mechanisms.
- Using the Service in connection with illegal activity, market manipulation, fraud, money laundering, or sanctions evasion.
- Probing, scanning, or testing the infrastructure or network for vulnerabilities without written authorisation.
- Embedding or committing your API key in publicly accessible source code repositories or client-side applications.
- Sending artificially inflated traffic, automated stress tests, or abusive request patterns not representative of legitimate use.
- Interfering with or disrupting the integrity or performance of the Service or its underlying infrastructure.
Violation of this section may result in immediate suspension or termination of your account without refund.
Plans & Billing
NodeFlare offers a free tier and paid monthly plans as described on the pricing page. Paid plans are billed monthly in advance. Plan upgrades take effect immediately; downgrades apply at the start of the next billing cycle.
The Free plan is not a time-limited trial. We currently do not automatically expire Free accounts or API keys solely because of inactivity. Monthly quota exhaustion limits further requests rather than expiring the account; acceptable-use and suspension provisions still apply.
All prices are stated in US dollars (USD) and are exclusive of VAT and any other applicable sales tax. Tax is calculated at checkout from your billing country and shown before you pay. Business customers in the EU who supply a valid VAT identification number are invoiced under the reverse-charge procedure and are not charged VAT by us.
- Unused monthly compute units do not roll over. Purchased extra CU follow the separate top-up terms shown at purchase.
- We reserve the right to change pricing with 30 days' written notice to the email address on your account.
- Crypto payments are converted at the prevailing market rate at the time of payment. Crypto payments are non-refundable once confirmed on-chain.
- Card payments may be refunded within 14 days of the charge for unused subscription time, at our discretion and where required by applicable law.
- Accounts more than 14 days past due may have API access suspended until the outstanding balance is cleared.
Rate Limits & Quotas
Each plan carries a per-second rate limit and a monthly compute-unit quota as detailed on the pricing page. These limits exist to ensure fair access for all users and the stability of the infrastructure.
- Requests exceeding the per-second rate limit receive an HTTP 429 response. You should implement exponential back-off retry logic.
- Requests made after the monthly quota is exhausted receive an HTTP 429 response until the next billing cycle begins or you purchase an add-on.
- Enterprise plans may negotiate custom limits under a separate agreement.
- NodeFlare reserves the right to apply temporary throttling during incidents or exceptional load conditions regardless of plan.
Uptime & SLA
Availability commitments differ per chain, because the infrastructure behind each chain differs. A chain served by NodeFlare nodes in five regions cannot honestly carry the same commitment as a chain served by a single machine. Each supported chain therefore falls into one of three tiers, and the tier — not a single headline figure — determines what is promised and whether service credits apply.
Uptime is measured as the percentage of one-minute intervals in a calendar month during which the NodeFlare endpoint for that chain responds to valid requests. Measurement is taken at our endpoint, which is the boundary we control.
Tier 1 — Multi-region · 99.9% · credits apply
NodeFlare-operated primary nodes are configured in two or more routing regions. Regional alternatives improve resilience but do not guarantee uninterrupted service. A public third-party RPC backstop is also configured for Ethereum, Base, BNB Chain, Arbitrum One and BOB, after our own nodes. Robinhood Chain has no public backstop. Chains: Ethereum, Base, BNB Chain, Arbitrum One, Robinhood Chain, BOB.
Tier 2 — Additional chains with failover · 99.5% · credits apply
NodeFlare-operated nodes serve these chains in one or more configured regions. A public third-party RPC backstop may serve a request when the available primary nodes cannot serve it. Currently supported chains in this tier: Optimism, Avalanche, HyperEVM, Unichain, Sonic, Polygon, XLayer, Soneium, Ink and Mode.
- The backstop disclosure also applies to Tier 1 chains where configured. Public fallback providers operate independently; contact [email protected] for routing and data-handling questions. Custom routing requires a separate agreement and confirmed configuration before use.
- During failover, the external provider receives the forwarded RPC request. Method support, historical depth and response latency may differ from our nodes; equivalence of capability is not promised.
- If a chain's NodeFlare node is withdrawn from service, that chain drops to Tier 3 — no committed percentage and no credits — for as long as it is served only by a third-party endpoint, regardless of the tier listed above.
Tier 3 — No committed percentage · commercially reasonable effort · no credits
Zircuit has one configured NodeFlare region and no public third-party backstop. This service is offered on a commercially reasonable effort basis unless a separate agreement specifies otherwise.
On successful HTTP RPC responses, nf-region: fallback identifies a public backstop response. A region value identifies the upstream routing region; nf-region: cache identifies a cached response, not its original upstream. Error responses may identify the gateway rather than a serving node. Historical state and tracing coverage depend on the node and requested block; a key does not guarantee complete archive coverage.
The 15 October routing clarification describes the current configuration. It does not retroactively waive prior commitments, accrued credit claims or separately agreed routing restrictions. The published monthly tier rule below continues to apply.
Exclusions and credits
- A chain's tier may change as infrastructure changes. The tier in force is the one published here on the first day of the calendar month in which an incident occurs.
- Scheduled maintenance windows announced at least 24 hours in advance are excluded from downtime calculations.
- Downtime caused by degradation of the underlying blockchain network itself — a chain halt, a consensus failure, a hard fork requiring client changes — is excluded on every tier.
- Downtime caused by your misuse of the API, exceeded quotas, or suspended account status is excluded.
- SLA credits apply to Tier 1 and Tier 2 chains only, are issued as account balance credit for the following billing cycle, carry no cash value and are non-transferable.
- To claim an SLA credit you must submit a request to [email protected] within 7 days of the incident.
- Enterprise agreements may vary any part of this section, including committed percentages, credit mechanics and dedicated capacity, in a separate signed contract that prevails over these Terms.
Intellectual Property
NodeFlare and its licensors retain all intellectual property rights in the Service, including but not limited to the API, dashboard, documentation, logos, and underlying software. Nothing in these Terms grants you any rights in our intellectual property beyond the limited licence to use the Service as described herein.
You retain ownership of any applications or data you create using the Service. You grant NodeFlare a limited, non-exclusive licence to process your requests solely to operate the Service.
Suspension & Termination
You may close your account at any time from the account settings page or by emailing [email protected]. On closure, your API key is revoked immediately and your data is deleted within 30 days, except where retention is required by law.
NodeFlare may suspend or terminate your account with immediate effect and without refund if:
- You breach the Acceptable Use policy (Section 03).
- Your account is more than 30 days past due.
- We are required to do so by law or a court order.
- We reasonably suspect fraudulent or abusive activity.
For less severe violations we will generally provide 7 days' notice and an opportunity to remedy the breach before termination.
Limitation of Liability
The Service is provided “as is” and “as available” without warranties of any kind, express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, or non-infringement.
To the maximum extent permitted by applicable law, NodeFlare shall not be liable for any indirect, incidental, special, consequential, or punitive damages arising from:
- API unavailability, latency, or incorrect responses.
- Blockchain reorganisations, forks, or network-level failures.
- Loss of funds, tokens, or assets resulting from your use of the Service.
- Unauthorised access to your account or API key due to your failure to maintain adequate security.
- Any third-party services you integrate with via NodeFlare endpoints.
Our total aggregate liability for any claims arising in any calendar month is limited to the total fees you paid to NodeFlare during that same calendar month.
Changes to These Terms
We may update these Terms at any time. For material changes — those that meaningfully affect your rights or obligations — we will provide at least 14 days' notice by email before the revised Terms take effect.
Non-material changes (such as clarifications, corrections, or new sections that do not restrict existing rights) may take effect immediately upon posting. The “Last updated” date at the top of this page reflects the most recent revision.
Governing Law
These Terms are governed by and construed in accordance with the laws of the Kingdom of the Netherlands, without regard to its conflict of law provisions. Any dispute arising from or relating to these Terms or the Service shall be subject to the exclusive jurisdiction of the competent courts of Amsterdam, the Netherlands.
If any provision of these Terms is found to be unenforceable, the remaining provisions shall continue in full force and effect.
Questions about this document?
Reach out and we'll get back to you within two business days.