**Actionable comments posted: 1**

🧹 Nitpick comments (4)

api-reference/openapi.json (2)
`5967-5986`: **Consider using reusable response components for repeated 400/401 blocks** The same `400`/`401` response objects are repeated across all research operations. Centralizing them under `components.responses` will reduce duplication and prevent drift.

♻️ Example refactor pattern
```diff + "components": { + "responses": { + "ResearchValidationError": { + "description": "Validation error", + "content": { + "application/json": { + "schema": { + "$ref": "#/components/schemas/ResearchErrorResponse" + } + } + } + }, + "ResearchAuthError": { + "description": "Authentication failed — invalid or missing API key", + "content": { + "application/json": { + "schema": { + "$ref": "#/components/schemas/ResearchErrorResponse" + } + } + } + } + } + } ``` ```diff - "400": { ...ResearchErrorResponse... }, - "401": { ...ResearchErrorResponse... } + "400": { "$ref": "#/components/responses/ResearchValidationError" }, + "401": { "$ref": "#/components/responses/ResearchAuthError" } ```

🤖 Prompt for AI Agents
``` Verify each finding against the current code and only fix it if needed. In `@api-reference/openapi.json` around lines 5967 - 5986, The OpenAPI spec repeats identical 400 and 401 response objects for research endpoints; refactor by creating reusable entries under components.responses (e.g., components.responses.ResearchBadRequest and components.responses.Unauthorized or similar) that reference the existing ResearchErrorResponse schema and then replace each inline "400" and "401" response block with $ref pointers to those new components; update any operation objects that currently embed the repeated blocks to use these component refs to remove duplication and keep semantics identical. ```
--- `14965-14968`: **Keep `status` constrained in success response schemas** In several updated schemas, `status` became an unconstrained string with only an example. That loosens the contract and reduces SDK type safety. Prefer `enum: ["success"]` (or `const: "success"`) for 200-success payloads.

✅ Example for one affected schema
```diff "status": { - "type": "string", - "example": "success" + "type": "string", + "enum": ["success"], + "example": "success" } ```
Also applies to: 15016-15019, 15258-15261, 15476-15478, 15531-15533, 16142-16145

🤖 Prompt for AI Agents
``` Verify each finding against the current code and only fix it if needed. In `@api-reference/openapi.json` around lines 14965 - 14968, The response schema currently defines "status" as an unconstrained string with only an example; update each affected success-response schema (e.g., the schema object that contains the "status" property shown in this diff and the other listed occurrences) to constrain it to the literal "success" by replacing the loose string type with either "enum": ["success"] or "const": "success" so the OpenAPI contract and generated SDK types reflect the fixed success value. Locate the "status" property definitions in the shown schema and the other occurrences (lines referenced in the comment) and change their definition accordingly, keeping any existing example if desired. ```

cli.mdx (2)
`379-381`: **Tighten repetitive “Deep web research” phrasing.** The heading and first sentence repeat the same wording; a shorter sentence improves scanability.

✏️ Suggested copy tweak
```diff ### Deep web research -Deep web research that synthesizes information from across the web into a cited report. +Synthesize web findings into a cited report. ```
As per coding guidelines, "Keep documentation content concise and scannable."

🤖 Prompt for AI Agents
``` Verify each finding against the current code and only fix it if needed. In `@cli.mdx` around lines 379 - 381, The heading "Deep web research" and the following sentence repeat the same phrase; remove the redundancy by shortening the sentence under the "Deep web research" heading to a concise descriptor (e.g., "Synthesizes information from across the web into a cited report.") so the heading remains and the body becomes a single scannable line; update the sentence text beneath the "Deep web research" heading to the concise version and remove the original repetitive sentence. ```
--- `350-350`: **Consider making radio scope explicit.** “List tracked radio stations” is fine, but “List globally tracked radio stations” is slightly clearer at a glance. As per coding guidelines, "Use clear, self-documenting titles and descriptions in documentation."

🤖 Prompt for AI Agents
``` Verify each finding against the current code and only fix it if needed. In `@cli.mdx` at line 350, Update the documentation string "List tracked radio stations" to explicitly indicate scope by changing it to "List globally tracked radio stations" wherever the exact phrase appears (e.g., the title or description in the CLI docs entry that currently reads "List tracked radio stations") so the command description is self-documenting and unambiguous; ensure the modified phrase is used consistently in the CLI help/MDX entry and keep formatting identical to surrounding lines. ```

🤖 Prompt for all review comments with AI agents

``` Verify each finding against the current code and only fix it if needed. Inline comments: In `@api-reference/openapi.json`: - Around line 6166-6190: The schemas for the query parameters "country", "interval", and "type" lack the constraints described in their descriptions; update the parameter schemas in openapi.json for the "country" parameter to enforce a two-letter ISO code (e.g., add minLength: 2, maxLength: 2 and a pattern like two alphabetic chars) and update "interval" and "type" to use explicit enums (interval: ["daily","weekly"]; type: ["regional","viral"]) so generated validators/SDKs will enforce the documented constraints; locate the parameter objects named "country", "interval", and "type" and add these schema constraint fields accordingly. --- Nitpick comments: In `@api-reference/openapi.json`: - Around line 5967-5986: The OpenAPI spec repeats identical 400 and 401 response objects for research endpoints; refactor by creating reusable entries under components.responses (e.g., components.responses.ResearchBadRequest and components.responses.Unauthorized or similar) that reference the existing ResearchErrorResponse schema and then replace each inline "400" and "401" response block with $ref pointers to those new components; update any operation objects that currently embed the repeated blocks to use these component refs to remove duplication and keep semantics identical. - Around line 14965-14968: The response schema currently defines "status" as an unconstrained string with only an example; update each affected success-response schema (e.g., the schema object that contains the "status" property shown in this diff and the other listed occurrences) to constrain it to the literal "success" by replacing the loose string type with either "enum": ["success"] or "const": "success" so the OpenAPI contract and generated SDK types reflect the fixed success value. Locate the "status" property definitions in the shown schema and the other occurrences (lines referenced in the comment) and change their definition accordingly, keeping any existing example if desired. In `@cli.mdx`: - Around line 379-381: The heading "Deep web research" and the following sentence repeat the same phrase; remove the redundancy by shortening the sentence under the "Deep web research" heading to a concise descriptor (e.g., "Synthesizes information from across the web into a cited report.") so the heading remains and the body becomes a single scannable line; update the sentence text beneath the "Deep web research" heading to the concise version and remove the original repetitive sentence. - Line 350: Update the documentation string "List tracked radio stations" to explicitly indicate scope by changing it to "List globally tracked radio stations" wherever the exact phrase appears (e.g., the title or description in the CLI docs entry that currently reads "List tracked radio stations") so the command description is self-documenting and unambiguous; ensure the modified phrase is used consistently in the CLI help/MDX entry and keep formatting identical to surrounding lines. ```

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR: - [ ] Push a commit to this branch (recommended) - [ ] Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

**Configuration used**: defaults **Review profile**: CHILL **Plan**: Pro **Run ID**: `024fa5e7-386e-4e99-b43c-df41274ab422`

📥 Commits

Reviewing files that changed from the base of the PR and between 8cd0bf2dceba676b79a06ad881534e1b5dda58d2 and 57a465295a9e48cec9e788a420d0d0d878440e6c.

📒 Files selected for processing (2)

* `api-reference/openapi.json` * `cli.mdx`