Data Feed Pricing
Our goal is to provide transparency around the way our pricing works.
To view our specific fees, please visit the documentation page for the respective job, and look for the Request Fee.
On this page:
Fee currency
Oracle request fees are typically denominated in LINK token, which are sent along with each request as payment.
If you prefer paying your fees in a different currency (ie, ETH or fiat), please reach out to us, as this can be arranged in the form an up-front payment in return for a set number of oracle requests.
Fee lifecycle
When you make a request to a Chainlink oracle, you'll send a fee (typically denominated in LINK token) along with your request. The fee amount varies by the specific network and data type, and is set by the node operator.
After retrieving your requested data, the node operator pays for the required gas to write the result onto the blockchain, in the currency of the respective chain's native gas token (ie, ETH).
To ensure you send the appropriate amount of LINK with your request, please ensure that your consumer contract is funded with sufficient LINK token, and that the fee variable within your consumer contract matches the one specified within our documentation for the related job.
How do we calculate our fees?
At LinkWell nodes, we pride ourselves in keeping our fees as low as possible for our clients, while also ensuring a redundant, reliable, and highly-secure oracle infrastructure.
Our per-request pricing is based on the following factors:
- Gas costs on the specified network
- The data type and quantity returned
- Your request volume
- Our own infrastructure costs
- Our existing customer volume
- The pricing of our fellow node operators
While we make every effort to keep our pricing consistent, as market conditions change, we may eventually need to re-evaluate. As such, it's recommended to keep your LINK payment configurable (ie, the fee object within your consumer contract), so that you can easily accommodate any such changes without having to re-deploy your contract. By default, all consumer contract examples present within our documentation provide a setFeeInHundredthsOfLink() function for this purpose.
1. Gas costs on the specified network
Writing your requested data on-chain requires a fulfillment transaction, which requires us (the oracle) to spend gas. Depending on the network you have chosen for your data, these gas costs can vary significantly. To minimize your costs and ensure a more consistent pricing model, we recommend against using the Ethereum mainnet network for your requests.
Gas pricing example:
- Polygon network: A node operator writes a
uint256object to a consumer contract deployed on MATIC mainnet, which costs 63,000 gas units to fulfill. Assuming a MATIC token price of 1 USD, and a network gas price of 150 Gwei, this will cost the node operator 0.01 USD in gas fees. - Ethereum network: A node operator writes a
uint256object to a consumer contract deployed on Ethereum mainnet, which costs 63,000 gas units to fulfill. Assuming an ETH token price of 2,000 USD, and a network gas price of 30 Gwei, this will cost the node operator 3.80 USD in gas fees.
The above example is for illustrative purposes only; in the real world, gas price, gas token price, and Chainlink token prices all fluctuate dramatically, and factor heavily into our pricing model.
2. The data type and quantity returned
While a uint256 object may cost us on the order of 60,000 gas units to fulfill on-chain, writing a bytes[] object may cost us 500,000 gas units or more, depending on the content and length of the elements returned. As such, our job pricing may vary by object type and quantity.
3. Your request volume
Customers willing to commit to a certain number of requests per day will enjoy a discounted price on their respective data feed(s). Our bulk pricing discounts begin at 10 requests / day.
4. Infrastructure costs
In maintaining a triple+ redundant, highly-secure, zero-downtime environment for our customers, we incur heavy infrastructure costs. Fees sent along with your requests go toward offsetting these costs.
You can read more about the associated costs of being a node operator on our FAQ page.
5. Our existing customer volume
As public node operators, we benefit from economies of scale: as our customer load increases, we expect to be able to lower our costs, while also being strategic about expanding our infrastructure.
In this way, we can afford to provide a more reliable oracle data infrastructure than any independent node operator could afford to maintain, resulting in a win-win for everyone!
6. The pricing of our fellow node operators
In order to remain competitive, LinkWell Nodes needs to take into consideration the pricing model of our fellow node operators when establishing our target price point.
Have a question about our pricing?
Please don't hesitate to contact us about your budget constraints. We're always happy to discuss!