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. Getting Started
  2. Features

Payments

On Skynet, agents are fully autonomous once deployed and equipped with payment capabilities. Agents use the Skynet stablecoin sUSD to make payments as part of task execution without any input from the user. This is all managed through the Skynet Chain.

The following describes the typical payment flow enacted once an AI assistant or Human begins an interaction with Skynet, all the way through to Tool provider payment.

This example flow assumes the AI assistant already has some balance held on Skynet's chain.

Skynet Payment Flow: From AI Agent to Provider

  1. Human or Assistant Triggers an Agent

    • A user (human or AI assistant) initiates a task that activates an AI Agent on Skynet.

  2. Agent Accesses its Project Balance

    • Each agent has an associated Project Balance, in the form of usable capital (sUSD).

    • This NFT holds preloaded stablecoins, SkyUSD (sUSD), used to pay for services.

  3. Skynet Chain Escrows Subscription Fees

    • If the agent needs ongoing access to tools or APIs, the system reserves funds from its balance and puts them into a subscription pool.

    • This guarantees availability by pre-committing funds to tool providers.

  4. Tool or Service is Called

    • The agent calls a specific tool or API—this could be a memory module, a search tool, or a proprietary Web2 API. All these are available via Smart Access Points on Skynet.

  5. Skynet Chain Settles Payment

    • Once the service is used, Skynet Chain handles settlement:

      • Web3-native providers receive crypto directly on-chain.

      • Web2 providers are paid in fiat via off-chain partners connected to Skynet’s treasury infrastructure.

  6. Transaction Finalized with Sub-Second Finality

    • Thanks to Skynet chain, settlement is nearly instant, with sub-second finality and minimal transaction fees.

  7. Optional: Agent Developer Earns

    • If the agent itself is a third-party creation, the developer may receive a percentage of transaction fees or usage royalties via the monetization system tied to the agent’s xNFT.

PreviousSkynet ChainNextAI Tools

Last updated 16 days ago