List Services
Internal Services
danube services list includes the services your organizations registered for their members, next to the public catalog, whenever the key you are using belongs to a member. They carry "visibility": "internal" or "visibility": "local_only" (run through the organization’s data-plane agent) in danube services info <service> and in --json output; catalog services are public. Only members of the organization see them, and a member the organization’s policies do not grant a tool does not see that tool in danube services tools or danube search either. Register one on the dashboard or through the organization endpoint: Onboard an internal tool.
Naming a Service
Every command that takes a<service> (connect, credentials store, services info, services tools, tools list) accepts the service id, its slug (stripe, google-sheets) or its exact name ("Google Sheets").
Resolution is exact, never fuzzy. The slug is looked up first; failing that, the name is compared to the public catalog after normalisation (case and punctuation are ignored) and must match exactly one service. Anything else exits 1 with error: not_found, resource: service and a candidates list (name, id, slug), and no credential is read or stored: