DAISI - Distributed AI Systems Inc

What are Secure Tools?

Secure tools are marketplace items that execute on the provider's server rather than on your host. Your API keys and credentials are sent directly to the provider and are never stored on Daisinet servers. The ORC only handles tool discovery and purchase management — execution and configuration go directly between your host/Manager and the provider.

Step 1: Purchase

Browse the marketplace and purchase a secure tool like any other item. Secure tools are identified by a shield icon on their listing card. Free, one-time, and subscription pricing all work the same way.

When you purchase a secure tool, the system generates a unique installation identifier and notifies the provider. This identifier is used for all communication with the provider — your Daisinet account ID is never shared.

Step 2: Configure

Go to Marketplace > My Purchases in the DAISI Manager.
Find the secure tool and click the Configure button.
Fill in the required setup fields (API keys, credentials, region, etc.).
For OAuth connections (e.g. Office 365, Google), click the "Connect to [Service]" button instead of entering credentials manually. A popup will open for you to authorize access. Once authorized, you'll see a green "Connected" badge.
Click Save Configuration for any non-OAuth fields. OAuth connections are saved automatically when you authorize.

Privacy: Your credentials are transmitted directly from your browser to the provider's server. They do not pass through the Daisinet ORC. The ORC never stores, logs, or caches your setup data. For OAuth connections, the provider handles all token exchange — Daisinet never sees your OAuth tokens.

Step 3: Use

Once configured, secure tools are loaded on your host at the start of each session. When a new inference session begins, the host requests the list of entitled secure tools from the ORC and creates lightweight proxies for each one. This means newly purchased tools become available on the next session without restarting your host.

During inference, the AI can invoke secure tools just like any other tool. Your host sends the execution request directly to the provider's server — the ORC is not in the execution path, so there's no added latency.

Per-Execution Costs

Some secure tools charge a credit cost per execution. This cost is displayed on the tool's marketplace listing and in the tool metadata available to your host. The cost is deducted from your credit balance each time the tool is invoked during inference.

To check a tool's per-execution cost before use, look at the ExecutionCreditCost field on the tool's marketplace listing or in the tool metadata returned by the ORC when loading session tools. A value of 0 or null means no per-execution charge (beyond any subscription or one-time purchase cost).

Troubleshooting

Issue	Solution
Tool not appearing on host	Start a new inference session. Secure tools are loaded per-session from the ORC. If the tool still does not appear, check that the purchase is active.
"Not entitled" error	Check that your purchase or subscription is active in My Purchases.
"Provider is unreachable" error	The provider's server may be down. Try again later or contact the provider.
"Tool has not been configured" error	Go to My Purchases and click Configure to set up your credentials.
"Unknown installation" error	The provider may not have received the install notification. Try re-purchasing or contact support.
OAuth popup blocked	Your browser is blocking the popup window. Allow popups for the Manager site and click Connect again.
OAuth connection stuck on "Waiting for authorization"	The popup may have closed before completing. Click Connect again to restart the flow. If it persists, check that the provider's OAuth endpoint is reachable.
"Could not check status" for OAuth	The provider's status endpoint is unreachable. The provider may be down. Try again later.
"Session validation failed" error	The provider could not validate your session with the ORC. This usually means the session has expired. Start a new inference session and try again.
"Insufficient credits for tool execution"	The tool charges a per-execution credit cost and your balance is too low. Add credits to your account and try again.