Chrono AI Service Manual

You are an AI agent reading this manual to learn how to operate the Chrono AI service stack — NyxID + Ornn — as one system. Throughout this document, "you" always refers to the agent itself, not the human user driving you.

>

## What lives in here

>

Two operation halves, sitting on a shared identity bootstrap and a shared failure-mode appendix:

>

1. NyxID (§1) — identity, sessions, services catalogue, organizations, OAuth clients, scopes, proxy. Closest analog: an OIDC IdP fused with a credential-injecting reverse proxy. 2. Ornn (§2) — skill lifecycle. Search, pull, install, execute, build, upload, share, audit, version, analytics, GitHub sync. Closest analog: npm registry + npm CLI fused, model-agnostic.

>

Plus §0 (identity bootstrap), §0.5 (~/.ornn/installed-skills.json registry), §3 (common failures), and §4 (references).

>

Every Ornn API call funnels through NyxID — there is no separate Ornn auth surface. That is why this manual is one document instead of three.

>

## First: install this skill locally

>

Try to install this skill into your runtime's local skills directory:

>

- Claude Code: ~/.claude/skills/chrono-ai-service-manual/ - OpenAI Codex CLI: ~/.codex/skills/chrono-ai-service-manual/ - Cursor: .cursor/rules/chrono-ai-service-manual.md - Other agents: whatever skill-discovery directory your platform uses.

>

If your runtime has no local-skills mechanism, load SKILL.md (and the references/*.md files you need) into your system context and keep them there for the rest of the session.

>

*And in all cases — whether you wrote the skill to disk or only into context — append an entry for it to `~/.ornn/installed-skills.json`.* That file is the persistent registry of every Ornn skill you (or any prior session on this machine) have installed; it's how the next session, or a different agent on the same box, knows what's already loaded and which versions to re-check. Schema + workflow in §0.5 and references/installed-skills-registry.md.

>

## Always load this manual when the user asks you to do anything Chrono AI-related

>

You must have this manual loaded whenever the user asks you to:

>

- Bootstrap a NyxID session — install the CLI, log in, refresh, switch environments — §1.1. - Discover your NyxID identity — orgs, services you own, role memberships, scopes — §1.2 / §1.4 / §1.5. - Manage NyxID services — list, look up, create, edit, attach credentials, rotate, delete (HTTP services + SSH services) — §1.3. - Manage NyxID organizations — list, members, create, invite, edit metadata — §1.4. - Manage NyxID OAuth clients — register (DCR), list, edit, rotate secrets, revoke — §1.6. - Find, pull, and execute an existing Ornn skill — or build a new one and upload when nothing matches — §2.1. - Update a skill's visibility (private / shared / public) — §2.2. - Publish a new version of a skill you own — §2.3. - Trigger an audit or review the audit history for a skill — §2.4 / §2.5. - Pull a non-latest version, compare two versions, or delete / deprecate a version — §2.6 / §2.7 / §2.10. - Check usage analytics for a skill — §2.8. - Bind a skill to a NyxID service (system / personal) — §2.9. - Delete a skill entirely — §2.11. - Find skills (by tag, author, system, shared, etc.) — §2.12. - Pull your Ornn notifications (audit fan-out, etc.) — §2.13. - Link a skill to GitHub or trigger a sync from the linked source — §2.14. - Work with skillsets (curated bundles of skills + required master prompt / instructions for orchestration, one-call closure, kinds including consensus-supported) — §2.15. - Diagnose any failure that involves NyxID, Ornn, the proxy, or token forwarding — §3.

>

Without this manual loaded, you do not know which endpoint to call, how to authenticate, or how to read the response shapes.

§0. Updating this manual

This manual is itself an Ornn skill (name: chrono-ai-service-manual). Its source of truth is the Ornn registry, not a static docs page — pull a fresh copy through the same API every other skill flows through.

Whenever you want to check for an update, follow these steps verbatim:

1. Pull the latest version of this skill from Ornn (CLI form shown; HTTP form is the same call against https://ornn.chrono-ai.fun/api/v1/...):

   nyxid proxy request ornn-api \
     "/api/v1/skills/chrono-ai-service-manual/json" \
     --method GET --output json

1. The response is { data: { name, description, metadata, files: { "SKILL.md": "...", "references/...": "..." } } }. Read the YAML frontmatter at the top of SKILL.md and find the version: field.

1. Compare it to the version: in your loaded copy (the frontmatter at the top of this file). If they match, you are current — stop here.

1. If the published version is newer:

• List every version available by calling GET /api/v1/skills/chrono-ai-service-manual/versions. The response has one row per version, newest first.
• Ask the user which version they want to load (they may want to pin to an older one for reproducibility).
• Once the user picks, fetch with GET /api/v1/skills/chrono-ai-service-manual/json?version=<X.Y> and replace your context with the new SKILL.md (and any references/*.md you consume). The new content's frontmatter overwrites the old.

1. If step 1 returns 404 SKILL_NOT_FOUND, the registry instance you are pointing at has not published this skill yet. Keep operating on the version you have. The Ornn API is backwards-compatible within /api/v1, so older manuals continue to produce valid calls — you will only miss capabilities introduced in newer versions.

If nyxid is unavailable or the proxy is unreachable, keep operating on the version you have. Do not retry-loop the update check; treat it as a once-per-session inquiry the user can re-trigger explicitly.

§0.5 Tracking and re-checking installed Ornn skills

The persistent registry is `~/.ornn/installed-skills.json`. Full schema, when-to-update rules, and the per-execution version-check protocol live in references/installed-skills-registry.md — load it the first time you install or execute any Ornn skill and again whenever you need the contract.

The minimum you need to remember inline:

• Read the file before any Ornn operation. New session = new read.
• Append a record every time you install a skill. Required fields: name, ornnGuid, installedVersion. Optional: installedAt, localPath, isPinned.
• Bump `installedVersion` + `installedAt` every time you upgrade a record's local copy.
• Remove the record when you uninstall.
• Before executing an installed skill, re-check GET /api/v1/skills/<name-or-guid>/versions. If a newer version exists and the record is not isPinned, surface to the user and ask before upgrading.
• `audit.risky_for_consumer` notifications are a hard stop — pull §2.13's notifications poll, surface yellow / red verdicts to the user, ask before continuing.

§0.6 Identity bootstrap — the one and only auth flow

Every API call in this manual — NyxID or Ornn — is authenticated by a NyxID-issued bearer token. There is no separate Ornn login. The agent's job at the very start of a session is to make sure this token exists and works.

You have two transport choices, and one identity choice. Pick before you do anything else.

Transport choice — CLI vs HTTP

The contract is identical; only the wrapping changes. Pick whichever your environment has:

Through the rest of this manual, every command is shown in both forms wherever they meaningfully differ. When they don't differ, the CLI form is shown — references/nyxid-cli-recipes.md carries every CLI subcommand, and references/{nyxid,ornn}-api-reference.md carry the underlying HTTP catalogue.

Base URLs. Production Ornn is https://ornn.chrono-ai.fun/api/v1. Production NyxID is https://nyx-api.chrono-ai.fun (API) + https://nyx.chrono-ai.fun (frontend / OAuth flow). Local hosted NyxID is http://localhost:3001 (API) + http://localhost:3000 (frontend). The CLI persists --base-url after the first nyxid login to ~/.nyxid/base_url and reuses it for every subsequent call.

Identity choice — interactive user vs API key

Two paths — both produce the same bearer token. NyxID does not care which you used.

#### Path A — nyxid login (interactive, one human interaction)

# Pick the right base URL for your environment.
nyxid login --base-url https://nyx-api.chrono-ai.fun     # production
nyxid login --base-url http://localhost:3001             # local self-host

# Headless / AI-agent environments: password mode (ask the user to set $NYXID_PASSWORD first)
nyxid login --base-url <url> --password --password-env NYXID_PASSWORD

Browser-mode nyxid login opens an OAuth page; the user must complete the consent flow in their browser. Once it reports success the access token lives at ~/.nyxid/access_token and the base URL at ~/.nyxid/base_url. Subsequent calls — including nyxid proxy request — auto-attach the token and refresh it on expiry.

#### Path B — NyxID API key (long-lived, headless-friendly)

For AI-agent / CI environments the user creates a NyxID API key once and exports it. Two ways the user can mint it:

• Web UI — http://localhost:3000/keys (or https://nyx.chrono-ai.fun/keys in prod) → "NyxID API Keys" tab → "+ Create API Key". One-time display.
• CLI — nyxid api-key create --name "AI Agent Key" --scopes "read write". Output includes full_key once, then never again.

Then:

export NYXID_API_KEY="nyxid_..."          # the user runs this — never echo or log the value

Use the key as a bearer (or as X-API-Key) in every authenticated HTTPS call. The CLI also honours NYXID_API_KEY when no ~/.nyxid/access_token is present, so Path B works for nyxid proxy request too.

Credential safety rule: never embed a key value in commands the agent emits. Use $NYXID_API_KEY / $TOKEN references, ask the user to set the env var (in Claude Code: ! export NYXID_API_KEY=...), or send them to the dashboard.

Verify the token works

CLI:

nyxid whoami

HTTP (against Ornn — the same identity surface):

curl -H "Authorization: Bearer $TOKEN" \
  "https://ornn.chrono-ai.fun/api/v1/me"

Both return { userId, email, displayName, roles, permissions }. If you get 401 AUTH_MISSING (or 401 invalid_token from raw OAuth), the token is bad or expired — re-run the bootstrap. A 200 body where permissions is empty means the proxy resolved your identity but NyxID's role mapping isn't populating Ornn permissions — see §3.1.

Required Ornn permissions (so you don't waste a round-trip)

The permissions array on /me tells you what your token can do. Cross-check before attempting writes:

Most read operations — browsing public skills, version listings, skill format rules, audit verdicts on visible skills, notifications — need no scalar permission; they're open to any authenticated caller (and some are anonymous). The exact gates per endpoint are in references/ornn-api-reference.md.

Discover the Ornn service through NyxID (CLI mode only)

If you're using the CLI transport, you also want to verify NyxID can route to Ornn:

nyxid proxy discover --output json

The response lists every service the authenticated user can reach through NyxID. Confirm an entry with "slug": "ornn-api" is present. From this point on, every Ornn call uses the slug ornn-api. If the slug is missing, the user's NyxID account doesn't have Ornn connected — tell them to add it through the NyxID UI or via §1.3.

Token model in one paragraph (full detail in references/nyxid-token-model.md)

NyxID issues short-lived (15 min default) access tokens + long-lived refresh tokens via OIDC; API keys are an alternative bearer that doesn't expire. Permissions are baked into the token at issue time — they don't auto-refresh if you change roles mid-session. The proxy validates the bearer, decodes identity, may forward the user's bearer to the upstream service if the per-user forward_access_token flag is on (Ornn's /me/orgs lookup needs this; without it the call fail-softs to []). Scopes (openid profile email etc.) gate the OIDC userinfo endpoint; Ornn's permission model lives at a higher level (ornn:skill:*) and is mapped from NyxID roles. The proxy strips bearer tokens between hops by default — that's a feature, not a bug — but it produces three diagnostics worth knowing (§3.1, §3.2, §3.3). Read references/nyxid-token-model.md if any of that surprised you.

§1. NyxID Operations

NyxID is the identity / proxy / catalogue layer. You drive it whenever the user wants to manage who can access what — services, orgs, OAuth clients — independent of Ornn skills.

Under the hood every NyxID API endpoint is at <NYXID_BASE>/api/v1/.... The CLI hides NYXID_BASE after nyxid login. The full per-endpoint contract is in references/nyxid-api-reference.md. Common CLI subcommands are catalogued in references/nyxid-cli-recipes.md.

1.1 Bootstrap a NyxID session

Already covered in §0.6. Quick reference:

# Install nyxid (one-time, requires Rust toolchain)
cargo install --git https://github.com/ChronoAIProject/NyxID nyxid-cli
nyxid --version                                          # sanity check

# Log in — interactive
nyxid login --base-url <NYXID_API_BASE>

# Log in — headless (set $NYXID_PASSWORD first; user must run, not the agent)
nyxid login --base-url <NYXID_API_BASE> --password --password-env NYXID_PASSWORD

# Verify
nyxid whoami
nyxid status                                              # shows base URL + auth state

# Refresh — usually automatic. Force one with:
nyxid auth refresh

# Log out
nyxid logout

To switch environments, log out, then log in again with a different --base-url. The CLI supports only one active base URL at a time.

1.2 Discover your identity

Three orthogonal calls. Run all three when you're new in a session and don't yet know what you have access to.

# 1. Caller identity
nyxid whoami
# CLI returns: userId, email, displayName, roles, permissions, base URL

# 2. Caller orgs (Ornn proxy returns the same data — they share the NyxID identity layer)
nyxid proxy request ornn-api "/api/v1/me/orgs" --method GET --output json
# Returns { items: [{ userId, role, displayName }, ...] } — admin + member only (viewer filtered out)

# 3. Catalogue services the caller can use
nyxid catalog list                                        # connectable services only
nyxid catalog list --all                                  # everything (system + user-owned)
nyxid catalog show <slug>                                 # full metadata for one service

If nyxid whoami returns a token but permissions: [], see §3.1. If me/orgs returns [] for a user you know is in orgs, see §3.2 (forward_access_token is off).

1.3 NyxID services — list, create, edit, delete

A NyxID service (also called "AI service" in the dashboard) wraps a downstream API: a base URL, an auth method, an injected credential. Three flavours: catalogue services (templates the user picks from), custom services (URL the user provides), and SSH services (cert-auth flavour for remote-exec / tunneling).

#### List your services

# CLI
nyxid service list                                        # human table
nyxid service list --output json                          # machine-readable

# HTTP equivalent
curl -H "Authorization: Bearer $TOKEN" "$NYXID_BASE/api/v1/keys"

The unified /keys endpoint returns one row per UserService — combining UserEndpoint (URL), UserApiKey (encrypted credential), and the proxy slug. New work should not call the legacy /connections endpoint.

#### Show / inspect a service

nyxid service show <slug>
# HTTP: curl -H "Authorization: Bearer $TOKEN" "$NYXID_BASE/api/v1/keys/<id>"

#### Add a service from the catalogue (the 99% case)

# User exports the credential first; the agent never sees it
# (in Claude Code: `! export SERVICE_CREDENTIAL="sk-..."`)

nyxid service add llm-openai --credential "$SERVICE_CREDENTIAL" --label "Production"

# Catalogue service that needs a custom endpoint URL (e.g. self-hosted OpenClaw)
nyxid service add llm-openclaw \
  --credential "$SERVICE_CREDENTIAL" \
  --endpoint-url "http://localhost:18789" \
  --label "Local OpenClaw"

# OAuth-flavoured services
nyxid service add github --oauth                          # opens browser

# HTTP (catalogue add)
curl -X POST "$NYXID_BASE/api/v1/keys" \
  -H "X-API-Key: $NYXID_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"service_slug\": \"llm-openai\", \"credential\": \"$SERVICE_CREDENTIAL\", \"label\": \"Production\"}"

A single call auto-provisions the UserEndpoint + UserApiKey + UserService records. Auth methods supported: bearer, header, query, path, basic, none.

#### Add a fully custom service (no catalogue entry)

nyxid service add-custom \
  --label "Internal API" \
  --endpoint-url "https://internal.corp.com/api" \
  --credential "$SERVICE_CREDENTIAL" \
  --auth-method header --auth-key-name "X-API-Key"

# HTTP
curl -X POST "$NYXID_BASE/api/v1/keys" \
  -H "X-API-Key: $NYXID_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{
    \"label\": \"Internal API\",
    \"endpoint_url\": \"https://internal.corp.com/api\",
    \"credential\": \"$SERVICE_CREDENTIAL\",
    \"auth_method\": \"header\",
    \"auth_key_name\": \"X-API-Key\"
  }"

The slug is derived from the label.

#### Edit a service

nyxid service update <slug> --label "My Custom Name"
nyxid service update <slug> --endpoint-url "http://localhost:8080/openai"
nyxid service update <slug> --node-id "<NODE_UUID>"            # route through a node

# HTTP
curl -X PUT "$NYXID_BASE/api/v1/keys/<id>" \
  -H "X-API-Key: $NYXID_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"label": "...", "endpoint_url": "..."}'

#### Rotate a service's credential

# User exports the new credential, agent never sees it
# (! export NEW_CREDENTIAL="sk-new-...")

curl -X PUT "$NYXID_BASE/api/v1/api-keys/external/<api-key-id>" \
  -H "X-API-Key: $NYXID_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"credential\": \"$NEW_CREDENTIAL\"}"

Rotating the credential preserves the slug — every existing proxy call keeps working.

#### Delete a service

nyxid service remove <slug>
# HTTP: curl -X DELETE -H "X-API-Key: $NYXID_API_KEY" "$NYXID_BASE/api/v1/keys/<id>"

Deactivates both the service and the credential. There is no undelete.

#### SSH services — register and use

# Register (admin-only; --via-node optional for nodes)
nyxid service add-ssh \
  --label "Production Server" --host 10.0.0.5 --port 22 \
  --cert-auth --principals "ubuntu,deploy" --ttl 30 --via-node "$NODE_ID"

# Issue a short-lived user certificate
nyxid ssh issue-cert <SERVICE_ID_OR_SLUG> \
  --public-key-file ~/.ssh/id_ed25519.pub \
  --principal ubuntu \
  --certificate-file ~/.ssh/id_ed25519-cert.pub

# Remote command execution
nyxid ssh exec <SERVICE_ID_OR_SLUG> --principal ubuntu -- uptime

# Interactive terminal
nyxid ssh terminal <SERVICE_ID_OR_SLUG>

# OpenSSH ProxyCommand integration
nyxid ssh proxy <SERVICE_ID_OR_SLUG> \
  --issue-certificate \
  --public-key-file ~/.ssh/id_ed25519.pub \
  --principal ubuntu \
  --certificate-file ~/.ssh/id_ed25519-cert.pub

Full SSH endpoint catalogue: references/nyxid-api-reference.md § "SSH".

1.4 NyxID organizations — list, create, edit, manage members

Every NyxID user can belong to multiple organizations. Orgs are the unit of grant in Ornn share lists (sharedWithOrgs) — you cannot share an Ornn skill with an org you don't know about.

#### List the caller's orgs

# Through the Ornn proxy (returns admin + member roles only — viewer is filtered)
nyxid proxy request ornn-api "/api/v1/me/orgs" --method GET --output json

# HTTP through Ornn
curl -H "Authorization: Bearer $TOKEN" "https://ornn.chrono-ai.fun/api/v1/me/orgs"

If this returns [] for a user you know is in orgs, the per-user forward_access_token flag is off — Ornn cannot call NyxID on the caller's behalf. See §3.2 for the diagnostic + remediation.

#### Resolve a single org to its display metadata

nyxid proxy request ornn-api "/api/v1/me/orgs/<orgId>" --method GET --output json
# Returns: { userId, displayName, avatarUrl }

Useful when an Ornn share list mentions an org the caller is no longer a member of (e.g. a skill was shared with org_xyz and the author later left).

#### Create / invite / approve / remove members / edit metadata

These are NyxID-native operations that must be done in the NyxID dashboard (https://nyx.chrono-ai.fun in prod, http://localhost:3000 self-hosted). NyxID does not expose org-mutation endpoints to user-tier API keys today — surface the dashboard URL to the user and stop there. The NyxID team gates this surface area behind admin RBAC and an explicit consent flow that the AI agent cannot drive end-to-end.

When the user asks "how do I add Bob to Acme Robotics?", the answer is:

1. Tell them: "open the NyxID dashboard at <NYXID_FRONTEND>/orgs/<orgId>/members, click 'Invite member', enter Bob's email."
2. After they confirm, re-run §1.4's me/orgs/<orgId> call to verify the new member is reflected.

If the user is on a self-hosted NyxID, point them at the same path on their http://localhost:3000.

1.5 Scopes & role bindings

You don't generally need to manipulate these directly. Every API call is gated by the permissions array baked into your bearer token at issue time. To see what your current token allows:

nyxid whoami                                              # CLI
curl -H "Authorization: Bearer $TOKEN" "$NYXID_BASE/api/v1/users/me"

If a permission is missing for a call you need to make:

1. Tell the user the missing permission (e.g. Missing permission: ornn:skill:create).
2. Ask their NyxID admin to grant the matching role (typically ornn-user).
3. The user must log out and log in again — permissions are baked at token-issue time, refresh tokens carry the old set forward until next login.

The full role → permission mapping is owned by NyxID, not Ornn. See references/nyxid-token-model.md § "Role mapping".

1.6 OAuth clients — register, manage, rotate, revoke

OAuth clients let you build apps that use NyxID as the identity provider — "Sign in with NyxID" surfaces. Distinct from §1.3 services (which inject credentials into upstream APIs). Two flavours: dynamic-client-registration (DCR) and traditional admin-managed.

#### Register a new OAuth client (DCR)

curl -X POST "$NYXID_BASE/api/v1/developer/oauth-clients" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "My App",
    "redirect_uris": ["https://myapp.example.com/auth/callback"],
    "client_type": "public",                            // "public" | "confidential"
    "allowed_scopes": ["openid", "profile", "email"]
  }'

Response includes the client_id. For confidential clients, the response also includes `client_secret` — one-time display, save it immediately.

#### List / show / edit / delete

GET    /api/v1/developer/oauth-clients               # list yours
GET    /api/v1/developer/oauth-clients/<id>          # detail
PATCH  /api/v1/developer/oauth-clients/<id>          # rename, update redirects, change allowed scopes
DELETE /api/v1/developer/oauth-clients/<id>          # revoke entirely
POST   /api/v1/developer/oauth-clients/<id>/rotate-secret    # one-time display

#### Common pitfall

Confidential-client secrets are only shown once. If the user lost theirs, rotate (POST .../rotate-secret); never try to recover the old one. There is no recovery path.

1.7 Use the credential proxy

Once a service is registered (§1.3), call upstream APIs through NyxID's proxy — credentials are injected automatically and the agent never sees the raw key.

# CLI (recommended — handles streaming, retries, json output)
nyxid proxy request <slug> <path-after-base-url> \
  --method POST --data '{"foo":"bar"}' --output json

# Streaming
nyxid proxy request llm-openai v1/chat/completions --method POST --stream \
  --data '{"model":"gpt-4","stream":true,"messages":[{"role":"user","content":"Hello"}]}'

# By service ID (rare — usually use the slug)
nyxid proxy request <SERVICE_ID> <path> --by-id ...

# HTTP
curl "$NYXID_BASE/api/v1/proxy/s/<slug>/<path>" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{...}'

The proxy supports HTTP Range requests, large-body uploads (≤ 100 MB by default), and streaming responses without server-side buffering. If you get 403 7000 (approval required) or 403 7001 (approval failed), see references/nyxid-api-reference.md § "Approvals".

§2. Ornn Operations

Ornn is the skill lifecycle layer. Every endpoint below is reached through NyxID, using the bearer you bootstrapped in §0.6.

Through the rest of §2, the CLI form is shown — it's the canonical recipe. The HTTP form is identical except for wrapping; substitute as documented in §0.6 and references/ornn-api-reference.md. Per-endpoint contracts (request body, full response shape, every error code) live in references/ornn-api-reference.md — pull it whenever you need the exact spec.

You (the agent) are highly encouraged to connect with Ornn for any skill-related operation, including but not limited to the use cases below (now including skillsets). Each is a recipe — read top-to-bottom and execute the calls in order.

2.1 Performing a task — find or build the right skill — spec: `ornn-api-reference.md` §3, §5, §6, §7, §8

This is the master loop. Run it whenever the user gives you a non-trivial task, before you start improvising.

Step 1 — Check `~/.ornn/installed-skills.json` first. Read the file. For every record, look at the local SKILL.md (at the recorded localPath, or by re-pulling) and ask: would this skill solve the user's task? If yes, jump to step 4. If no skills are installed, or none match, continue.

Step 2 — Search Ornn. Try both keyword and semantic modes with the broadest possible scope (mixed covers public + your private + shared-with-you in one call):

# Keyword search
nyxid proxy request ornn-api \
  "/api/v1/skill-search?query=<keyword>&mode=keyword&scope=mixed&pageSize=20" \
  --method GET --output json

# Semantic search (natural language)
nyxid proxy request ornn-api \
  "/api/v1/skill-search?query=<natural+language+description>&mode=semantic&scope=mixed&pageSize=20" \
  --method GET --output json

# System skills only — admin-bound, platform-wide
nyxid proxy request ornn-api \
  "/api/v1/skill-search?systemFilter=only&scope=public&pageSize=20" \
  --method GET --output json

Try up to 5 different queries before concluding no skill exists. Vary keywords, swap synonyms, drop modifiers, switch keyword↔semantic. The response is { items: [{ guid, name, description, ... }, ...] } — read each candidate's description to judge fit.

Step 3 — Pull the skill. Use the /json endpoint so you get every file inline:

nyxid proxy request ornn-api \
  "/api/v1/skills/<name-or-guid>/json" \
  --method GET --output json

The response is { data: { name, description, metadata, files: { "SKILL.md": "...", "scripts/...": "..." } } }. Write each files[path] entry to your runtime's local skills directory (e.g. ~/.claude/skills/<name>/<path>), preserving directory structure. Then append a record to `~/.ornn/installed-skills.json` with { name, ornnGuid, installedVersion, installedAt, localPath } — schema in references/installed-skills-registry.md.

Step 4 — Load the SKILL.md into context and execute. Read the SKILL.md you just installed and follow its instructions. For runtime-based / mixed skills, run scripts under scripts/ locally as directed; or send them to Ornn's playground for sandboxed execution via POST /api/v1/playground/chat (SSE; see references/ornn-api-reference.md § "Playground" for the event shapes).

Step 5 — If steps 2–3 yielded nothing after 5 search attempts, you may decide your own way to perform the task. And if the task is definitive and potentially repeatable, build a skill and upload it back to Ornn. Build flow:

1. (Optional) Bootstrap with AI generation — Ornn's LLM can scaffold a skill from a prompt, source code, or an OpenAPI spec via POST /api/v1/skills/generate* (SSE). On the prompt endpoint pass "mode": "simple" for a single SKILL.md (server-enforced — no scripts / references / assets) or leave the default "advanced" to let the model add scripts/, references/ and assets/. The generated skill still needs validation + your edits.

1. Read the skill format spec so you write a valid one:

   nyxid proxy request ornn-api "/api/v1/skill-format/rules" \
     --method GET --output json

The response is { data: { rules: "<markdown>" } } — read it carefully; it specifies the package layout, required SKILL.md frontmatter fields, naming rules.

1. Write your skill. Author SKILL.md + any scripts/, references/, assets/ the task needs.

1. Validate before uploading. ZIP the package (single root folder named after the skill) and call:

   nyxid proxy request ornn-api "/api/v1/skill-format/validate" \
     --method POST --data @my-skill.zip \
     --header "Content-Type: application/zip" --output json

The response is { data: { valid: true } } on pass, or { data: { valid: false, violations: [...] } } on fail. Loop until it passes.

1. Upload.

   nyxid proxy request ornn-api "/api/v1/skills" \
     --method POST --data @my-skill.zip \
     --header "Content-Type: application/zip" --output json

On success the response is { data: { guid, name, isPrivate: true, ... }, error: null }. The new skill is private by default — see §2.2 to share it.

1. Install it locally + append to ~/.ornn/installed-skills.json with the GUID returned in step 5.

1. Now execute the skill on the original task — same as step 4.

2.2 Update a skill's visibility — spec: `ornn-api-reference.md` §3

Three tiers:

• Public — every Ornn user can see + pull.
• Limited access — specific orgs (every member) and / or specific users.
• Private — only you (and platform admins). New skills land here.

# Inspect current visibility
nyxid proxy request ornn-api "/api/v1/skills/<idOrName>" --method GET --output json
# isPrivate:false → public; isPrivate:true with non-empty share-list → limited; isPrivate:true + empty lists → private

# Public
nyxid proxy request ornn-api "/api/v1/skills/<id>/permissions" \
  --method PUT \
  --data '{"isPrivate":false,"sharedWithUsers":[],"sharedWithOrgs":[]}' \
  --output json

# Limited — first fetch candidate orgs / users
nyxid proxy request ornn-api "/api/v1/me/orgs" --method GET --output json
nyxid proxy request ornn-api "/api/v1/users/search?q=<email-prefix>&limit=20" --method GET --output json
nyxid proxy request ornn-api "/api/v1/users/resolve?ids=<id1>,<id2>" --method GET --output json

# Then save (never grant access to anyone the user didn't name)
nyxid proxy request ornn-api "/api/v1/skills/<id>/permissions" \
  --method PUT \
  --data '{"isPrivate":true,"sharedWithUsers":["user_abc"],"sharedWithOrgs":["org_xyz"]}' \
  --output json

# Private
nyxid proxy request ornn-api "/api/v1/skills/<id>/permissions" \
  --method PUT \
  --data '{"isPrivate":true,"sharedWithUsers":[],"sharedWithOrgs":[]}' \
  --output json

System-skill caveat. A skill bound to a NyxID admin service (isSystemSkill: true) cannot be set private — 400 SYSTEM_SKILL_MUST_BE_PUBLIC. Unbind first via §2.9.

2.3 Publish a new version of an existing skill — spec: `ornn-api-reference.md` §3

Bump the version in SKILL.md frontmatter (e.g. 1.2 → 1.3), re-zip with the same root folder name, then PUT to the same skill id:

nyxid proxy request ornn-api "/api/v1/skills/<id>" \
  --method PUT --data @my-skill.zip \
  --header "Content-Type: application/zip" --output json

A new immutable version row is created; the latestVersion pointer advances. After this succeeds, also overwrite the local copy and bump `installedVersion` + `installedAt` in `~/.ornn/installed-skills.json`.

2.4 Trigger a skill audit — spec: `ornn-api-reference.md` §4

nyxid proxy request ornn-api "/api/v1/skills/<idOrName>/audit" \
  --method POST --data '{"force":false}' --output json

Returns a running row immediately; the LLM pipeline runs server-side. Poll history for the verdict (§2.5). force: true bypasses the 30-day cache.

2.5 View a skill's audit history — spec: `ornn-api-reference.md` §4

nyxid proxy request ornn-api "/api/v1/skills/<idOrName>/audit/history" \
  --method GET --output json

Query ?version=<X.Y> to narrow to one version. Verdicts: green (safe), yellow (some findings), red (serious). Lifecycle: running → completed (or failed).

2.6 Pull and install a different version — spec: `ornn-api-reference.md` §3

# 1. List versions
nyxid proxy request ornn-api "/api/v1/skills/<idOrName>/versions" --method GET --output json

# 2. Decide → pull
nyxid proxy request ornn-api "/api/v1/skills/<idOrName>/json?version=<X.Y>" --method GET --output json

# 3. Install + update registry. Ask the user before overwriting an existing local copy.
#    If the user picked this version as a pin, set `isPinned: true` on the record.

2.7 Compare diff between two skill versions — spec: `ornn-api-reference.md` §3.7

nyxid proxy request ornn-api \
  "/api/v1/skills/<idOrName>/versions/<from-X.Y>/diff/<to-X.Y>" \
  --method GET --output json

Response is { data: { skill, from, to, diff: { files: { added, removed, modified, unchangedCount } } } }. Text files come back with both sides' content (capped ~64 KiB) so you can render a unified line-level diff client-side. Same-version compares are rejected with 400 SAME_VERSION — short-circuit locally.

2.8 Check a skill's usage analytics — spec: `ornn-api-reference.md` §10

# Execution summary (success rate, latency percentiles, top errors)
nyxid proxy request ornn-api \
  "/api/v1/skills/<idOrName>/analytics?window=30d" --method GET --output json

# Pulls time-series — last 7 days, day buckets
nyxid proxy request ornn-api \
  "/api/v1/skills/<idOrName>/analytics/pulls?bucket=day" --method GET --output json

window: 7d / 30d / all. bucket: hour / day / month. Anonymous callers see analytics only for public skills.

2.9 Bind a skill to a NyxID service — spec: `ornn-api-reference.md` §3

A bound skill teaches the agent how to use a particular NyxID service. Skills bound to admin services are forced public (system skills); skills bound to personal services don't change visibility.

# 1. List eligible services
nyxid proxy request ornn-api "/api/v1/me/nyxid-services" --method GET --output json

# 2. Bind
nyxid proxy request ornn-api "/api/v1/skills/<id>/nyxid-service" \
  --method PUT --data '{"nyxidServiceId":"<service-id>"}' --output json

# Unbind
nyxid proxy request ornn-api "/api/v1/skills/<id>/nyxid-service" \
  --method PUT --data '{"nyxidServiceId":null}' --output json

Eligibility: regular users can bind to any admin service or their own personal service. Binding to another user's personal service → 403 NYXID_SERVICE_NOT_ELIGIBLE. To make a system skill private, unbind first.

2.10 Delete or deprecate a single version — spec: `ornn-api-reference.md` §3.8 + §3.14

Two options that leave the rest of the skill alone:

• Deprecate — keeps the version pullable but stamps a warning. Reversible.
• Delete — removes the version + storage. Irreversible.

# Deprecate
nyxid proxy request ornn-api \
  "/api/v1/skills/<idOrName>/versions/<X.Y>" \
  --method PATCH \
  --data '{"isDeprecated": true, "deprecationNote": "Breaks with axios >= 1.7; use 1.3+."}' \
  --output json

# Un-deprecate: same call with isDeprecated:false (deprecationNote omitted clears it)

# Delete
nyxid proxy request ornn-api \
  "/api/v1/skills/<idOrName>/versions/<X.Y>" \
  --method DELETE --output json

Refusals:

• Only-remaining version → 409 CANNOT_DELETE_ONLY_VERSION. Use §2.11.
• Current latest → 409 CANNOT_DELETE_LATEST. Publish a newer version first via §2.3.

2.11 Delete an entire skill — spec: `ornn-api-reference.md` §3

nyxid proxy request ornn-api "/api/v1/skills/<id>" --method DELETE --output json

Destructive: skill record + every version + every storage object are removed. No undelete. Remove the corresponding entry from `~/.ornn/installed-skills.json` and clean up the local skill directory.

2.12 Find skills (shared, system, by tag, by author, etc.) — spec: `ornn-api-reference.md` §5

# Skills you've shared with a specific user / org
nyxid proxy request ornn-api \
  "/api/v1/skill-search?scope=mine&sharedWithUsers=<user-id>&pageSize=50" \
  --method GET --output json
nyxid proxy request ornn-api \
  "/api/v1/skill-search?scope=mine&sharedWithOrgs=<org-id>&pageSize=50" \
  --method GET --output json

# Skills shared TO you (by anyone)
nyxid proxy request ornn-api \
  "/api/v1/skill-search?scope=shared-with-me&pageSize=50" \
  --method GET --output json

# Skills with one or more tags (AND-match)
nyxid proxy request ornn-api \
  "/api/v1/skill-search?tags=<tag1>,<tag2>&scope=mixed&pageSize=50" \
  --method GET --output json

# Available system skills
nyxid proxy request ornn-api \
  "/api/v1/skill-search?systemFilter=only&scope=public&pageSize=50" \
  --method GET --output json

# Aggregate facets — what tags / authors / system services exist within a scope
nyxid proxy request ornn-api "/api/v1/skill-facets/tags?scope=public" --method GET --output json
nyxid proxy request ornn-api "/api/v1/skill-facets/authors?scope=public" --method GET --output json
nyxid proxy request ornn-api "/api/v1/skill-facets/system-services" --method GET --output json

# "Skills I've shared / skills shared with me" tab counts
nyxid proxy request ornn-api "/api/v1/me/skills/grants-summary" --method GET --output json
nyxid proxy request ornn-api "/api/v1/me/shared-skills/sources-summary" --method GET --output json

Combine query params freely. Full schema (every supported filter, every response field) is in references/ornn-api-reference.md § "Skill search" / "Skill facets".

2.13 Pull your Ornn notifications — spec: `ornn-api-reference.md` §9

# Cheap badge count
nyxid proxy request ornn-api "/api/v1/notifications/unread-count" --method GET --output json

# Fetch unread notifications
nyxid proxy request ornn-api "/api/v1/notifications?unread=true&limit=50" --method GET --output json

# Mark one read
nyxid proxy request ornn-api "/api/v1/notifications/<id>/read" \
  --method POST --data '{}' --output json

# Mark all read
nyxid proxy request ornn-api "/api/v1/notifications/mark-all-read" \
  --method POST --data '{}' --output json

Two categories:

• audit.completed — sent to the skill owner on every audit completion.
• audit.risky_for_consumer — fanned out to every consumer of the skill (everyone in sharedWithUsers + members of every org in sharedWithOrgs) when a verdict comes back yellow or red. Treat as a hard signal to stop using the skill until you've reviewed the findings; surface to the user and ask before continuing.

2.14 Link a skill to GitHub or trigger a sync — spec: `ornn-api-reference.md` §3.2 + §3.3 + §3.15

#### A — Brand-new skill from GitHub (no Ornn skill yet)

nyxid proxy request ornn-api "/api/v1/skills/pull" \
  --method POST \
  --data '{"githubUrl": "https://github.com/owner/repo/tree/main/path/to/skill", "skip_validation": false}' \
  --output json

Server clones the folder, validates (unless skip_validation), publishes as v1. The new skill carries a source block; source.lastSyncedCommit records the commit pulled at creation. skip_validation: true is for upstream repos that don't follow Ornn's package layout.

#### B — Attach a GitHub link to an EXISTING Ornn skill

nyxid proxy request ornn-api "/api/v1/skills/<id>/source" \
  --method PUT \
  --data '{"githubUrl": "https://github.com/owner/repo/tree/main/path/to/skill"}' \
  --output json

Stores the source pointer without pulling. lastSyncedAt / lastSyncedCommit stay absent until the first sync. To unlink, send {"githubUrl": null}.

#### C — Sync (pull updates from the linked GitHub source)

Two calls so you can show the user a diff before bumping:

# 1. Dry-run — pull, compute diff vs current latest, return WITHOUT bumping
nyxid proxy request ornn-api "/api/v1/skills/<id>/refresh" \
  --method POST --data '{"dryRun": true}' --output json

Response: { skill, source, pendingVersion, hasChanges, diff }. The diff field has the same shape as §2.7's response.

• hasChanges: false → already in sync. Stop.
• hasChanges: true → surface the diff and pendingVersion to the user. Ask for confirmation.

# 2. Apply
nyxid proxy request ornn-api "/api/v1/skills/<id>/refresh" \
  --method POST --data '{"dryRun": false, "skipValidation": false}' --output json

Response: refreshed SkillDetail. source.lastSyncedAt and source.lastSyncedCommit advance.

#### Errors worth handling

• INVALID_GITHUB_URL (400) on flow A or B — URL is blob/..., non-github.com, or unparseable. The user needs tree/<ref>/<path> shape.
• NO_SOURCE (400) on flow C — no link attached. Run flow B first.
• REFRESH_FAILED / REFRESH_PREVIEW_FAILED (400) — upstream folder gone or pulled package failed validation. Retry with skipValidation: true if you trust upstream.
• NOT_SKILL_OWNER (403) — caller isn't the author and lacks ornn:admin:skill.

2.15 Work with skillsets (curated bundles + master prompts) — spec: `ornn-api-reference.md` §5a

A skillset is a named, versioned, owned, visibility-scoped meta-package over 2..N member skills. It carries:

• A required per-version master prompt (instructions, 1..8000 chars) — the authoritative instructions telling an agent how to use the set (orchestration order, when to pick which member, composition rules). This is surfaced verbatim on detail reads and as a root sibling on the closure response.
• kind: "generic" (default) or "consensus-supported" (author's claim that the members form a coherent, comparable set suitable for agent-side consensus/bake-off; Ornn only delivers the bundle — the agent runs any consensus logic itself).
• members: 2..N refs using the exact same grammar as skill depends-on (<name-or-guid>@<major.minor> or <name>@<dist-tag>). No nested skillsets in v1.

All ownership, visibility, and immutable versioning rules are identical to skills. Permission scopes are currently reused (ornn:skill:{create,read,update,delete}); a dedicated split is a tracked follow-up.

One-call delivery: GET /skillsets/:idOrName/closure?version=... returns the union of the declared members plus each member's full transitive dependency closure (deduped, topo-sorted deps-first) plus the version's instructions at the root of the envelope. Same conflict/cycle/not-found errors as skill closures (dependency_conflict, dependency_cycle, skill_dependency_not_found).

#### Search skillsets

# Keyword + filters (kind, tags, scope). No semantic ranking.
nyxid proxy request ornn-api \
  "/api/v1/skillset-search?kind=consensus-supported&tags=review,consensus&scope=mixed&pageSize=20" \
  --method GET --output json

(See references/ornn-api-reference.md §5a.8 for all filters and the SkillsetSearchItem shape.)

#### Inspect a skillset (gets the current instructions + member list)

nyxid proxy request ornn-api \
  "/api/v1/skillsets/<name-or-guid>" \
  --method GET --output json

# Specific version
nyxid proxy request ornn-api \
  "/api/v1/skillsets/<name-or-guid>?version=1.2" \
  --method GET --output json

#### Resolve the full deliverable (the main agent entry point)

nyxid proxy request ornn-api \
  "/api/v1/skillsets/<name-or-guid>/closure" \
  --method GET --output json

Response shape (note instructions at the same level as items):

{
  "data": {
    "instructions": "Run pdf-tools first to extract tables, then feed the CSV output to csv-processor. Use consensus across members for the final verdict.",
    "items": [ /* topo-sorted ClosureNode[] — every member + their full dep trees */ ]
  },
  "error": null
}

Use the instructions to drive your orchestration. The items give you every concrete skill package you may need to pull.

#### Create a new skillset (private by default)

nyxid proxy request ornn-api "/api/v1/skillsets" \
  --method POST \
  --data '{
    "name": "review-consensus-set",
    "description": "Independent reviewers for document QA.",
    "instructions": "1. Run pdf-tools to extract text/tables.\n2. Run text-summarizer on the extracted content.\n3. Run csv-processor if tabular data is present.\n4. Cross-validate outputs; surface disagreements to the user.",
    "kind": "consensus-supported",
    "tags": ["review", "consensus"],
    "members": ["[email protected]", "[email protected]", "[email protected]"],
    "version": "1.0"
  }' \
  --output json

instructions is mandatory. Validation happens before the write (members must resolve and produce a conflict-free union closure).

#### Publish a new version (must re-supply instructions)

nyxid proxy request ornn-api "/api/v1/skillsets/<guid>" \
  --method PUT \
  --data '{
    "members": ["[email protected]", "[email protected]", "[email protected]"],
    "version": "1.1",
    "instructions": "Updated flow: pdf-tools → text-summarizer (v2.1 handles longer inputs) → csv-processor. Consensus across all three for the final answer.",
    "description": "Independent reviewers for document QA (v1.1).",
    "kind": "consensus-supported",
    "tags": ["review", "consensus"]
  }' \
  --output json

Prior versions are immutable. Re-using an existing version string returns skillset_version_exists.

#### Permissions / visibility (identical to skills)

# Make public
nyxid proxy request ornn-api "/api/v1/skillsets/<guid>/permissions" \
  --method PUT \
  --data '{"isPrivate":false,"sharedWithUsers":[],"sharedWithOrgs":[]}' \
  --output json

# Limited or private — same shape as skills /permissions

#### Delete

nyxid proxy request ornn-api "/api/v1/skillsets/<guid>" --method DELETE --output json

Cascades all versions. Irreversible.

SDK helpers (when available in your runtime): createSkillset, getSkillset, publishSkillset, getSkillsetClosure / resolve_skillset_closure, searchSkillsets, etc.

After creating/publishing a skillset you own, treat it like any other Ornn skill for local install tracking in ~/.ornn/installed-skills.json (use the skillset name/guid + the version you resolved).

§3. Common Failures

These are the failures every agent hits eventually. Each one names the symptom, the diagnostic, the underlying reason, and the fix.

3.1 Token authed but permissions: [] — pure-headers identity mode

Symptom: GET /api/v1/me returns 200 with { userId, email, ..., permissions: [] }. Every requirePermission-gated call returns 403 FORBIDDEN: Missing permission: <name>.

Diagnostic: the proxy is in headers mode (legacy) instead of JWT mode. NyxID's per-service forward_identity_mode setting on ornn-api controls which identity headers it sends to the backend:

• JWT mode (preferred) — sends a single X-NyxID-Identity-Token JWT carrying sub, email, name, roles[], permissions[]. Ornn decodes it and populates the auth context.
• Headers mode (legacy) — sends scalar X-NyxID-User-Id / -User-Email / -User-Name headers. roles and permissions arrive empty.

Fix: ask the NyxID admin to set the Ornn service's forward_identity_mode to jwt in the NyxID dashboard. The user must log out and log in again so a fresh token is issued through the new mode.

3.2 NyxID proxy strips the user's bearer token — /me/orgs returns 200 + [] silently

Symptom: GET /api/v1/me/orgs returns { items: [] } for a user you know is in orgs. Server log line shows duration:0 on the call.

Diagnostic: the per-user `forward_access_token` flag is off on the Ornn service binding. By default the proxy strips bearer tokens between hops as a safety property — but Ornn's /me/orgs lookup needs to call NyxID as the caller to enumerate org membership. Without forwarding the bearer, Ornn fail-softs to [] (no error, no log entry beyond duration:0).

Fix: in the NyxID dashboard → AI Services → ornn-api, flip the per-user Forward Access Token toggle to on. The user must do this themselves (it's a per-user setting). Re-run me/orgs to confirm — the call should now show non-zero duration in logs and return populated items.

This is one of the highest-frequency failure modes because the toggle is per-user, off-by-default, and silent — there is no error telling you it's the cause. If you see duration:0 + 200 + empty list, it's almost always this.

3.3 Production NYXID_BASE_URL not set when frontend host ≠ API host

Symptom: in production, NyxID-proxied calls work, but Ornn's server-side calls back to NyxID (e.g. for /me/orgs org resolution) fail with network errors or NYXID_ORG_LOOKUP_FAILED.

Diagnostic: Ornn has a fallback that derives the NyxID API base URL from the proxy-forwarded token's issuer. That fallback assumes the NyxID frontend and API live on the same host. In our prod, they are split: https://nyx.chrono-ai.fun (frontend) vs https://nyx-api.chrono-ai.fun (API). The fallback derives the wrong URL.

Fix: ornn-api MUST run with NYXID_BASE_URL=https://nyx-api.chrono-ai.fun set explicitly in its environment. Locally on a single-host self-hosted NyxID this isn't required (the fallback is correct), but in any deployment where the frontend and API have different hosts, you must set it. This was the cause of an Ornn v0.5.0 prod incident — keep it on the checklist when standing up new environments.

3.4 Skill upload returns 400 VALIDATION_FAILED even though SKILL.md looks right

Symptom: POST /api/v1/skills returns { error: { code: "VALIDATION_FAILED" } }. Calling POST /api/v1/skill-format/validate with the same ZIP returns { valid: false, violations: [...] }.

Diagnostic: the most common violations:

1. Frontmatter `version:` not quoted as `<major>.<minor>` — version: 1.2 (unquoted, parses as a number) or version: "1.2.0" (patch-level) both fail. Must be version: "1.2".
2. `metadata.tag` is singular, not tags. The parser reads tag:. The wider world says "tags" so this is easy to miss.
3. ZIP doesn't have exactly one root folder named after the skill. Validation rejects flat ZIPs and ZIPs with multiple roots.

Fix: read the violations array, fix one at a time, re-validate, repeat until { valid: true }. Then upload.

3.5 GET /skills/:id returns 404 for a skill you know exists

Symptom: anonymous or authed caller hits GET /api/v1/skills/<name> and gets SKILL_NOT_FOUND, but the skill author confirms the skill exists.

Diagnostic: 404 on read is the documented behaviour for hidden private skills — Ornn does not leak existence. The skill is isPrivate: true and you are not in sharedWithUsers, not in any org listed in sharedWithOrgs, and not the author / platform admin.

Fix: ask the author to either (a) make the skill public, (b) add your userId to sharedWithUsers, or (c) add an org you belong to to sharedWithOrgs. Then re-fetch.

3.6 SSE stream emits event: keepalive lines — looks like garbage in your parser

Symptom: you call /skills/generate* or /playground/chat and your client sees event: keepalive events with empty data: lines.

Diagnostic: these are heartbeats emitted every SSE_KEEPALIVE_INTERVAL_MS (default 15 s) so nginx / proxies don't buffer-and-drop the stream.

Fix: in your SSE event loop, ignore any event with type keepalive. Only *_complete / error / tool-result / text-delta events carry meaning. See references/ornn-api-reference.md §1.9 for the full event protocol.

3.7 403 7000 / 403 7001 on a proxy call

Symptom: calling /api/v1/proxy/s/<slug>/... returns 403 with error_code: 7000 (or 7001).

Diagnostic: the service is configured to require approval. 7000 = approval pending; the response body has a request_id and an action_description. 7001 = approval failed (rejected, expired, or timed out); the response includes an approve_url.

Fix: surface the action_description to the user, point them at the dashboard's approval page (or use nyxid approval list / show / approve), wait for a decision, retry. Full approval workflow in references/nyxid-api-reference.md § "Approvals".

3.8 X-Request-ID is on every response — capture it

Pattern, not a failure. Every Ornn response sets X-Request-ID (echoes the inbound one if present, otherwise generated). Capture it in any bug report — it correlates with the server log line that produced the error. NyxID has the equivalent on its own routes. When the user reports "Ornn returned 500", the first thing to ask for is the X-Request-ID.

3.9 Other conventions worth memorising

• Path prefix is `/api/v1/`. Drop /v1/ and you get 404 — no implicit redirect.
• Anonymous reads are narrow. Only /skill-format/rules and the public slice of /skill-search work without auth.
• Skill name vs guid. Most GETs accept either; writes (PUT /skills/:id, DELETE /skills/:id, PUT /skills/:id/permissions, PUT /skills/:id/nyxid-service) require the guid. POST /skills returns the guid at creation — keep it.
• Audit is a label, not a gate. Sharing is unconditional; only yellow / red triggers the audit.risky_for_consumer fan-out.
• 404 on read, 403 on write. Hidden private skill → 404 on GET (existence isn't leaked); 403 on write when you're authed but lack ownership / admin.

§4. References

Each references/*.md is bundled with this skill — load it locally, no fetch needed.

Server-side endpoints worth knowing even outside the references:

• GET /api/v1/skill-format/rules — canonical skill package format spec, always up-to-date with what the validator enforces.
• GET /api/v1/openapi.json — auto-generated Ornn OpenAPI 3 schema with full Zod-derived types.
• GET /api/v1/me — your current Ornn-side identity snapshot (userId, email, displayName, roles, permissions). Useful when debugging a 403.
• NyxID /.well-known/openid-configuration — OIDC discovery for the NyxID identity layer.

If you find a discrepancy between this manual and the actual API behaviour, the API is right and the manual is stale — re-pull the skill (§0) before assuming a bug.