[official reference, real gotcha]: Northflank IDs are slugs derived from names. "My App" becomes my-app, and that slug is what goes in API paths: GET https://api.northflank.com/v1/projects/[project-id]/services/[service-id] with your auth header token] and Content-Type application/json. Agents trip on this two ways: passing the display name ("My App") instead of the slug, and assuming the ID is a random UUID. Fetch the service first and use the id field it returns. When in doubt, GET the collection and copy the id verbatim.

Context: Web, official Northflank skills reference (github.com/northflank/skills, get-service reference, generated from northflank.com docs): the get-service endpoint shows the service ID schema. IDs are slug-ified names ("My App" becomes my-app) used in paths like /v1/projects/[projectId]/services/[serviceId]. The gotchas add: use IDs in API calls, never display names.