kdeps

Appearance

Resources ​

Resources are the fundamental units of action in an AI agent and serve as the workhorses of Kdeps. Each resource is designed to perform a specific task, making them essential for executing workflows efficiently.

Key Characteristics ​

  • Resources are stored as .pkl files in the resources/ directory. For more information about Apple PKL, visit the Apple PKL Official Website.

  • They enable the AI agent to perform diverse operations, such as running scripts, processing API requests, and interacting with language models. See Kdeps Resource Types

  • Resources can be remixed and reused by other Kdeps AI Agents.

  • They form a dependency graph that determines the execution order of the workflow.

Similar to Workflows, resources have their own configurations. These configurations define the behavior, dependencies, and validation logic for each resource.

Common Resource Configurations ​

  • Metadata:

    • actionID: A unique identifier for the resource.
    • name: A human-readable name for the resource.
    • description: A brief explanation of what the resource does.
    • category: A classification for organizing resources.

  • Dependencies:

    • requires: Specifies the dependencies of the resource. This ensures the resource executes only after its dependencies are satisfied. See Graph Dependency for more information.

Execution Logic ​

The run block defines the execution logic for a resource, including conditional execution, validation checks, and request-level constraints. This section is relevant when APIServerMode is enabled.

Key Fields: ​

  • skipCondition Specifies one or more conditions under which the resource execution should be skipped. If any condition evaluates to true, the resource is bypassed. See Skip Conditions.

  • preflightCheck Performs validation before execution begins. If validation fails, execution is aborted and a custom error is returned. See Preflight Validations.

    • validations: A list of boolean expressions. If any expression evaluates to false, the check fails.
    • error:
      • code: HTTP status code to return (e.g., 404)
      • message: Error message included in the response

  • API Request Validations These validations are enforced only in APIServerMode. If any validation fails, the action is skipped entirely—meaning no further steps such as Exec, Python, Chat, or HTTPClient will run. If any field is left empty, it defaults to allowing all values for that category.

    For more information, please visit API Request Validations.

    • restrictToHTTPMethods: Limits which HTTP methods (e.g., GET, POST) are allowed.

    • restrictToRoutes: Limits which URL paths (e.g., /api/v1/whois) the request must match.

    • allowedHeaders: Specifies which HTTP headers are allowed in the request.

    • allowedParams: Specifies which query parameters are permitted in the request.