CyAI
Role Definitions
| Role | Description |
|---|---|
| Customer | All users of Cysic AI products, including CyOps users and users of the developer API. |
| Provider | Users who supply token services to CyAI. They use their own compute hardware to connect to CyAI, provide token services, and earn income and rewards. |
| Worker | A role subordinate to a Provider. One machine corresponds to one Worker. Providers connect to CyAI using Workers as the smallest unit. |
| Verifier | Uses Immaculate technology to run LDD tests on all Workers, verifying the validity and accuracy of each Worker's service. This role is currently fulfilled by the CyAI official team. |
Provider
Reserve
- The minimum reserve is 500 CYS.
- With 500 CYS reserved, a Provider may connect up to 5 Workers.
- Beyond 5 Workers, each additional Worker requires an extra 100 CYS reserve.
- Only Providers who have reserved may connect to CyAI.
- Reserve requirements may be adjusted dynamically by the official team in the future.
UnReserve
Before unreserving, the current reserve must satisfy the requirements for the number of currently online Workers. If it does not, the Provider must take Workers offline until the remaining reserve meets the requirement for the desired unreserve amount.
Prerequisites for Connecting to CyAI
- Reserve has been completed and meets the requirements.
- An API key has been created in the platform console.
- A networked computer capable of running large language models is available.
- The model has been downloaded on the machine, and an OpenAI-compatible API service has been started via an inference engine (e.g. vLLM, SGLang). If you are unfamiliar with downloading models or installing inference engines, you can use the inferbench tool for automatic download and installation.
Worker
- Each Worker runs on one machine and serves only one model.
- A Worker can provide token services externally and earn rewards only when its status is online and its verify status is verified.
Customer
Enabling CyAI
Customers can enable or disable the CyAI feature on the profile page.
| Setting | Behavior |
|---|---|
| CyAI enabled | The platform includes CyAI Provider resources in the selection pool, and together with official model resources and Cysic resources, selects the best-priced resource for the Customer. The Customer also receives platform rewards. |
| CyAI disabled | The platform does not include CyAI Provider resources in the selection pool, and the Customer does not receive rewards. |
Price Acceptance
After enabling CyAI, users can set an acceptable price for models.
When none of the platform resources (including CyAI, Cysic, official model providers, etc.) meet the user's price requirements:
| CyAI Price Auto Match | Behavior |
|---|---|
| On | The user accepts the platform's best available price. The platform selects the optimally priced resource and returns the result. |
| Off | The user rejects the platform's best available price. The platform terminates the session and returns a 503 error. |
Verifier
Verification Flow
- When a Worker first connects, its verify status defaults to unverified. It must pass an LDD test to become verified.
- The Verifier periodically runs LDD tests and validation on all online Workers of all Providers.
LDD Test and Verification Rules
| Condition | Result |
|---|---|
| Passes the test once | Marked as verified |
| Fails the test 3 times in a row | Marked as unverified |
Ban
When a Worker is repeatedly marked as unverified, it is set to ban status. Banned Workers are disconnected from CyAI. The Provider must manually delete the Worker from the console, verify that the local model is running correctly, and then manually restart cyai-client.
Any determination of failed verification results in a penalty.
Cases That Directly Set Verify Status to Unverified
| Case | Description |
|---|---|
| a | First connection |
| b | Disconnected (offline for more than 30 minutes) |
| c | LDD fails 3 times in a row |
| d | Banned |
| e | Reserve falls below the minimum requirement |
| f | Worker's model changes |
Workers in unverified status must pass an LDD test again to become verified.
LDD Penalty Rules
Within a 24-hour window, penalties in CYS are applied based on how many times a Worker was set to unverified due to LDD failure:
| Occurrences (N) | Penalty per occurrence | Cumulative |
|---|---|---|
| 1 | 1 CYS | 1 |
| 2 | 3 CYS | 4 |
| 3 | 5 CYS | 10 |
| 4 or more | 10 CYS | \(10 + (N - 3) \times 10\) |
Provider Scoring Rules
Positive factors:
- CYS reserve amount
- Average parameter size of models served by Workers
- Number of tokens served, and other composite factors
Negative factors:
- Offline duration
- Number of LDD test failures
Rewards
Reward Period
Reward amounts are set per period. Each week from Monday through Sunday is one reward period, with a total reward amount configured for that period. The total reward per period may be adjusted dynamically based on operations.
Settlement Period
Each day is one settlement period. Rewards are distributed once per day. The total reward for a given day is 1/7 of the corresponding reward period's total amount.
Provider and Customer reward pools are separate.
Provider Rewards
Rewards consist of two parts: Provider rewards and Worker rewards.
Provider reward factors (higher values increase rewards):
- Provider score
- Total daily income from tokens served by the Provider
- Provider overall cache rate
Worker reward factors:
| Effect | Factors |
|---|---|
| Increase rewards | Worker model parameter size — larger models earn more rewards |
| Decrease rewards | Worker offline duration; number of LDD test failures |
Customer Rewards
The following factors increase rewards:
- Token spending amount for the day
- Total tokens consumed for the day
- Parameter size of the models used