Skip to main content
PulseScanner.io

Terms of Use

Draft — under review

  1. 1. As is.

    The PulseScanner website, data and API ("the Service") are provided "as is" and "as available", without warranty of any kind, express or implied, including any warranty of merchantability, fitness for a particular purpose, accuracy or non-infringement.

  2. 2. Not financial advice.

    Nothing on the Service is financial, investment, legal or tax advice, or a recommendation to buy, sell or hold any asset. Do your own research.

  3. 3. Third-party chain data.

    The data is derived from public blockchain networks and other third-party sources we do not control. It may be delayed, incomplete, reorganised or wrong; unfinalized data can change; prices and valuations are estimates.

  4. 4. No liability for loss.

    To the fullest extent permitted by law, we are not liable for any loss or damage of any kind — direct, indirect, incidental or consequential, including trading losses and lost profits — arising from the use of, or reliance on, the Service or its data, or from its interruption or unavailability.

  5. 5. API use.

    API access is subject to the limits of your plan (call units, request rates, tiers). API keys are personal to the account that created them and may be revoked for abuse. Endpoints may change or be discontinued, with notice where practical.

  6. 6. Service level.

    99% monthly uptime SLA: if the API's availability falls below 99% in a calendar month, the downtime is credited back to your plan at 2×, automatically. The commitment is that the API answers /health from the public edge. Availability for a calendar month is the number of minutes the edge check passes divided by the number of minutes in that month, counted in whole minutes from the first failed check. If availability falls below 99.0% for a calendar month, the credit is 2× the downtime minutes, pro-rated against your plan's monthly fee and applied as plan time; it is capped at one month's fee and is applied automatically. This does not cover:

    • maintenance announced at least 24 hours in advance;
    • faults in Cloudflare or in upstream networks;
    • chain-level events, including halts and reorganisations;
    • requests refused by your own plan's rate limit or quota;
    • events beyond our reasonable control (force majeure).

  7. 7. Changes.

    We may update these terms; continued use of the Service after a change means you accept it.

  8. 8. Contact.

    (To be filled in.)