Legal
The rules for accounts, API use, credits, subscriptions and billing.
Effective
Version
Contracting party
Contact
Contents
01The contract and who we are02Eligibility and accounts03The service04Keys and account security05Permitted and prohibited use06Third-party and public data07Credits and charging08PAYG purchases09Subscriptions10Top-ups and auto-recharge11Failures, cancellation and refunds12Rate limits and fair use13Prices, VAT and taxes14Jobs, monitors and webhooks15Service changes and versions16Intellectual property17Suspension, closure and deletion18Availability and reliance19Liability20Consumer rights21Changes to these Terms22Law and disputes23Notices and general terms01Monocrawl is a trading name of NTV LTD, a private limited company registered in England and Wales with company number 11364012, whose registered office is Amelia House, Crescent Road, Worthing, West Sussex, England, BN11 1QR. NTV LTD is VAT registered under number GB310799500. In these Terms, “Monocrawl”, “we”, “us” and “our” mean NTV LTD; “you” means the person or organisation using the service.
These Terms, the order information shown at checkout, the Privacy Notice and any written enterprise order form make up the agreement. If an enterprise order form expressly conflicts with these Terms, that order form controls for that conflict.
A “Business Customer” acquires the service wholly or mainly for trade, business, craft or profession. A “Consumer” is an individual acquiring it wholly or mainly outside those purposes. Tell us accurately which applies at checkout.
02You must be at least 18. If you use Monocrawl for an organisation, you confirm that you can bind it. You must provide accurate account and billing information and keep it current.
03Monocrawl supplies a hosted API and related console that request, cache, normalise and return information from third-party providers, official APIs and public online sources. Endpoint documentation identifies the input, response and credit cost.
Production routes under /v1 return a live upstream result, a permitted cached result, or an error. They do not substitute sample-shaped output after an upstream failure. Explicit /sandbox routes may return clearly marked synthetic data and are free.
Catalogue entries that are not connected to a live upstream return ENDPOINT_NOT_AVAILABLE. Free browser tools may use disclosed synthetic examples; those examples are not claims about a person, account or event.
04Keep API keys, recovery codes and login credentials secret. Do not put keys in client-side code, public repositories or support messages. Apply appropriate key limits, rotate a key that may be exposed, and revoke credentials no longer needed.
Notify us through the security category without delay if you suspect compromise. We may revoke a key or session to contain risk. We will never ask for a third-party social-platform password or session cookie.
05Subject to this agreement, you may call the API and incorporate results into your own value-added internal or commercial product. You may not offer Monocrawl itself, its credentials, or substantially unmodified raw responses as a proxy, pass-through, resale or substitute API.
06Results may be supplied by independent upstream services or derived from publicly accessible pages. Public accessibility does not remove privacy, database, copyright, publicity, contractual or platform rights. You decide why and how you use returned data and are responsible for a lawful basis, notices, retention, security and responses to rights requests for your use.
Upstream records can be incomplete, stale, duplicated, removed, inaccurate or context-dependent. Verify important facts at the primary source. Follow the Public Data and Data Sources Notice for provenance and correction, removal or suppression requests.
07Credits are service units, not money, stored value or a transferable financial product. Each endpoint has a price published in the current catalogue and endpoint documentation. A successful request consumes that price. A successful but empty or no-match result is normally chargeable because the upstream request and processing completed; an endpoint-specific exception applies only when its documentation expressly says so.
Failed synchronous requests, rate-limit or fair-use refusals, unavailable catalogue endpoints and sandbox responses consume zero credits. Paid asynchronous jobs reserve or consume credits as documented; a failed, cancelled or reaped paid job receives an idempotent credit refund. A cache hit may have a lower documented price.
Credits from different sources share one wallet. For expiry calculations, usage is attributed to expiring plan credits before non-expiring purchased credits.
08The current paid PAYG packs are Hobby (3,000 credits for £15.00), Standard (22,000 credits for £49.00), Growth (75,000 credits for £149.00), Scale (155,000 credits for £299.00). The checkout page and Stripe confirmation control if a price changes before purchase.
Purchased PAYG credits do not expire while the account remains open. They may not be transferred between accounts or redeemed for cash except as these Terms or mandatory law require.
09New subscriptions are no longer offered. Existing subscriptions retain their agreed billing and credit rules. The legacy plans are Build (£19.00 for 5,000 credits), Ship (£49.00 for 24,000 credits), Scale (£149.00 for 78,000 credits), Max (£299.00 for 160,000 credits). A subscription renews automatically each month using the payment method held by Stripe until cancelled.
Each successful monthly invoice grants the plan allowance. Unused plan credits roll into the next period up to one additional month’s allowance; any excess expires at renewal. Remaining plan credits expire when the subscription ends. Purchased PAYG and top-up credits are not removed merely because a subscription ends.
You may cancel from Billing. Ordinary cancellation takes effect at the current period end and stops renewal; access and plan credits continue until then. A past-due subscription may be restricted or ended. Separate statutory cancellation instructions for Consumers appear below and on the cancellation page.
10An active legacy subscriber may buy top-up credits at the current plan rate from £10, subject to a per-period allowance equal to that plan’s monthly grant (Build: 5,000; Ship: 24,000; Scale: 78,000; Max: 160,000). Top-up credits are purchased, non-expiring credits.
Auto-recharge is optional. If enabled, it charges the saved Stripe payment method for the selected PAYG pack when the configured threshold is crossed, subject to your monthly recharge-count cap. It grants exactly that pack’s credits with no bonus. You can disable it in Billing at any time. A failed charge grants no credits.
11Business Customers
Once credits are granted, PAYG packs, subscriptions and top-ups are generally non-refundable. We will correct a duplicate or incorrect charge, billing error or payment reversal and will comply with mandatory law. Failed API work is handled by zero charging or credit restoration, not ordinarily by a cash refund. We may agree a proportionate remedy for a material service failure.
Consumers
Consumers retain mandatory rights, including rights concerning services performed with reasonable care and skill and applicable distance-contract cancellation rights. At checkout a Consumer expressly requests immediate supply. If cancellation occurs after supply begins, we may deduct an amount proportionate to service supplied where the law permits; the right to cancel digital content can be lost after supply begins only where the legal conditions are met. Faulty or misdescribed supply remains subject to statutory remedies.
Account closure
Voluntary deletion is not a refund request. The deletion screen shows the remaining plan, purchased and promotional balance and requires acknowledgement before those credits are lost. Raise a statutory cancellation, billing error or requested refund before deleting. Promotional and plan credits have no cash value. If we close a compliant paid account for our own convenience, we will provide fair treatment for identifiable unused purchased PAYG/top-up value, normally a pro-rata refund or reasonable time to use it.
12The default per-key limit is 600 requests per minute and 25 concurrent requests. An endpoint, plan or written order may set another limit. We may apply disclosed fair-use ceilings to costly upstream-backed endpoints, together with proportionate anti-abuse controls. Refused requests are free.
Do not distribute work across accounts or keys to evade a limit. We may temporarily reduce traffic to protect customers, upstream quotas, security or service stability and will distinguish that refusal from a successful paid result.
13UK consumer-facing prices are shown VAT-inclusive where applicable. Stripe calculates and itemises tax using the billing information supplied at checkout; the receipt or invoice records the final treatment. A UK VAT number does not by itself make a domestic UK purchase subject to reverse charge.
Cross-border place-of-supply, reverse-charge and local-tax treatment depends on the customer’s status, location and the law applying to the supply. You must provide accurate evidence and remain responsible for taxes you must self-account for. We do not promise a particular tax outcome merely because a tax number is entered.
14Async jobs and monitors continue after the initiating request. You are responsible for lawful targets, schedules and retention. Pause or delete monitors you no longer need. Jobs can partially complete; their status and output disclose failures according to the endpoint contract.
Webhooks are at-least-once deliveries. Verify the signature, reject stale timestamps, deduplicate by delivery ID and return a timely 2xx response. We retry failures and may disable persistently failing endpoints. Currently implemented outbound event types are billing.low_balancebilling.credits_exhaustedbilling.purchase_succeededbilling.auto_recharge.succeededbilling.auto_recharge.failedsubscription.renewedsubscription.endedjob.completedjob.failedmonitor.findingsmonitor.attentionmonitor.digest. A test event proves connectivity but is not a business event.
15Platforms and upstreams change without notice. We may add, change, reprice, suspend or remove endpoints, schemas, providers and features. We aim to announce a materially breaking planned change and provide a reasonable migration period where practicable. Urgent legal, security, abuse or upstream changes may take effect immediately.
/v1 is the current compatibility boundary, not a promise that every field or upstream record is permanent. Endpoint documentation and changelog identify material compatibility details.
16We and our licensors retain rights in the Monocrawl service, software, documentation, branding and original schema/normalisation work. We grant you a limited, non-exclusive, non-transferable right to access the service during the agreement and use outputs in accordance with these Terms.
We do not claim ownership of your code, queries or independently created product. You grant us only the rights needed to process inputs, provide the service, secure it, troubleshoot it and comply with law. Third-party results remain subject to third-party rights.
17We may restrict keys or suspend an account where reasonably needed for security, suspected unlawful or abusive activity, payment failure, material breach, upstream compliance or protection of the service. Where practicable we will explain the reason and allow a remedy. We may terminate for an unremedied material breach after reasonable notice, or immediately for serious illegality, security risk or deliberate evasion.
Self-serve deletion first disables auto-recharge and asks Stripe to cancel any active subscription. If Stripe cancellation cannot be confirmed, deletion stops. Once billing is closed, deletion removes account data, keys, ordinary service history and credits. We retain required financial evidence in pseudonymised form for the applicable statutory period and may retain an open legal, cancellation or support request while it is handled or needed for claims. Deletion is replay-safe but irreversible.
18The self-serve service has no guaranteed service level, uptime, response time, coverage or support time unless a separate written order expressly provides one. Maintenance, incidents, upstream changes, quotas and internet conditions can interrupt it.
We provide a technical data-access service, not legal, financial, employment, credit, medical or identity-verification advice. Outputs can be wrong or stale and must not be treated as authoritative without verification. Nothing in this clause removes duties or remedies that cannot lawfully be excluded.
19Liabilities that are not limited
Nothing excludes or limits liability for death or personal injury caused by negligence, fraud or fraudulent misrepresentation, or any liability that law does not permit us to exclude or limit.
Business Customers
Subject to the paragraph above, neither party is liable to the other for loss of profit, revenue, anticipated savings, goodwill, business opportunity or data, or for indirect or consequential loss. Our aggregate liability arising from the agreement is limited to the greater of (a) the fees you paid us in the six months before the event giving rise to the claim and (b) £250. This allocation reflects a low-cost self-serve service without an SLA; enterprise customers needing another allocation can request a written order and insurance-aligned cap.
Consumers
We are responsible for loss or damage that is a foreseeable result of our breach or failure to use reasonable care and skill. We are not responsible for loss that was not foreseeable, for business losses arising from consumer use, or for loss caused by your breach. Your mandatory statutory rights are unaffected.
20If you are a Consumer, nothing in these Terms excludes rights under the Consumer Rights Act 2015, the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 or other mandatory consumer law. Where these Terms conflict with a mandatory right, the right prevails.
Pre-contract price, credits, billing frequency, renewal and cancellation information is shown before Stripe Checkout. After purchase, Billing provides a downloadable confirmation and Stripe provides the payment receipt or invoice. Use the online cancellation form or any clear statement to exercise an applicable statutory right.
21We may update these Terms for product, legal, security or commercial reasons. We target at least 30 days’ notice before a material change applies to an existing customer. Urgent legal or security changes may apply sooner, with notice as soon as reasonably practicable.
The effective date and version identify the current text. A change does not retrospectively alter a completed one-time purchase. If you do not accept a future material change, stop using the service and cancel renewal before it takes effect.
22English law governs the agreement. For Business Customers, the courts of England and Wales have exclusive jurisdiction. Consumers may have mandatory rights to bring proceedings in another part of the United Kingdom or their home jurisdiction; nothing here removes those rights.
Please first submit a recorded legal or billing request so we can try to resolve the issue. This does not prevent either party seeking urgent injunctive relief or using a statutory complaint or court process.
23Send support, billing, cancellation, privacy, legal and security notices through the recorded contact route. It issues a reference and does not depend on email configuration. Formal postal notices may be sent to the registered office above. We may send account notices to the email on your account or display them in the console.
You may not assign the agreement without our consent. We may assign it as part of a reorganisation or transfer of the service, provided Consumer rights are not reduced. A delay in enforcing a right is not a waiver. If a provision is unenforceable, the remainder continues. These Terms do not create a partnership, agency or third-party enforcement right.
For a statutory cancellation, include the account email, purchase reference, purchase date and a clear statement that you cancel. The model form on the cancellation page is optional; any unambiguous statement is sufficient where the right applies.