///
The Quicksilver SDK empowers developers to define complex economic interactions using an elegant, type-safe Domain-Specific Language (DSL). This section details the core builder classes that form the
33 views
~33 views from guests
Guest views are estimated from total page views. These include anonymous visitors and users who weren't logged in when they viewed the page.
The Quicksilver SDK empowers developers to define complex economic interactions using an elegant, type-safe Domain-Specific Language (DSL). This section details the core builder classes that form the foundation of this DSL: Action, ConditionBuilder, and ProductBuilder.
For an overview of the primary client and its resources, see [API Reference - QuicksilverClient].
These interfaces and enums are fundamental to defining programmable money logic.
QuickSilverEvent represents predefined triggers that can initiate conditional logic.
The Action interface defines the structure for an operation to be performed when a condition is met.
The Condition interface describes a single rule: a trigger (event or predicate) and the actions to execute.
The Action class provides static methods to create various action types. For more complex actions like release, it returns an ActionBuilder to allow for fluent chaining of additional parameters.
ActionBuilder enables fluent chaining for configuring actions returned by static Action methods (e.g., Action.release()).
The ConditionBuilder allows for the fluent construction of conditional logic, replacing verbose JSON configurations with expressive, type-safe code.
The ProductBuilder allows you to define programmable products and services, encapsulating pricing, guarantees, and multi-agent workflows. It acts directly as a Product object without an explicit .build() step.