Skip to main content
Use this quickstart when you have a pre-provisioned credential and need to confirm what it can read. The three requests are read-only. They do not create or change Registry content.
Preview. Run the requests in an approved development environment before relying on them in production automation.

Before you start

  • Obtain a bearer credential through your organization’s access process.
  • Keep it in an approved secret store or ignored local environment file.
  • Set the public Gateway URL and credential in your shell:

Choose your interface

The identity response confirms the caller and whether it has completed onboarding. Workspace and Skill lists return visible results; an empty list is still a successful read.
Use the CLI for local work, CI jobs, and coding agents that need machine-readable output.
auth status identifies the resolved account and credential source without printing the credential. Select a workspace returned by workspace list before a write.

Verify the result

Confirm that the identity is the expected account, then choose a workspace returned by the CLI or SDK response before a write. If the response is an error, use Errors and retries; do not change a workspace ID or retry a write until you understand the result. Next, publish and retrieve a Skill or use the CLI Skill workflow.