Terms of Service

1. The service and who provides it

Weather Data Market is operated by Wellbian Labs Pte. Ltd. (WELLBIAN LABS PTE. LTD., 웰비안랩스). Wellbian Labs is the operator and seller of the service, the party that contracts with you under these terms, and the holder of the rights in this site and its content. The weather data is supplied to Wellbian Labs under licence by KWeather Co., Ltd. (케이웨더 주식회사), a Korean meteorological company operating since 1 July 1997.

Wellbian Labs Pte. Ltd. - a Singapore private company limited by shares · UEN 202604584N · incorporated 29 January 2026 · Registered office: 111 Somerset Road #06-01W, Singapore 238164 · Principal activity: software and application development · Director: Kim Sunghwan (CEO) · admin@wellbianlabs.io.

KWeather Co., Ltd. is the data-supply partner. It supplies weather data to Wellbian Labs under licence and is not a party to your purchase contract. Wellbian Labs is not a subsidiary of KWeather: KWeather holds no shares in it.

The two companies are nonetheless related parties under common control. Kim Dong-sik is Representative Director of KWeather Co., Ltd. (the data supplier) and the majority shareholder of Wellbian Labs Pte. Ltd. (the operator and contracting party). That relationship is stated here rather than left out: both registries are public, and a service whose premise is that you should not have to trust its operator has no business leaving a discoverable ownership link unmentioned.

The service is currently in public beta. Purchases are real: payments settle in native XRP on the XRP Ledger mainnet. Every collection run's snapshot hash is anchored on Flare mainnet in the SnapshotAnchor contract, and a second Flare contract publishes resolved verdicts for settlement contracts to read. Payments in USDT on BNB Smart Chain were accepted until 23 September 2026; purchases made that way remain downloadable, and the first-generation anchors written there remain verifiable, but no new transactions are made on that chain. The Flare Confidential Compute path and the FLR-priced market remain on a testnet and are not used for real transactions. Which rails are accepted, and which network each contract is on, is listed on the Technical Proof page.

One product is sold: a per-city subscription to the consensus oracle, giving live values, forecasts and the cross-check determination for its term. Values are produced by a multi-source consensus pipeline (median + MAD outlier rejection) and anchored on a public ledger as SHA-256 snapshots. For occasional use there is per-call metering, described in section 5. The standalone dataset product, air quality and the separate oracle verification feed were withdrawn from sale; these terms continue to govern purchases of them made before withdrawal.

From 26 October 2026 the contracting party for new purchases is Wellbian Labs Pte. Ltd. Purchases paid before that date were contracted with KWeather Co., Ltd. under the terms in effect at the time of payment (section 13: each purchase is governed by the terms in force at payment). Wellbian Labs, as operator, handles delivery, re-download and refund requests for those purchases at admin@wellbianlabs.io.

2. Contract formation - payment is the contract

A quote (quoteId) is valid for 10 minutes. Executing the on-chain payment (purchase / purchaseBundle) that references the quoteId hash constitutes acceptance of these terms and forms the contract. The transaction hash is the contract record; no signature or paper document exists or is required.

Prices are 25 USD for 30 days and 200 USD for 365 days, multiplied by the number of cities. Other lengths are not sold - a quote for any length other than 30 or 365 days is rejected before payment. The XRP Ledger has no settlement contract able to recompute the price, so the quote converts the USD price to XRP at the FTSOv2 XRP/USD rate published on Flare at the moment it is issued and fixes that amount in drops for the quote's validity; the amount actually delivered is verified by us against the ledger and is bound to the quote by a destination tag issued with it. A payment that arrives without that tag, in an issued currency rather than native XRP, or short of the quoted drops is not accepted. The quoted XRP amount is fixed for the quote's validity; the exchange rate used is recorded with the quote.

3. Forward contracts (future periods)

Periods may extend up to 365 days from the purchase date. Days that lie in the future are delivered as empty rows at claim time and fill in automatically as observations, verdicts and anchors accumulate - re-download from the same purchase URL at any time at no extra cost.

The provider does not guarantee that every future day will contain observations for every source; the consensus pipeline records what the sources report.

4. Subscriptions

A subscription is sold in exact 30-day or 365-day terms starting on or after the purchase date, per city. Other lengths are not sold. Access ends automatically when the term ends.

Access is by revocable token, not by purchase ID. The claim response returns an `accessToken` beginning `wdm_sub_` once, and only its SHA-256 is stored; send it as `Authorization: Bearer`. The purchase ID identifies the order and is not a credential - it travels through logs, referrers and shared links, so it grants nothing on its own. A lost token is replaced by minting a new one with a signature from the paying wallet, or from the account that bought it; existing tokens can be revoked at any time.

One token opens every city that the paying wallet currently subscribes to. Buying another city adds it to the same token from that day, with no new credential. A token stops working when every subscription on that wallet has ended.

Data already received during the term may be kept and used after it ends, under section 7. What ends with the term is access to new data.

4-a. Determination reports

A determination is a verdict on a condition you open - a city, a metric (temperature, humidity, wind or precipitation), a comparison and a threshold, and a target hour in UTC. After the target hour has passed, the next hourly run produces one of three outcomes: met, not met, or withheld. Each outcome comes with a report stating the consensus value at that hour, the condition, how many independent observations supported the consensus and how many disagreed, how many sources contributed and how many were excluded, and the reason in plain language.

'Withheld' is a result, not a failure: it is returned when the consensus for that hour was not corroborated well enough to settle on, when too few sources contributed, or when no run exists for that hour. A withheld determination is not a decision for either side of any contract that references it. It is not refunded, because the work of determining was done; what it tells you is that the hour cannot bear a settlement.

A determination is included with a subscription covering the city, and is otherwise paid from metered credits at the price shown in the 402 response at the moment of opening. A determination opened by an autonomous agent binds its operator under section 5. Determinations are final: the same condition and hour reads the same anchored run and returns the same outcome. The report explains the outcome; it does not disclose the rule (section 7-b).

5. Per-call metering (AI agents)

Call credits are prepaid by sending native XRP to the payment account with destination tag 402. The XRP delivered is converted to USD at the FTSOv2 XRP/USD rate published on Flare at the moment we verify the payment, and credits are issued at 0.04 USD per call (minimum 4 USD). The rate used is recorded with the top-up. Credits are bound to the sending account, are non-transferable, and do not expire. A transaction hash can be credited exactly once.

An order placed by an autonomous agent binds the person or company that controls the wallet or the API key it used, exactly as if they had placed it themselves. This service does not, and cannot, check whether an agent was authorised by its operator - it sees a wallet signature or a key. Set the budget and the scope on your side, before the agent runs. Whoever holds a key is responsible for what is bought with it, including purchases made by a sub-agent it delegated to.

Because the service cannot tell an authorised agent from a compromised one, it does not treat an agent misfire as a service fault. A duplicate purchase caused by the same order being submitted twice is refunded under section 9 - the transaction hash makes that verifiable. Repeat purchases the agent genuinely intended, or spending beyond a budget it was not given, are not: the remedy there is to revoke the key, which you can do at any time from the account page, and which takes effect immediately.

6. Data integrity & verification

Every dataset is canonically serialized and hashed (SHA-256); the hash is returned at claim time and reproduces on re-download for immutable (fully past) periods. Index snapshots are anchored on Flare mainnet in the SnapshotAnchor contract, one transaction per run that is never overwritten; snapshots from before 23 September 2026 additionally carry legacy anchors - an IndexAnchored event on BNB Smart Chain and the memo of a 1-drop payment on the XRP Ledger. The same SHA-256 is recorded on each, so verifying any one is sufficient. The ledgers in use, the accounts and contracts involved and the verification procedures are published on the Technical Proof page.

7. Licence to use the data

Purchase grants a non-exclusive, worldwide, non-transferable licence to use the delivered data in your own products, services and analyses, including commercially and including display to your own end users. No separate agreement is issued; this section is the licence.

Attribution is required wherever values obtained here are shown. Display "Powered by Weather Data Market" as a link to weathermarket.io. Every data response carries an `attribution` object with the exact text, the link and ready-to-paste markup, and lists any upstream source whose own licence requires separate credit - preserve those too.

You may show the data to your users inside your product. You may not offer it to third parties as a data feed, API, dataset or bulk download, whether free or paid. Serving the data to your own front end through your own backend is not redistribution; exposing it to your customers as a data service is.

Reselling the data substantially as delivered under another brand is prohibited, with or without attribution.

Analyses, indexes, forecasts and other works derived from the data are yours to use and publish, provided the result is not a substitute for the raw feed.

Data already delivered may be kept and used indefinitely, including after a subscription term ends. What ends with the term is access to new data - not the right to use what you already received.

Storing the delivered data in your own database, cache, or a vector store for retrieval, and putting it in front of a model at inference time, is ordinary use and is permitted - an AI agent reading values to answer a question is the use this service was built for. Training or fine-tuning a model on the data is a different act, because the resulting weights can reproduce the feed without ever calling it again, and that is redistribution by another route. It is not granted by this section: ask, and it will be quoted separately. Publishing a model whose purpose is to emit values substantially equivalent to this feed is prohibited regardless of where its training data came from.

7-a. Free and public responses

The free tier is the present. For any city you name, the current consensus value and the next 3 days of forecast are served without payment, through the API, the MCP tools and the public pages alike. You may show those current values in your own product, with the attribution in section 7.

Everything accumulated is a paid product: the consensus history, every source's raw reading, the 5-minute observations, the canonical snapshot bytes, the full 16-day forecast, and the cross-check determination (verdict, settlementEligible, settlementReason, the per-metric breakdown and the corroboration counts). A subscription serves all of it for the cities it covers without limit; metered credits serve it for any city at one credit per call, which is the form intended for republishing to your own customers at volume - you are billed in proportion to the calls you make.

Two limits apply to the free tier. Without a city parameter only a 10-city sample is returned, because one request would otherwise carry the whole catalogue. And past 120 requests an hour from one address the free tier answers 429 with a Retry-After until the hour rolls over; past 600 the block lengthens. Paid credentials are never subject to either limit.

You may not accumulate free responses into a history; resell or redistribute the data as a feed, API, dataset or bulk download, free or paid; present free values as settlement-grade or as carrying a determination they do not carry; or obtain accumulated data or the determination by any means other than a subscription or metered credits, including by inference from repeated free calls. Circumventing the sample limit or the hourly budget is a breach of these terms whether or not a technical measure prevented it.

The provider may change what is free, and by how much, at any time. Nothing in this section grants a licence beyond what it states.

7-b. Proprietary method

The consensus rule and the determination rule - the estimator, its parameters, the tolerances applied to each metric, the weighting and classification of sources, the corroboration thresholds and the freshness rules - are trade secrets of the provider and the operator. They are not part of what is sold and are not disclosed in any response, report or document. What is public is that the rule exists, that it does not change between runs without a versioned notice, and that every run's hash is anchored on a public ledger so its output cannot be altered afterwards.

You may not reverse-engineer, reconstruct or approximate the rule from responses, reports, snapshots or any other output of the service, nor publish or describe an approximation of it as the provider's method. A determination report explains what supported an outcome and what did not; it does not licence the method that produced it.

8. Intended use, and uses that are not permitted

This service exists to support decisions that have always been made on weather data: parametric climate insurance, crop and energy hedging, prediction-market and oracle-based settlement, agricultural and logistics planning, disaster preparedness, research, and operational risk management. The on-chain elements exist so that the number underlying such a decision can be checked afterwards by every party to it. Using the verdict oracle as the determination reference of a prediction market is an intended use of this service, not an excluded one.

The data must not be used to operate an activity that requires a licence, permit or registration under the gambling laws of the Republic of Korea - including the Act on Special Cases concerning Regulation and Punishment of Speculative Acts, the National Sports Promotion Act and the Tourism Promotion Act - by a party that does not hold that authorisation, and must not be supplied to or embedded in such an unlicensed activity. Whether a given prediction market or settlement platform falls under those laws depends on how and where it operates; that assessment, and compliance with it, is the operator's responsibility under the paragraph below, not a judgement this service makes for them.

Users are responsible for ensuring their use is lawful in every jurisdiction in which they and their users are located. Purchasing constitutes a representation that the intended use complies with this section.

Where the provider becomes aware of use that breaches this section, access may be suspended or terminated immediately and without refund, and the provider may decline further sales to that buyer. This is a condition of the licence in section 7, not merely a request.

9. Withdrawal and refunds

A blockchain transaction cannot be reversed. That is a fact about the payment rail, not a limit on your rights: where a refund is due, it is paid by a separate transfer to the paying wallet or account in the currency received, or in fiat currency where that is not possible.

Consumers in the Republic of Korea may withdraw from the contract within 7 days under the Act on Consumer Protection in Electronic Commerce. For digital content, that right does not extend to content whose supply has already begun with your express consent - but this product is divisible by day, so withdrawal applies to the days not yet supplied, refunded pro rata. Days already delivered are deducted.

A full refund of the affected portion is made, without reference to the period above, where: data ordered was not delivered; the cities, period or product delivered differ from the order; a service fault prevented claim or download; the same order was paid for twice; or an amount was charged in error. Report it to Wellbian Labs at admin@wellbianlabs.io with the transaction hash.

Refunds due are paid within 3 business days of the withdrawal or of agreement on the fault, as the Act requires. Network fees already spent on the blockchain are not recoverable by either party and are not refunded.

Nothing in this section limits a right that Korean consumer law does not permit to be limited.

10. What is warranted, and what is not

What is warranted is the process, not the weather. The sources are named, the consensus rule is published, every collection run is hashed and anchored on a public ledger, the number of contributing sources ships with each row, and the enclave build is reproducible from published code. Those are verifiable claims and we stand behind them: they are what makes the data resistant to silent alteration, by us or by anyone else.

What is not warranted is that any value is correct, complete, timely, or fit for a particular purpose. Weather values are consensus estimates derived from third-party meteorological sources and cross-checked against the observation class (not any single station) inside fixed tolerances that are part of the proprietary rule (section 7-b). The verdict and rain (Y/N, ≥0.1mm) fields are computed by that fixed rule - they are labels produced by an algorithm, not warranties of physical fact. Days built from fewer than three sources are marked low_consensus and should not be relied on as consensus values at all.

The service is provided as-is. To the maximum extent permitted by applicable law, the provider is not liable for any decision, contract outcome, settlement, business interruption, or direct, indirect, incidental, special or consequential loss arising from a weather value being other than the buyer expected, whether or not the provider was advised of the possibility.

That limitation is about the weather, not about our performance. It does not apply to failure to deliver data that was paid for, defects in the service or its contracts, security incidents or breaches of personal data, or a refund owed under section 9 - for those, liability follows the general law and is not capped by this section. Nothing in these terms excludes liability that Korean law does not permit to be excluded, including liability arising from intent or gross negligence, and nothing limits a consumer right that may not be limited.

For any other liability that cannot lawfully be excluded, the aggregate limit is the amount actually paid for the affected purchase. Buyers relying on the data for insurance settlement or hedging at material value should agree an individual service level and liability arrangement with Wellbian Labs rather than rely on these standard terms.

Users are responsible for deciding whether the data is appropriate for their purpose, and for any independent verification their use requires. The verification procedures needed to do that are published on the Technical Proof page.

11. Accounts & wallets

Member accounts (email + password) are optional and only store purchase history; payment always occurs from the buyer's own wallet. You are responsible for securing your wallet keys, API keys and purchase IDs. AI agents may transact without an account.

12. Privacy

Wellbian Labs Pte. Ltd. is the personal information controller. What is collected, why, how long it is kept, where it is stored and how it is administered from Singapore, and how to exercise access, correction and deletion rights are set out in full in the Privacy Policy, published separately from these terms at /privacy. On-chain data is public by nature and is outside the service's control.

13. Changes

Prices and terms may change prospectively; changes never affect already-paid contracts. The version of these terms in force at payment time governs each purchase.

14. Where the service is offered

The data covers cities worldwide. Where the service is sold is a separate question, and this section answers it: the contract is offered from the Republic of Korea, and it is offered to buyers in the Republic of Korea, Singapore, and other jurisdictions in Asia and elsewhere where no local authorisation is required for it.

It is not marketed in, or directed at, the European Economic Area or the United Kingdom during the beta. That is a statement about where we sell, not a technical block: the pages are reachable from anywhere and free values are served to anyone. If you buy from the EEA or the UK, the purchase is valid and the GDPR section of the Privacy Policy applies to you - but no EU representative has been appointed under Art. 27 yet, and consumer notices required by your own country's law may not be present. One will be designated, and named in the Privacy Policy, before the service is marketed there.

Sales are refused where a sanctions regime prohibits them, and to wallets identified as sanctioned. Buyers are responsible for whether receiving and paying for this data is lawful where they are.

This service is in public beta. Buying in small amounts first is advised, and is advised on the purchase page for the same reason.

15. Governing law and jurisdiction

These terms and any dispute arising from them are governed by the laws of the Republic of Korea, without regard to conflict-of-laws rules. The Seoul Central District Court shall be the court of first instance, save where a consumer's mandatory right to sue in another forum applies under Korean law.

If any provision is held unenforceable, it is severed and the remainder continues in force.

16. Contact

One address handles everything - technical, API and operational questions, the contract itself, the licence in section 7, breach of section 8, refunds, disputes, personal-data requests and any formal notice: admin@wellbianlabs.io. It is staffed by Wellbian Labs Pte. Ltd., the operator and the party you contract with.

KWeather Co., Ltd. supplies the weather data under licence and is not a party to this contract; enquiries, refunds and notices about this service go to Wellbian Labs at the address above.

Reports of use that breaches section 8 go to the same address.