Using Multiple Oracles to Provide Greater Reliability

In addition to sending requests to individual oracles, you are also able to use multiple oracles that verify the accuracy of the same result. Using multiple oracles helps gurantee that the results provided to your smart contract are accurate, creating a high degree of assurance that your smart contract is being triggered correctly.

Each oracle supports the same type of request, as indicated by the Tasks column, so you can send the same parameters to multiple oracles to ensure that your contract is not reliant on a single node to execute. See the Receiving Data from Multiple Oracles section for an example.

On this page, we list the available oracles running on each test network and their available Job IDs. You will need a Job ID in order to request data from Chainlink. Be sure to familiarize yourself with creating Chainlinked projects , and our Solidity Reference.

We first show the oracle contracts on each network. It is important to note that you must use the Job ID associated with the correct oracle contract. Meaning, Job IDs associated with the Chainlink Team will only work when sent to the Chainlink Team's oracle address.

The tables on this page will help you understand what the Job ID represents. In the first column, we list the tasks associated with the job. For further reading on what makes up a job in a Chainlink node, take a look at the Job Specifications page. In the middle column, we give the Job ID for each available oracle, listed alphabetically. In the third column, we display the parameters that are required to be given per-request. For further reading on request parameters, see the Request & Receive Data page.

📘 Important Information Each oracle will wait for 3 confirmations before processing a request.

Please contact Chainlink and our node operators to obtain Job IDs before use in mainnet. Use Job IDs in testnet for integration and onboarding purposes.