Sine Powers is an independent tool catalog and execution interface. Select an organization to begin without creating a project, preparing an instance, or configuring your own provider account. Tool availability, pricing, authorization, and runtime support must still be satisfied separately.
Run your first tool
- Sign in to Console, select an organization, and open Powers.
- Search the Tool catalog, open a tool Endpoint, and read its description, version, input/output contract, and runtime support status.
- Open the Endpoint in the playground. Platform execution is the default.
- Fill required parameters from the tool’s actual schema. Review the input JSON, price, available balance, and optional project attribution.
- Explicitly run the tool, then inspect saved status, results, and financial details in the result view and Call history.
Platform execution does not require a provider key. A catalog entry does not guarantee an available execution route or price. Unsupported tools can remain visible with an explanation.
Supply the correct input
Inputs follow the tool contract, using body, queryParams, and pathParams as needed. Names and structure depend on the Endpoint; there is no universal executable request body. Values in pathParams must be strings. The complete request is limited to 64 KiB.
Tools with object-field schemas can provide an input helper. It fills only defaults explicitly declared by the contract; arrays and objects use JSON. Review the resulting input before execution and edit complex fields directly when necessary.
A project optionally attributes the call and does not create a separate credential catalog. Endpoint IDs may contain # or /. Programmatic clients must encode the entire ID instead of treating part of it as a URL fragment.
Use your own provider account
To use your own provider account and credentials, open Advanced BYOK (bring your own key). It is available to organization owners and admins, subject to connection-write permission.
- Add a direct provider connection supported by the runtime, supplying the account identity and credentials requested by the form.
- After saving, only connection metadata is returned. Plaintext credentials are not returned, and a successful save does not prove that the provider accepts them.
- Return to the tool playground, expand the advanced own-account settings, and explicitly select a compatible organization account.
- Review cost and input, then execute. Return to the default option to use platform execution again.
Organization BYOK does not support self-configured aggregator providers. If an own-account call fails, it does not automatically switch to the paid platform path or another provider. Disabled credentials can be re-enabled; revocation is permanent. Use a new connection identity when changing accounts.
Check the provider bill separately from Cloud platform fees. Selecting your own account does not imply that every fee is zero. Review the displayed execution price and organization Billing.
Recover uncertain calls
ACCEPTED, RUNNING, and UNKNOWN do not mean success. A tool can modify external data, so do not create another request merely to check whether the original succeeded.
- With a Run ID, query that record or use Recover original request.
- Without a Run ID, inspect call history first. If submission recovery is needed, retain the original request identifier, input, Endpoint version, project, and selected own account.
- If input is missing after a refresh, provide exactly the original input. Recovery identifiers do not store tool input, credentials, or result bodies.
Leaving the page does not cancel server execution. Start a new call only when you intend another operation, considering that the earlier task may still be running. Check execution results and financial settlement independently.
Programmatic access and usage
Open API and CLI to generate examples from the selected Endpoint’s actual version and input contract. Default platform examples do not require instance parameters or provider connection identifiers. Create an API key with toolRun to execute, catalogRead to inspect the catalog, and runRead to inspect calls, adding other capabilities only as needed.
Call history shows organization records visible to the current user. Project selection does not partition that history catalog. Use organization Usage for Cloud usage filtered by project. Tool counts, durations, and native measurements remain distinct; missing values are not zero, and the current page’s record count is not total usage.