Update to Domino Data Lab

{
  "description": "Introduction to calling Domino platform APIs. Covers authentication (API proxy, PAT, service account), which host to use for which API, pagination limits, and common errors. Use before any other Domino API, SDK, app, extension, or governance automation skill.",
  "included_files": [
    {
      "relative_path": "API-SPECS.md",
      "size_in_bytes": 1926
    },
    {
      "relative_path": "ERRORS.md",
      "size_in_bytes": 4385
    },
    {
      "relative_path": "HOSTS.md",
      "size_in_bytes": 7581
    },
    {
      "relative_path": "LIMITS.md",
      "size_in_bytes": 2240
    },
    {
      "relative_path": "SDK-MAP.md",
      "size_in_bytes": 2583
    }
  ],
  "name": "domino-api-intro",
  "skill_md_contents": "---\nname: domino-api-intro\ndescription: Introduction to calling Domino platform APIs. Covers authentication (API proxy, PAT, service account), which host to use for which API, pagination limits, and common errors. Use before any other Domino API, SDK, app, extension, or governance automation skill.\ncompatibility: Domino 6.3 and Domino Cloud. Requires DOMINO_API_HOST; in a run use DOMINO_API_PROXY or the localhost:8899 access-token endpoint, outside a run a Personal Access Token.\n---\n\n# Domino platform API intro\n\nApplies to Domino 6.3 and Domino Cloud.\n\nRead this skill first whenever you automate Domino over HTTP or the Python SDK.\n\n## Authentication\n\nFollow https://docs.domino.ai/cloud/reference/api/domino-api-authentication for every call (API proxy in-run, access token + platform host, PAT, and service account).\n\nLegacy user API keys (`X-Domino-Api-Key`, `DOMINO_USER_API_KEY`) are described as deprecated, never recommended. Product migration docs: https://docs.domino.ai/cloud/reference/api/domino-api-authentication#authenticate-with-an-api-key-legacy\n\n| Context | Summary (details on the auth page) |\n|---------|-------------------------------------|\n| In-run | Prefer `DOMINO_API_PROXY` with **no** `Authorization` header when set; else Bearer from `http://localhost:8899/access-token` on `DOMINO_USER_HOST` (or `DOMINO_API_HOST`) |\n| Outside a run | Public deployment HTTPS URL + Bearer **PAT** (you) or **service account** (automation) |\n\nHost selection (gateway, governance 404, WebVFS, inference) is separate from auth mode: [HOSTS.md](./HOSTS.md).\n\n## Reference files (this skill)\n\n| File | Use when |\n|------|----------|\n| [HOSTS.md](./HOSTS.md) | Pick base URL (gateway, WebVFS, inference, governance external URL) |\n| [LIMITS.md](./LIMITS.md) | Pagination, caps, deprecated env names |\n| [ERRORS.md](./ERRORS.md) | Retries, 502/timeouts, job status fields, datasource 500 workaround |\n| [SDK-MAP.md](./SDK-MAP.md) | Which plugin skill or doc covers each surface |\n| [API-SPECS.md](./API-SPECS.md) | OpenAPI files and route discovery |\n\n## Next steps\n\nUse domain skills under `skills/` (python-sdk, apps, governance, datasets, and others). They assume the auth and host rules above.\n"
}