Terms of Service

In these Terms:

By creating an Account, signing in to the Console or calling the Service, you confirm that you have read, understood and agree to these Terms.

We handle your personal information as described in our Privacy Policy.

The Pricing page, the Console and the documentation form part of this agreement. If they conflict with these Terms, these Terms prevail, except that specific prices, CU weights, Free Credit amounts and usage limits are as published on the Pricing page and in the Console at the relevant time, and technical rules, such as which requests are billed, how they are metered and the coverage of each network, are as set out in the documentation. Any change to the documented rules on which requests are billed, or how they are metered, that is adverse to you is subject to the notice period in Section 12 and the refunds in Section 11.

If you have signed a separate written agreement with us for the Service, that agreement governs the matters it covers, and these Terms govern everything else.

You must be at least 18 years old and have full legal capacity to enter into these Terms. The Service is not directed at anyone under 18.

If you use the Service on behalf of a company or other organization, you represent that you are authorized to accept these Terms on its behalf, and that organization is bound by them.

The Service is designed mainly for developers and businesses, but individuals may use it too. If you are a consumer protected by applicable law, nothing in these Terms affects the rights you have by law that cannot be excluded by contract.

You must also meet the requirements of Section 15 (Sanctions and compliance). If we have previously terminated your Account for breach of these Terms, you may not register a new one without our consent.

We provide the JSON-RPC API and the Data API for Supported Networks. Unless the documentation or the Console states otherwise, the same API key works on all Supported Networks, and Credits and rate limits are shared across all networks and across the JSON-RPC API and the Data API; they are not split by network.

Available methods, datasets, historical ranges and features differ by network, as stated on the Supported Chains page and in the documentation; not every method or feature is offered. BlockVectra is not affiliated with, or endorsed by, the developers, operators or foundations of the Supported Networks.

We provide access to, and queries of, blockchain data. We are not an exchange, broker, custodian or financial institution; we do not hold your digital assets or private keys, and we do not initiate, sign or execute transactions on your behalf.

The Service is at an early stage, and its features, interfaces, limits and Supported Networks may change more often than those of a mature service; such changes are governed by Section 20.

You can sign in to the Console with a wallet signature (externally owned account (EOA) wallets only; supported wallet types are as described on the sign-in page), a GitHub account or a Google account. When you sign in with a method that is not yet linked to any Account, a new Account is created for it automatically; separate Accounts have separate Credits, API keys and records. To prevent abuse, we may limit or pause new sign-ups.

Wallet sign-in only asks you to sign a sign-in message to prove that you control the wallet address. The signature creates no on-chain transaction and authorizes no transfer. We will never ask for your private key or seed phrase.

Always sign in with the method you used to create your Account, and keep that wallet or third-party account secure. If you lose every sign-in method for your Account (for example, the wallet you sign in with), you may be permanently unable to sign in to it, and we have no obligation to restore it. You may contact us with supporting material (such as top-up records), and we may, at our discretion, help verify your identity, but we do not guarantee that your Account can be restored. If your Account cannot be restored, you may request a refund of unused Paid Credits under Section 11.

An API key is the credential for calling the Service: anyone who has it can call the Service using your Account and consume your Credits. The full API key is shown only once, when it is created or rotated; we cannot show it to you again.

Keep your API keys confidential: do not put them in browser front-end code, client applications or public code repositories, and do not give them to anyone you have not authorized. If you suspect a key has been exposed, rotate or revoke it in the Console immediately. Rotation revokes the old key immediately, with no grace period; as with revocation, the old key stops working within a few seconds. Revocation cannot be undone.

All usage made with your API keys is treated as your usage and is charged to you, including usage by others after a key has been exposed, unless the exposure was caused by a security flaw on our side.

If we find that an API key may have been exposed or misused (for example, it appears in a public code repository), we may disable it and, where reasonably practicable, tell you. The number of API keys an Account can hold and how often keys can be created are subject to limits we set; the Console tells you when you reach a limit.

New Accounts may receive a sign-up grant of Free Credits and, if eligible, periodic top-ups, under the rules published on the Pricing page. The amount of Free Credits, the top-up rules, the per-second call cap and other free-plan terms are as published on the Pricing page and in the Console at the relevant time. While an Account is suspended, free top-ups are paused.

Each individual or organization may use only one Account on the free plan. Having more than one Account only because Accounts were created automatically for different sign-in methods is not a breach of this paragraph; we may treat those Accounts as belonging to the same user and disable the extra free Accounts.

We may change, pause or end the free plan at any time, and will announce this in advance where reasonably practicable. Free Credits already granted to your Account will not expire or be taken back as a result. However, if you obtained Free Credits through conduct prohibited by Section 13 (for example, credits in Accounts registered to obtain extra Free Credits), we may take them back when we discover it; this exception applies only to credits granted as a result of that conduct, not to Free Credits you obtained properly before.

After your Account's first paid top-up, it becomes a paid Account under the rules published on the Pricing page: it no longer receives periodic free top-ups, and the free plan's per-second call cap no longer applies. Any unused Free Credits stay in your Credits and can still be used.

All Accounts are subject to rate limits and other technical limits, such as request size, the number of calls in a batch, the range of a single query and the time limit for a single request, as described in the documentation and the Console. We may adjust these limits to protect the Service. Requests rejected for exceeding a limit are not billed; see Section 8 for how timeouts are billed. If you need higher limits, contact us.

We meter your calls in CU: each method or data endpoint is metered at its CU weight. CU weights, the conversion between CU and billing units, and the price of billing units are as published on the Pricing page and in the Console at the relevant time, and may differ by method, product or network. Usage is totalled for each settlement period and deducted from your Credits; see the Pricing page for how settlement works. You can view your usage, charges and top-ups in the Console; usage figures may lag slightly.

Our metering records are the basis for billing. If you believe they are wrong, you may dispute the charges through the contact email within 60 days after the end of the settlement period and provide supporting information; we will investigate and respond, and if we confirm a metering or charging error we will credit the corresponding amount back to your Account. If a failure of the nodes we use causes a large number of abnormal responses, we may also, at our discretion, credit back the corresponding amount. This paragraph does not affect your statutory rights.

The basic billing rules are as follows (the documentation has the full rules):

Credits are prepaid: you top up first and then use the Service. How to top up is described on the Pricing page and in the Console; we add Credits to your Account after we confirm receipt of your payment. The minimum top-up is shown on the Pricing page. The currencies, assets and networks we accept are those stated in the written instructions we provide for that top-up.

Pay only according to the written payment details we send you from the contact email for that top-up. We will never provide or change a payment address or account through any other channel; if in doubt, check with us through the contact email first.

On-chain payments cannot be reversed once sent. You bear any loss caused by sending funds on the wrong network, in the wrong asset or to the wrong address; however, if the funds actually reach an address or account we control, we will, after verification and deduction of the reasonable costs involved, credit them to your Account or return them to the originating address. If you underpay, we credit the amount actually received; if the amount received is below the minimum top-up, we will contact you and, at your choice, credit it or return it less fees. If funds have arrived but cannot be matched to your Account because payment information is missing, we will credit or return them once you provide enough information for us to verify. Network fees, bank charges and intermediary bank charges for a payment are borne by the payer. For stablecoin payments, Credits are added at the conversion we confirm in writing for that top-up before you pay and are not adjusted afterwards for changes in the coin's price; the payer bears the risk that a payment is frozen by a third party or cannot be redeemed before it reaches us.

To comply with law or manage risk, we may decline a top-up or, before adding Credits, ask you for information about your identity and the source of funds; if we decline a top-up, funds already received are returned, less fees, to the original paying account or address, except where the law requires them to be frozen or restricted. Some payment methods may not be available in all countries or regions.

Credits are a prepaid right to use the Service. They are not money, e-money, a deposit or a stored-value instrument. Credits bear no interest, have no cash value, and cannot be transferred, sold or moved between Accounts; except for refunds under Section 11, they can only be used to pay for the Service.

Credits, whether Free Credits or Paid Credits, do not expire.

When your available Credits run out, new requests are rejected until you top up or your Free Credits are topped up. Because settlement is not instantaneous, your Credits may go negative. Any negative amount will be deducted from your next top-up, and on a paid Account it is a fee you owe. On a free-plan Account, a negative amount is offset at the next free top-up, and we will not otherwise charge you for it. We may waive small negative amounts.

If a payment is recalled, reversed or charged back after Credits are added, or is frozen or must be returned by law because its source involves fraud, stolen assets or sanctions, we may deduct the corresponding Credits from your Account and suspend your Account; any part already used that cannot be deducted is a fee you owe.

Paid Credits are not refundable, except that you may request a refund of unused Paid Credits in the cases listed in this Section. Free Credits are not refundable. To the extent permitted by law, Paid Credits in an Account terminated for your serious breach of these Terms are not refundable.

The refundable amount is calculated as follows. (1) Unsettled usage is subtracted from your current Credits to give your "available Credits"; if available Credits are zero or less, nothing is refundable. (2) Free Credits are treated as used first, then Paid Credits in the order they were added. Your unused Paid Credits are therefore the lesser of your available Credits and the total of your paid top-ups not yet refunded, and are treated as coming from your most recent paid top-ups. (3) Each refund case covers only the unused Paid Credits it concerns; for example, the first case below covers only the unused part of that top-up. Example: if your Credits are worth USD 60, unsettled usage is worth USD 10 and you made two paid top-ups of USD 30 each, your available Credits are worth USD 50 and your unused Paid Credits are USD 50: all USD 30 of the later top-up and USD 20 of the earlier one.

When refunding, refundable billing units are converted back into the original payment currency at the conversion rate that applied when that top-up was credited, and the refund will not exceed the amount of that top-up we actually received. Refunds are made only to the original paying account or address; if that is not possible, we will agree another refund route with you after verifying that you control the original payment source. Network and bank fees for the refund are deducted from the refunded amount, and fees you bore when paying are not refunded, except where applicable law prohibits charging a consumer fees for a refund. Before refunding, we may verify your identity and the source of the payment; amounts that we are legally prohibited from paying are handled as the law requires.

You may request a refund in the following cases:

We may change prices, CU weights and the conversion rate for billing units. We will announce any change that is adverse to you (such as a higher price or CU weight) at least 30 days in advance, in the manner described in Section 30; however, a change to particular methods or features made to comply with law, or to protect the Service from attack or abuse, may take effect as soon as it is announced. Changes in your favor (such as a price cut) may take effect as soon as they are announced. The first CU weight published for a newly launched method, dataset or network is not a change. Changes to the free plan are governed by Section 7.

Credits already added are kept as billing units; a change to the conversion between billing units and US dollars applies only to top-ups made after the change takes effect. If you do not accept an adverse change, you may stop using the Service before it takes effect or within 30 days after it takes effect, and request a refund of unused Paid Credits under Section 11.

Unless stated otherwise, prices exclude any applicable taxes. You are responsible for taxes arising from your use of the Service or your top-ups, except those we are required by law to bear. We will provide receipts or invoices as required by applicable law.

You may use the Service only for lawful purposes and in accordance with these Terms and the documentation. If you breach this Section, we may suspend or terminate your Account or API keys under Section 24 and take back Free Credits obtained in breach of it under Section 7.

You must not:

If you find a security vulnerability in the Service, tell us through the contact email and do not disclose it publicly until we have fixed it. If you act in good faith, verify the issue only to the minimum extent necessary, do not access or modify others' data or degrade the Service, and report promptly, we will not pursue action against you under Section 13 for that research.

As long as the activity itself is lawful and stays within your limits and Credits, the following uses are allowed:

You represent and warrant that neither you, nor any organization you represent, nor its owners or controllers, is a target of applicable sanctions laws, or is located in, or ordinarily resident in, a country or region subject to comprehensive sanctions or embargoes; and that you will not use the Service for or on behalf of a sanctioned person, to evade sanctions, or in breach of applicable export control laws.

To comply with law, we may screen payment sources and transactions relayed through the Service, decline top-ups or refuse to relay transactions, and suspend or terminate Accounts. We have no obligation to screen every request. Funds that must be frozen or restricted by law are handled as the law requires, and Section 11 does not apply to them.

Data returned by the Service comes from third-party blockchain networks and their nodes and is processed and computed by us. Data may be inaccurate, incomplete, delayed or interrupted, and we do not guarantee that it is accurate, complete or timely. Where a network supports it, you can query, through the Data API, how far each dataset lags behind the latest block.

Blockchains can reorganize, so data already returned may later change or become invalid. The finality threshold we apply to indexed data is our own protection against reorganizations and does not represent the network's consensus finality; on layer-2 networks, the relevant blocks may not yet be final on the underlying network they rely on.

Datasets and historical coverage differ by network: data may be available only from a certain block onward, may have gaps, may cover only a recent period, or may be returned only in part, and some datasets are snapshots refreshed periodically. The exact coverage is as stated on the Supported Chains page and in the documentation.

Do not rely on the Service as the sole basis for high-value decisions, settlement or liquidation; independently verify data you use for important purposes.

No data provided through the Service, including trade and price data for decentralized exchanges (DEXs) and data relating to tokens, NFTs and tokenized stocks, is investment, financial, legal or tax advice, or an offer, solicitation or recommendation regarding any asset.

This data is not an official quote or reference price. We are not affiliated with the issuers, exchanges or custodians of the assets concerned, and the data gives you no rights in any underlying asset.

Without our written consent, you may not use price or trade data provided by the Data API as a benchmark or settlement price for any financial instrument or financial contract. This does not restrict on-chain state read through the JSON-RPC API, including prices held in on-chain contracts.

When you submit a signed transaction through the Service, we relay it to network nodes as is. We do not modify or sign it, and we do not send transactions on your behalf.

We do not guarantee that a transaction will be broadcast or included on-chain, or its timing, ordering or outcome, or that it will be protected from front-running or MEV. You are responsible for the content, legality, fee settings and consequences of your transactions; once on-chain, a transaction is public and irreversible.

If a request times out or fails, the transaction may already have reached the network and the call may already have been billed. Check the transaction's status first, and do not blindly resubmit requests that change on-chain state. We may refuse to relay particular transactions to comply with law or to prevent abuse.

Supported Networks are developed and operated by third parties and are outside our control. Networks may fork, stop producing blocks, roll back, upgrade or change their rules, and may suffer congestion or security incidents. We are not responsible for resulting service interruptions, data changes or losses, unless applicable law provides otherwise. If a network undergoes a contested fork, we may decide which chain to support, or pause services related to that network.

The Service relies on infrastructure and services provided by third parties, such as hosting, network acceleration and security protection, as well as sign-in through GitHub and Google. Your use of those third-party services is also subject to their terms. When you reach the Service through third-party network infrastructure, you may see error pages that the Service did not generate.

We may add, change or discontinue features, methods, datasets and Supported Networks. Where reasonably practicable, we will describe incompatible changes to the JSON-RPC API or Data API interfaces in the documentation in advance; this paragraph sets no fixed minimum notice period. Changes required immediately for security or legal reasons may be described after they are made.

Before we remove a Supported Network, or discontinue the JSON-RPC API or the Data API as a whole, we will give at least 30 days' notice where reasonably practicable, unless immediate removal is required for security or legal reasons or because the network itself has stopped operating. Credits already added remain usable on other networks and products; if, because a network or dataset is removed, you can no longer reasonably use the Service, you may request a refund under Section 11.

Networks, features or datasets marked Beta on the Supported Chains page or in the documentation may be incomplete or unstable and may change or be withdrawn at any time; the notice period above does not apply to them. Unless stated otherwise, Beta features are billed at their published CU weights.

We make no availability or service-level commitment (SLA), and we do not guarantee that the Service will be uninterrupted or error-free.

The Status page shows the operating status of each Supported Network for information only; it is not a commitment. When we determine that a network is temporarily unavailable, JSON-RPC calls to that network are generally rejected, and rejected calls are not billed (see the documentation).

We may suspend some or all of the Service for maintenance, upgrades, security or legal reasons. Where reasonably practicable, we will announce planned maintenance in advance.

We provide technical support through the contact email and will reply as soon as we can, but we do not commit to any response time or support level.

We or our licensors own all intellectual property rights in the Service, its software, documentation, website content, trademarks and logos. As long as you comply with these Terms, we grant you a limited, non-exclusive, non-transferable, non-sublicensable and revocable license to access and use the Service.

Raw blockchain data is owned neither by us nor by you. Subject to these Terms (including Section 13), you may freely use and redistribute on-chain data obtained through the JSON-RPC API. You may use, process and display data returned by the Data API in your own products and services, including for commercial purposes, and may provide it to your users as part of them; but without our written consent you may not compile Data API data, as is or substantially as is, as the whole or main content of a standalone dataset, database or data service that you sell, rent, license or otherwise redistribute to third parties.

You may send us comments and suggestions. You agree that we may use such feedback free of charge and without restriction, with no obligation to you. Except to state accurately that you use the Service, you may not use our name, trademarks or logos without our written consent.

We handle your personal information in accordance with our Privacy Policy.

Please note: transactions you submit to blockchain networks through the Service are public and cannot be deleted, and wallet addresses are publicly visible on-chain. If more than one sign-in identity (for example, a wallet and a GitHub or Google account) is linked to your Account, we will know that these identities belong to the same Account.

You may stop using the Service at any time. You may ask to close your Account through the contact email (or in any other way the Console or the documentation describes); after verification we will disable your sign-in and API keys.

When we suspend or terminate your Account or API keys, we will tell you why where reasonably practicable and permitted by law, and you may appeal through the contact email; in urgent cases we may act immediately. We may also terminate your Account while you are not in breach, either on at least 30 days' notice (sent to the email address you have used to contact us, for example when requesting a top-up, or otherwise announced as described in Section 30) or immediately; in either case we will refund unused Paid Credits under Section 11.

We may suspend or terminate your Account or API keys if:

While your Account is suspended, we may prevent you from signing in to the Console, end existing sign-in sessions, disable your API keys and pause free top-ups.

When your Account is terminated or closed: your API keys stop working; Free Credits lapse; unused Paid Credits are refunded only in the cases set out in Section 11; and any negative amount on a paid Account remains payable. We keep billing, top-up and other records as described in our Privacy Policy and as required by law, and we do not promise to delete all data immediately.

Provisions that by their nature survive termination, such as payment obligations, disclaimers, limitation of liability, indemnity, governing law and dispute resolution, continue to apply after termination.

To the maximum extent permitted by applicable law, the Service (including the free plan and Beta features) is provided "as is" and "as available". We make no express or implied warranties, including warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy of data, or that the Service will be uninterrupted or error-free.

Nothing in these Terms excludes or limits any liability that cannot be excluded or limited under applicable law, or affects your statutory rights as a consumer.

The limits in this Section do not apply to: (a) property damage caused by our intentional misconduct or gross negligence; (b) liability for death or personal injury; (c) liability for fraud or fraudulent misrepresentation; or (d) any other liability that cannot be limited under applicable law.

Subject to the above, to the maximum extent permitted by applicable law:

To the extent permitted by applicable law, you will indemnify us against losses and reasonable costs (including reasonable legal fees) arising from any third-party claim against us caused by your breach of these Terms or applicable law, or by your infringement of third-party rights. We will notify you promptly and allow you to take part in the defense.

We may change these Terms from time to time. We will post the revised Terms on this page, update the "Last updated" date and, where reasonably practicable, summarize the main changes.

Material changes that are adverse to you take effect 30 days after they are announced; other changes, and changes required immediately to comply with law or to protect the Service from attack or abuse, take effect when posted. If you keep using the Service after a change takes effect, you accept the revised Terms; however, for a change that is adverse to you, you may still, before it takes effect or within 30 days after it takes effect, tell us that you do not accept it, stop using the Service and request a refund of unused Paid Credits under Section 11.

Changes to the dispute resolution provisions do not apply to disputes that arose before the change took effect.

Signing in to the Service does not require an email address, so we generally give notice through our website (including this page and the Pricing page) or the documentation, and a notice is treated as delivered once posted. If you have contacted us by email (for example, to request a top-up), we may also notify you at that address.

For price changes adverse to you (see Section 12) and material changes to these Terms adverse to you (see Section 29), in addition to posting them as described above, we will email each Account that has requested a top-up by email, at the address used for that request.

Send notices to us, including legal notices, to the contact email.

These Terms are governed by the laws of Singapore, without affecting any mandatory protection you have as a consumer under the laws of your habitual residence.

If a dispute arises, both parties will first try to resolve it amicably through the contact email. If it is not resolved within 30 days after either party requests negotiation in writing:

If you have any questions about these Terms, contact us through the Contact page or the contact email ([email protected]).