Rivalz hackathon
  • Developer Guides (Short Version)
    • Rivalz AI World Hackathon
      • Hackathon Ideas
    • Developer Overview
    • OCY - AI Data Storage and RAG
      • Rivalz Developer Console
        • How to signup an account
        • How to claim your free credit
        • Dashborad
        • Billing
        • Profile
        • Upload history
      • Access to the Rivalz Storage
      • Knowledge Base
      • Retrieval Augmented Generation (RAG)
      • SDK and APIs
        • PythonSDK
        • NodejsSDK
    • ADCS - AI/Data Oracle System
      • Data Providers
      • Adaptor Creator
      • Dapp Creator
        • Off-chain Components
          • Adaptor
          • ADCS Nodes
            • Fetcher Node
            • Data Storage
            • Data Providers
        • On-chain Components
          • CoordinatorBase
          • Consumer Contract
          • Oracle Router
          • Oracle
      • Dapp-Example
      • Embed a data provider to AI Agents
      • Self-Agent Deployment
    • Eliza ai16z
    • Project Submission (CLOSED)
Powered by GitBook
On this page
Export as PDF
  1. Developer Guides (Short Version)
  2. ADCS - AI/Data Oracle System
  3. Dapp Creator
  4. Off-chain Components

Adaptor

PreviousOff-chain ComponentsNextADCS Nodes

Last updated 5 months ago

The Adaptor is a critical parameter for off-chain inference that acts as a template, dictating the structure and content of inference requests. Users define the specific parameters for the schema used in off-chain inference as follows:

  • Request Instructions: This contains detailed guidelines about the nature of the request, including various parameters such as variables, consumer contracts, event requests, and required user fees.

  • Reference Data: The data that the inference should reference or utilize, including any necessary context or historical data.

  • Response Format: The expected structure of the inference response, which ensures the output is formatted correctly for subsequent workflows. This could be a boolean, JSON, or Integer format depending on the use case.

Users can define multiple Adaptor, each tailored to specific requirements, with each adaptor being uniquely identified by a randomly generated jobID during the creation process. These jobIDs serve as crucial identifiers in Consumer contracts, ensuring accurate referencing.

Refer to Adaptor Creator to learn more.