dominodatalab/domino-ai-plugin / skills/domino-api-intro
domino-api-intro
VerifiedIntroduction to calling Domino platform APIs. Covers authentication (API proxy, access token, PAT, service account), which base URL to use, pagination, and common errors. Use before any other Domino API, SDK, app, extension, or governance automation skill, and whenever a request needs a Domino base URL or credential.
| File | Kind | Size |
|---|---|---|
| API-SPECS.md | markdown | 3.0 KB |
| ERRORS.md | markdown | 5.7 KB |
| HOSTS.md | markdown | 5.8 KB |
| LIMITS.md | markdown | 2.9 KB |
| SDK-MAP.md | markdown | 4.8 KB |
| SKILL.md | skill md | 7.6 KB |
API-SPECS.md
View on GitHub# OpenAPI specs and route discovery
Check that a route and its body exist in the spec for the target Domino version before
calling it; do not guess routes from memory.
## Published Public API specs
One per supported target.
| Target | OpenAPI JSON | Reference UI |
|--------|--------------|--------------|
| Domino 6.3 | https://docs.domino.ai/api-specs/6.3/public-api.json | https://docs.domino.ai/6.3/reference/api/domino-open-api |
| Domino Cloud | https://docs.domino.ai/api-specs/cloud/public-api.json | https://docs.domino.ai/cloud/reference/api/domino-open-api |
```bash
# List paths in the Cloud spec (swap cloud for 6.3)
curl -s https://docs.domino.ai/api-specs/cloud/public-api.json | jq -r '.paths | keys[]' | grep taxonomy
# Request body for one operation
curl -s https://docs.domino.ai/api-specs/cloud/public-api.json \
| jq '.paths["/api/jobs/v1/jobs"].post.requestBody.content["application/json"].schema'
```
Differences between the two: the Cloud spec adds
`POST /api/jobs/v1/projects/{projectId}/job-defaults`, `/api/environments/v2/environments`,
environment name/description `PUT`s, Model API collaborators/visibility under
`/api/modelServing/beta`, app roles, and repository default-ref/readme routes. The 6.3 spec
alone has `/api/aigateway/v1/*`.
## A deployment's own reference
Every Domino deployment from 6.3 serves an unauthenticated API reference at
`https://<domino-domain>/docs`, with one OpenAPI document per service:
```bash
curl -s https://<domino-domain>/docs/configuration.json | jq '.sources[] | {title, url}'
```
| Document | Contents |
|----------|----------|
| `/docs/openapi/openapi-public.json` | That deployment's full Public API |
| `/docs/openapi/openapi-internal.json` | The internal API (the `/v4/*` routes; non-public, may change in a future Domino version) |
| `/docs/openapi/data_taxonomy_service-swagger.json` | Tags and properties service |
| `/docs/openapi/data_remotefs_service-swagger.json` | NetApp Volumes service |
| `/docs/openapi/rai_guardrails_service-swagger.json` | Governance service |
`$DOMINO_API_HOST/assets/public-api.json` is only a subset of the Public API and omits
governance, taxonomy, model monitoring, NetApp volumes and dataset-file routes; do not
treat it as complete.
## Internal routes (`/v4/*`)
`/v4/*` routes are the Domino Internal API. They are not in the Public API spec and are
not versioned for external use. Prefer the `/api/...` equivalent; where none exists,
label the call **non-public route; may change in a future Domino version** at the point of use ([route types](./SKILL.md#route-types)).
## Product docs
- https://docs.domino.ai/llms.txt indexes every page; any page is Markdown with `.md`
appended (for example
https://docs.domino.ai/cloud/reference/api/domino-api-authentication.md).
- Service entry pages: [Tags API](https://docs.domino.ai/cloud/reference/api/tags-api),
[NetApp Volumes API](https://docs.domino.ai/cloud/reference/api/domino-volumes-api),
[Governance API](https://docs.domino.ai/cloud/reference/api/governance-api).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |