CLI

npx contentbind init     # scaffold the route, env file and a first component
npx contentbind doctor   # check an integration end to end

doctor

Six checks, in the order things actually break:

1. The key is present and shaped like a key.
2. The API answers.
3. A real delivery call for a real URL returns content.
4. The editor origin registered for the workspace matches where the editor runs.
5. The SDK version in the project is one the API still speaks to.
6. The canvas responds to the editor handshake.

Each failure names the file or setting to change. A blank canvas is nearly always one of the first four, and doctor will say which.