🤖 Auto-Update: API Documentation OpenAPI Spec

[SohamRatnaparkhi]

Auto-generated from hydradb-application @ 6a9e3873a7492d091ac8c1f90bc0f190bd3d09c8 (staging).
Merging deploys docs via Mintlify. Review api-reference/v2/openapi.json before merging.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
cortex-ai	🟢 Ready	View Preview	Sep 23, 2026, 5:18 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[github-actions]

✅ Mintlify Hygiene

No issues found.

[openhack-agent]

✅ OpenHack Summary

Security review of 🤖 Auto-Update: API Documentation OpenAPI Spec. 1 changed file; 0 findings at or above the low reporting threshold.

0   0   0   0

Confidence Score: 5/5

No reportable security findings were detected in this scan.

Security merge-readiness rubric: 1 = critical, 2 = high, 3 = medium, 4 = low, 5 = no reportable findings. This score reflects scan findings, not a guarantee of correctness or complete coverage.

Files Needing Attention: None

Important Files Changed

• api-reference/v2/openapi.json (modified)

Last reviewed commit: 5bb26ff · View review on OpenHack

---

TIP: Mention @openhack-agent in a PR comment to request a review or ask a question. Use @openhack-agent fix all for every finding, or @openhack-agent fix unresolved threads for open review threads only.

[openhack-agent]

OpenHack reviewed this commit. See the OpenHack Summary for the confidence score and fix actions.

[greptile-apps]

Confidence Score: 4/5

The PR should not merge until the /query response variants are made mutually exclusive, since valid four-key responses currently violate the published oneOf contract.

Findings

1.  Response Variants Overlap ▶
2.  Examples Contradict Schemas ▶

Summary

This automated update synchronizes the v2 OpenAPI contract with the application, adding and revising database, connector, ingestion, query, profile, credential-vault, and graph APIs.

• Adds unified context ingestion and expanded query response models.
• Adds connector pause/resume, credential-vault, database rename/instructions, and profile/subgraph operations.
• Updates filtering, storage-layout, ACL-warning, plan-cap, and deprecation documentation.
• Greptile automatically discovered a related ticket that helped explain the purpose of this PR: keeping the Go-generated OpenAPI specification reliably synchronized with the Mintlify documentation repository.

_{Reviews (1) · Last reviewed commit: "chore(docs): update OpenAPI spec from hy..."}

[greptile-apps]

Response Variants Overlap

A valid four-key /query response satisfies both branches of this oneOf. search.QueryResult requires those four keys, while search.V2RetrievalResult has no required fields and permits unknown properties. Because oneOf requires exactly one match, conforming validators and generated clients can reject or fail to decode ordinary /query responses. Make the variants mutually exclusive or use a non-exclusive union.

[greptile-apps]

Examples Contradict Schemas

Several newly generated examples do not match their declared schemas: collections is an object but is shown as an array, credentials is an array but is shown as an object, context is an array but is shown as a string, and boolean upsert is shown as "true". These examples feed the published API reference and can lead users or generated examples to send structurally invalid values. Update the generator annotations so each example conforms to its schema.