Describe one provider authentication profile

Base URLhttps://sinecloud.dev/api/powers/v1

Before your first request

Select your organization, prepare resources in Console, and issue an organization API key with the required product scopes. Current permissions, resource access, budget and available funds are checked on every call.

Choose an available endpoint, then inspect its current revision and input schema. The catalog covers endpoint discovery, organization connections, tool runs and durable run recovery. Managed runs include endpointId, expectedEndpointRevision and input; native runs also select an organization-owned connection and may select an explicit binding. Preserve the native result and status envelope.

Use the Cloud scopes listed in x-sinecloud-scopes on each operation. Native permission names describe runtime capabilities. Connection changes require connectionWrite and an organization-wide key without a project restriction; add BYOK credentials in Console. Reuse the original Idempotency-Key, revision and complete input when recovering an uncertain run. HTTP success alone does not mean execution succeeded.

Organization key authentication and base URL

The production API origin is https://sinecloud.dev; the documentation origin does not serve product requests. The path prefix is /api/powers/v1. Use the complete path documented for the operation, replacing resource IDs, models and endpoint revisions with your actual selections.

Authorization: Bearer $SINECLOUD_API_KEY

Set SINECLOUD_API_KEY to your own environment variable value; never use platform service credentials. Each operation lists required scopes in x-sinecloud-scopes.

This reference is read-only. Run requests in Console or your own client. Browsing documentation never creates a key, starts execution or incurs an execution charge. Keep request IDs and execution receipts; a lost connection does not cancel work. Follow the operation’s recovery instructions before submitting again.