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. Build your Project on Skynet
  2. Integrate AI agent tools

Configuration

  1. SUBNET_ID: Represents the unique identifier for a specific subnet within a network, enabling targeted network configuration and management.

  2. MONGODB_URL: The connection string required to connect to a MongoDB database, including details like the database cluster location, authentication credentials, and optional connection parameters.

  3. MONGODB_DBNAME: Specifies the name of the MongoDB database to be used, allowing the application to select the appropriate database within a MongoDB instance.

  4. MONGODB_COLLECTION_NAME: Defines the name of the collection within the database where data records are stored, making it clear which specific data group the application interacts with.

  5. JSON_RPC_URL: The endpoint URL for accessing a JSON-RPC service, commonly used in blockchain networks to interact with decentralized applications or perform various RPC calls.

  6. ACCESSPOINT_PRIVATE_KEY: A sensitive private key used for authenticating and signing actions performed by a cluster operator; it should be securely stored to prevent unauthorized access.

  7. ACCESSPOINT_WALLET_ADDRESS: The public wallet address of the cluster operator, typically used in decentralized environments to receive and manage tokens or assets.

  8. PORT: Specifies the port number on which the application server listens, directing incoming requests to the correct application service.

PreviousInstallationNextInitialization and Setup

Last updated 5 months ago