LogoLogo
  • Developers
    • Macrocosmos SDK
      • Get Started
      • API Keys
      • Subnet 1 Apex API
      • Subnet 13 Gravity API
    • Tools
      • Macrocosmos MCP
  • SUBNETS
    • Subnet 1 Apex
      • Subnet 1 Getting Started
      • Subnet 1 Mining Setup Guide
      • Subnet 1 Incentive Mechanism
    • Subnet 9 IOTA
      • Subnet 9 Incentive Mechanism
      • Subnet 9 Mining Setup Guide
      • Subnet 9 Validating
    • Subnet 13 Data Universe
      • Subnet 13 Getting Started
      • Subnet 13 Data Universe API
      • Subnet 13 Incentive Mechanism
    • Subnet 25 Mainframe
      • Subnet 25 Getting Started
      • Subnet 25 Mainframe API
        • API Keys
        • Folding API
          • Running Folding API Server
          • Endpoints
        • Organic API
          • Endpoints
      • Subnet 25 Incentive Mechanism
  • Subnet 37 Finetuning
    • Subnet 37 Getting Started
    • Subnet 37 Mining Setup Guide
    • Subnet 37 Validating Setup Guide
    • Subnet 37 Incentive Mechanism
    • Subnet 37 Competitions
  • CONSTELLATION - USER GUIDES
    • Apex User Guide
      • Navigating Apex
      • FAQs
    • Gravity User Guide
      • Scraping data
      • Managing and Collecting your data
      • FAQs
    • Nebula User Guide
      • Explore Nebula
      • Analyzing data
  • About us
    • About Macrocosmos
    • Bittensor
      • DTAO
    • News and updates
    • Macromedia
    • Subnet Status Update
Powered by GitBook
On this page
  1. SUBNETS
  2. Subnet 25 Mainframe
  3. Subnet 25 Mainframe API

Organic API

PreviousEndpointsNextEndpoints

Last updated 1 month ago

The Organic API provides an interface for submitting real-world protein folding tasks to Mainframe. Unlike synthetic validation tasks that are generated by validators, organic tasks are submitted externally by authorized clients and represent genuine scientific interest in specific protein structures. This document covers the API endpoints, authentication mechanism, architecture, and how organic jobs are processed within the system.

For information about the general Folding API for interacting with the subnet, see Folding API

The API can be deployed in two ways:

  1. Same-process deployment: The API runs within the validator process.

  2. Separate-process deployment: The API runs in a dedicated process, communicating with the validator through a pipe.