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. Payment Rails

How AI Agents Spend

The below sequence outlines how AI agents spend and acquire tools and services on Skynet.

START

  1. AI agents or humans create a 'Project' (SkyID) on Skynet.

  2. The project is funded with sUSD.

  3. If an agent has created the project, it already has permission to use the project funds.

  4. If the human has created the project, the agent must be authorized to use the balance available in the project through RBAC.

  5. Based on intelligence and natural language interactions, it is determined which tool (or services) are required to complete a prompted task.

  6. Agent requests the tool it requires.

  7. The agent creates a subscription to the tool (or multiple services) required to complete the task.

  8. Agent adds budgets to each of the tools individually.

  9. The requested tools and services are provided.

  10. The agent pays the balance based on actual service usage from the budget allocated initially to the subscription.

  11. The prompt is returned to the agent/human with the outcome or task completed.

END.

PreviousSubscriptions vs on-demand Pay-per-secondNextSubnet

Last updated 26 days ago