Documentation Cloud4.ai
HomeCloud ConsoleDiscord Community
  • 🌟Cloud4.ai Documentation
  • Introduction
    • Overview
    • Security
    • 💸Pricing
    • 😀Commission to Model Developers
    • Backlog
    • Enterprise
  • SDK
    • 🚩Quick Start
    • 🔐Authentication
    • ⚙️Configurations & Env Variables
    • ⭐Request
      • Execution Options
      • Execution Schedule
    • 🔗Response
    • 🔶Commands
    • 🟥Errors
  • Concept
    • Organization Structure
    • C4AI Command
    • SIC (Service Identity Code)
    • .cc4
    • 📕Glossary
  • Services
    • General Information
    • 🟨EES (Elastic Endpoint)
      • 🔶EES Commands
      • Use Cases
    • 🟨CSS Credentials Store
      • Best Practices
    • 🟨AAC (AI API Connector)
      • AAC Commands
    • 🟨AIL (AI Lambda)
    • 🟨CES (Chain Execution)
    • 🟨API Schema
    • 🟨KDB (Knowledgebase)
      • KDB Commands
    • 🟨CDB (Context Data Storage)
    • 🟨PL (Prompt Library)
      • PL Commands
    • 🟨PLPrompt (Prompt)
      • Prompt Commands
    • 🟨IDR (Intellectual Data Retrieval)
    • 🟨IDTS (Intellectual Data Transformation Service)
    • 🟨IDOS (Intellectual Data Observation Service)
    • 🟨Files
    • 🟨SJS (Scheduled Job Service )
Powered by GitBook
On this page
  • C4AI Command
  • Life-cycle
  • Example

Was this helpful?

  1. Concept

C4AI Command

PreviousOrganization StructureNextSIC (Service Identity Code)

Last updated 1 year ago

Was this helpful?

C4AI Command

The Cloud4.ai system operates on a Commands framework, where each command specifies the behavior of the service in various scenarios. This approach offers a unified interface for all C4AI Services, ensuring alignment across multiple use cases. Every operation on a service is routed through a command, facilitating a comprehensive trace log of the operational process.

Not all commands are accessible via the API due to security and access control measures. The complete list of commands associated with services can be found below or within each respective Service Section.

Life-cycle

The Command entity represents a simple object that answers the questions: who, when, and what was executed. Due to its simplicity, the lifecycle of the Command entity is straightforward and demonstrates successful or failed command execution.

Example

The following structure represents the nested structure of the command.

❗️Note: The nested structure of the command can be provided using _binding property that is specific for the Execution Commands like C4AI_EES_Execute_Command. Find more: Request

{
  "sic": "sic@0000000001:ees:0000000001",
  "operation": "EXECUTE",
  "command": {
    "sic": "sic@0000000001:aac-instance:0000000001",
    "operation": "EXECUTE",
    "parameters": {
      "system_role": "You're a friendly giraffe!"
    },
    "credentials": {},
    "_bindings": {
      "user_input": {
        "sic": "sic@0000000001:aac-instance:0000000001",
        "operation": "GET_VALUE",
        "parameters": {
          "system_role": "You're a friendly giraffe!",
          "user_role": "You're a friendly giraffe!"
        }
      }
    }
  },
  "schedule": {},
  "options": {
    "priority": "INSTANT"
  }
}

EES Commands
AAC Commands
Prompt Commands
KDB Commands