Update to Inngest

{
  "description": "Use when the user explicitly asks for the Inngest REST API v2, raw HTTP, OpenAPI, API docs, API authentication, or an endpoint that the Inngest CLI does not expose. Covers api-docs.inngest.com, llms.txt, the OpenAPI v2 spec, Bearer authentication with API keys or signing keys, production and local base URLs, raw curl/fetch requests, request-shape discovery, pagination, secret redaction, and when to prefer the `inngest-api-cli` skill instead.",
  "included_files": [
    {
      "relative_path": "references/rest-api-v2.md",
      "size_in_bytes": 7477
    }
  ],
  "name": "inngest-api",
  "skill_md_contents": "---\nname: inngest-api\ndescription: >-\n  Use when the user explicitly asks for the Inngest REST API v2, raw HTTP,\n  OpenAPI, API docs, API authentication, or an endpoint that the Inngest CLI\n  does not expose. Covers api-docs.inngest.com, llms.txt, the OpenAPI v2 spec,\n  Bearer authentication with API keys or signing keys, production and local\n  base URLs, raw curl/fetch requests, request-shape discovery, pagination,\n  secret redaction, and when to prefer the `inngest-api-cli` skill instead.\n---\n\n# Inngest REST API v2\n\nFor Cloud operations with connected MCP tools, use `inngest-cloud` first.\nKeep this skill for explicit terminal/HTTP work or a capability missing from\nMCP. Do not ask for an API key when OAuth MCP can complete the task.\n\nUse this skill for raw REST API v2 work and API reference lookup. If the task\ncan be completed through `npx inngest-cli@latest api`, use `inngest-api-cli`\ninstead; the CLI is safer for agents because it handles target/auth flags and\nendpoint command wiring.\n\n## Prefer CLI First\n\nUse `inngest-api-cli` for:\n\n- Run and trace debugging from a run ID or event ID.\n- Account, environment, key, webhook, app sync, and function invocation checks.\n- Insights table/schema/query workflows.\n- Local dev server or Cloud operational checks.\n\nUse raw REST API v2 only when:\n\n- The CLI does not expose the needed endpoint.\n- The user explicitly asks for HTTP, curl, fetch, OpenAPI, or API docs.\n- You need to inspect request/response schemas before deciding what to do.\n\n## Docs Lookup\n\nWhen precision matters, fetch current docs instead of guessing:\n\n- API overview: `https://api-docs.inngest.com/`\n- Authentication: `https://api-docs.inngest.com/authentication`\n- LLM index: `https://api-docs.inngest.com/llms.txt`\n- OpenAPI v2 spec: `https://api-docs.inngest.com/api-specs/v2.json`\n- Markdown page pattern: add `.md` to a docs URL, for example\n  `https://api-docs.inngest.com/v2/runs/GetFunctionTrace.md`\n- Endpoint request/response schemas:\n  [references/rest-api-v2.md](references/rest-api-v2.md)\n\nIf a Markdown page returns an error or omits generated reference details, use\nthe OpenAPI spec for methods, paths, parameters, request bodies, and schemas.\n\n## Base URLs\n\n- Cloud v2: `https://api.inngest.com/v2`\n- Local dev server v2: `http://localhost:8288/api/v2`\n- API docs say the dev server may also be reached through the local server\n  origin. Confirm the actual dev server port before making local requests.\n\n## Authentication\n\nThe REST API uses Bearer token authentication.\n\n- Prefer `INNGEST_API_KEY` for requests from CI, scripts, tools, and agents.\n- Signing keys are primarily for apps communicating with Inngest; use them for\n  API requests only when that is the available, appropriate credential.\n- API keys are for v2 endpoints only.\n- Include `X-Inngest-Env` or use an environment-scoped API key when operating\n  outside the default production environment.\n- Never paste, print, commit, or log API keys, event keys, signing keys,\n  webhook URLs, or decrypted secrets.\n\nExample:\n\n```bash\ncurl -fsSL \\\n  -H \"Authorization: Bearer $INNGEST_API_KEY\" \\\n  -H \"X-Inngest-Env: $INNGEST_ENV\" \\\n  https://api.inngest.com/v2/account\n```\n\n## Endpoint Discovery\n\nUse the OpenAPI spec as the source of truth:\n\n```bash\ncurl -fsSL https://api-docs.inngest.com/api-specs/v2.json\n```\n\nCurrent v2 areas include account, environments, keys, webhooks, apps, function\ninvocation, event-run lookup, function runs, traces, Insights, and partner APIs.\nEndpoint coverage can change, so inspect the spec before writing a raw request.\n\nFor API-only or access-gated endpoints, such as partner-account endpoints,\nconfirm the user has the needed access before attempting a call.\n\n## Request Rules\n\n- Derive method, path, query params, headers, and body from OpenAPI.\n- Do not invent undocumented request fields.\n- Use structured JSON parsing before making decisions from responses.\n- Use body files or here-docs for complex JSON instead of shell-escaped one\n  liners.\n- Add pagination cursors when `page.hasMore` is true and complete results are\n  needed.\n- Treat missing `data` in list responses as an empty list unless an error is\n  present.\n\n## Mutation Safety\n\nRead before write. Confirm target account, environment, resource, and intent\nbefore raw HTTP mutations unless the user's instruction already makes all of\nthat explicit.\n\nTreat these categories as mutating or side-effecting:\n\n- Creating or patching environments.\n- Creating webhooks.\n- Syncing apps.\n- Invoking functions.\n- Partner account creation.\n- Broad Insights queries that may be expensive or noisy.\n\n## Output Handling\n\n- Summarize IDs, names, statuses, pagination, and actionable errors.\n- Redact token values, webhook URLs, sensitive payload fields, and decrypted\n  secrets.\n- Do not paste large raw traces, full OpenAPI fragments, or full response\n  bodies unless the user asks.\n- If auth fails, first verify that a credential is present in the environment;\n  then ask the user to provide or rotate `INNGEST_API_KEY` without pasting it\n  into chat.\n"
}