Sine Powers / Tools and integrations
One tool catalog for your applications and agents.
Discover search, research and data tools, inspect their input contracts and call them through a consistent API. Use platform execution by default, with optional organization credentials for supported direct providers.
What you can build
Discover a tool by what it does
Search the catalog by tool, original service or category. Read each Endpoint’s version and input/output contract before deciding how it fits your application.
Start with platform execution
Call tools with a configured platform route without first supplying a provider key. Organization owners and admins can optionally manage supported direct-provider BYOK credentials.
Follow a call to its recorded result
Inspect persistent invocation status, output and financial details. Keep the same request identity when recovering an uncertain result instead of submitting another independent call.
Sine Powers
Get started in the Console
Built for your workflow
- Web search and research tools in your application
- Company and contact data workflows
- Server-side integrations built against explicit Endpoint contracts
Find an Endpoint
Open the tool catalog and select a tool. Review the schema, current runtime support and the permissions and price shown for your organization.
Prepare the tool input
Fill the fields required by that Endpoint. Keep the default platform execution option, or explicitly choose an authorized direct-provider account when you need BYOK.
Run and keep the request identity
Submit the call, then inspect its result and billing. Use the saved run ID or original idempotency key to recover a request whose result is not yet confirmed.
Read-only API example
Discover the catalog from your own application.
The public Powers gateway retains its versioned API. This example reads the catalog; selecting a tool and executing it are separate operations.
export SINE_CLOUD_URL="https://sinecloud.dev"
curl "$SINE_CLOUD_URL/api/products/sine-powers/gateway/v1/catalog" \
-H "Authorization: Bearer $SINE_CLOUD_API_KEY"The Cloud API key needs Powers catalogRead permission. An executable Endpoint also needs an available route, toolRun permission, valid input and billing admission.
Set SINE_CLOUD_API_KEY securely in your environment with the required product permissions. Keep it on your server; never expose it in browser code.
Access and billing
Workspace access
The catalog and execution are separate capabilities. A listed tool is not a promise that its route is configured or that every organization can execute it. Review the live availability and schema in the Console.
How usage is charged
Default platform calls use the organization wallet at published prices. BYOK provider charges are separate from Cloud charges. The call result and financial settlement have their own recorded states; an unknown result is not treated as free or successful.
View pricing