Lab: verify the docs against the live API

Every curl command in this course was checked against the live OpenAPI spec before being written down, and the check is short enough to run yourself. This is the method, not a special case of it.

1. 1

   Fetch the real specification. It is public, current, and generated from the same code that serves the API.

   code Copy

   curl -s https://api.1claw.co/openapi.json -o /tmp/spec.json
   python3 -c "import json; print(len(json.load(open('/tmp/spec.json'))['paths']), 'documented paths')"

2. 2

   472 paths, give or take, and that number itself will grow as the API does.

   text Copy

   472 documented paths

3. 3

   Hundreds of paths. Confirm the one lesson two lessons ago actually rests on: creating a secret.

   code Copy

   python3 -c "
   import json
   spec = json.load(open('/tmp/spec.json'))
   path = '/v1/vaults/{vault_id}/secrets/{path}'
   print(path, 'exists:', path in spec['paths'])
   print('methods:', list(spec['paths'][path].keys()))
   "

4. 4

   Confirmed, with the exact methods available on it.

   text Copy

   /v1/vaults/{vault_id}/secrets/{path} exists: True
   methods: ['put', 'get', 'delete']

5. 5

   Now check something this course has not shown you yet, from a track further along.

   code Copy

   python3 -c "
   import json
   spec = json.load(open('/tmp/spec.json'))
   hits = [p for p in spec['paths'] if 'rotate-key' in p]
   print(hits)
   "

6. 6

   Two matches, and the agent one is exactly what the compliance track's endpoint reference names.

   text Copy

   ['/v1/agents/{agent_id}/rotate-key', '/v1/platform/apps/{appId}/rotate-key']

You just independently confirmed a claim from a lesson you have not read yet: an endpoint exists for rotating an agent's API key, at the path the compliance track states it at. That is not a coincidence and it is not something you should take on faith either.

• The spec is generated from the server's actual routes, not written by hand and left to drift. A path documented here is a path that exists, right now, in production.
• This is also how you would catch a course going stale. If a future 1Claw release renamed an endpoint, this exact check would show you a missing path before you wasted an hour debugging a 404.
• The same method scales to anything: a CLI flag, an SDK method, an MCP tool name. Whenever a course, a blog post, or a colleague states a technical fact about a live system, there is usually a primary source you can query directly.