GPT-5 finding
Inconsistent API base paths and owner scoping may confuse clients
mediumapi-contracthigh
- gitlawb/references/api-reference.md:32-37
- gitlawb/references/api-reference.md:43-44
- gitlawb/references/api-reference.md:72-75
- gitlawb/references/api-reference.md:102-106
- gitlawb/references/api-reference.md:50-57
The docs mix endpoints under /api/v1 with root-scoped endpoints (/repos for Git Smart HTTP, /tasks, /health, /peers, /ipfs). Additionally, Git Smart HTTP paths omit {owner} even though other repo endpoints include owner/name. Without an explicit routing convention, clients may construct incorrect URLs or be unable to disambiguate repositories by owner.
Recommendation
Document the base path conventions clearly: which resources live under /api/v1 versus root, and why. For Git Smart HTTP, clarify whether {owner} is required in the path (e.g., /repos/{owner}/{name}/git-receive-pack) or if {name} is globally unique on the node. If both forms are supported, provide explicit examples for each. Consider aligning all JSON API endpoints under /api/v1 and reserving root for Git Smart HTTP only.