Skynet
Visit SkynetBlogUse-casesDiscord
  • Getting Started
    • Introduction to Skynet
    • Why Skynet?
    • Features
      • Skynet Intelligence
      • Skynet Orchestration
      • Data Security
      • Memory
      • Skynet Chain
      • Payments
      • AI Tools
    • Skynet Interoperability
  • Agent Studio
    • Studio Overview
    • Dashboard
    • Workflow
  • Skynet Ecosystem
  • Skynet Protocol
    • SkyIDs
    • Role Based Access Control (RBAC)
    • Organizational Services
    • Add AI Agent tools
    • Payment Rails
      • Fiat/Crypto On-ramp
      • Settlement With Tooling Providers
      • Subscriptions vs on-demand Pay-per-second
      • How AI Agents Spend
    • Subnet
      • Types of Subnet
      • Subnet fault-tolerance and security
      • Provider Subnet
      • Provider Subnet functions
      • Tool fees
    • Smart Access Points
  • FAQ
  • Tutorials
  • Concepts
    • Glossary
  • Technical Support
  • Build your Project on Skynet
    • Interact with AI service to create an Agent
      • Prerequisites
      • SDK Initialization
      • Adding Balance to a Subnet
        • Best Practices
        • Common Errors and Solutions
      • Authentication
      • userAuthPayload
      • Service Endpoints
    • Integrate AI agent tools
      • Installation
      • Configuration
      • Initialization and Setup
      • Core Functions
      • Endpoint Summary
  • Developer Portal
Powered by GitBook
On this page
  1. Skynet Protocol
  2. Subnet

Types of Subnet

The Skynet protocol includes various subnet types tailored to specific tool requirements:

  • Public Subnet: These subnets are accessible to the public and cater to AI applications or agents that do not require high-security measures or authorization before use. Users or enterprises utilizing this subnet do not need permission; it is permissionless.

  • Private Subnet: Reserved and restricted, private subnets provide the tools for AI applications or agents requiring heightened security and privacy. Only whitelisted enterprises or entities can access these private subnets, and the enterprise or entity is responsible for configuring automated failover between different private subnets.

  • Sovereign Subnet: Sovereign subnets are inaccessible to any parties other than the entity that established them, as they are dedicated solely to using the creating entity.

PreviousSubnetNextSubnet fault-tolerance and security

Last updated 26 days ago