🤖 Auto-Update: API Documentation OpenAPI Spec

[SohamRatnaparkhi]

Auto-generated from hydradb-application @ 90ba87bf22729efa0749c8566610bf09055a8247 (main).
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 19, 2026, 5:29 PM

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

[github-actions]

✅ Mintlify Hygiene

No issues found.

[greptile-apps]

Confidence Score: 4/5

The PR should not merge until the advertised JSON ingestion body is represented in the machine-readable request contract; the remaining findings are documentation-quality corrections.

Findings

1.  JSON ingestion is undefined ▶
2.  Examples violate their schemas ▶
3.  All behavior is undocumented ▶
4.  No-cache contract is missing ▶

Summary

This generated OpenAPI update substantially expands the v2 contract with unified ingestion, database administration, connector lifecycle controls, retrieval diagnostics, entity profiles, credential-vault operations, and additional schema fields. The primary merge blocker is that JSON ingestion is advertised but omitted from the machine-readable request content map.

• Adds connector pause/resume, plan-cap, and ACL-warning surfaces.
• Adds database rename and custom-instruction operations.
• Expands unified context ingestion and retrieval response models.
• Adds entity-profile, subgraph, and credential-vault routes.
• Contains several schema/example and supporting-guide inconsistencies.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Client[API client or generated SDK] --> API[v2 OpenAPI surface]
  API --> Ingest[Unified context ingestion]
  API --> Query[Query, profiles, and subgraphs]
  API --> Connectors[Connector pause, resume, and health]
  API --> Databases[Database lifecycle and instructions]
  API --> Vault[Credential vault]
  Ingest --> Context[Knowledge and memory corpora]
  Query --> Context
  Connectors --> Context
  Databases --> Context

Loading

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

[greptile-apps]

JSON ingestion is undefined

This description says callers may send an application/json ingest body, but requestBody.content defines only multipart/form-data. OpenAPI renderers and generated SDKs therefore cannot expose the advertised JSON request shape, and the maintained endpoint guide still tells callers not to send JSON. Add an application/json content entry with the unified ingest schema, or remove the JSON-body claim if it is unsupported.

Knowledge Base Used:

• API integration surface
• Ingestion processing APIs

[greptile-apps]

Examples violate their schemas

Several new examples have the wrong JSON type: collections is an object map but uses an array example, credentials is an array but uses an object example at lines 4775–4783, and the boolean upsert uses the string example "true" at lines 5672–5674. These mismatches can produce misleading Mintlify samples and fail schema-example validation. Each example should match its declared type.

Knowledge Base Used: API integration surface

[greptile-apps]

All behavior is undocumented

The list request now accepts type: "all", but this description still mentions only knowledge and memory, and the maintained List Context guide documents only those two values. Document what all returns and update the guide so callers do not have to guess how combined results are merged, ordered, or scoped.

Knowledge Base Used: API endpoint families

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

No-cache contract is missing

The credential-reveal operation says its plaintext-secret response must never be cached, but this successful response does not declare a Cache-Control: no-store header. Add that response-header contract so consumers and generated documentation can verify the required handling instead of relying only on prose.

[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: 19f145b · 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.