How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Sageox Git API

Browse repository files, view commits, compare branches, and manage the Ledger. The Ledger stores historical context (decisions, discussions, AI-generated summaries) as version-controlled files in a GitLab-backed repository. Also handles repository uninstall and permanent deletion workflows.

Sageox Git API is one of 23 APIs that Sageox publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Git. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 16 operations across 15 paths, and defines 1 schema. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against 3 base URLs: http://localhost:3000, https://test.sageox.ai, https://sageox.ai.

16 operations 15 paths 1 schemas 14 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Servers
http://localhost:3000
https://test.sageox.ai
https://sageox.ai
Authentication
HTTP Bearer
Contact
SageOx Team
License
MIT
Resource Areas
1

Authentication & Security 1

Sageox Git API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — JWT token obtained from the auth service (/api/auth/token). Token is validated using JWKS from the auth service. Required claims: sub (userid), email, name, ti…

Paths & Operations 16

Across 15 paths, the API surfaces 16 operations — 14 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Git 16

Browse repository files, view commits, compare branches, and manage the Ledger. The Ledger stores historical context (decisions, discussions, AI-generated summaries) as version-co…

GET
/api/v1/repos/{repo_id}/tree
Get repository file tree
getRepoTree 4 params → 200400401403404500
GET
/api/v1/repos/{repo_id}/files/{path}
Get file content or blame information
getRepoFileOrBlame 3 params → 200400401403404500
GET
/api/v1/repos/{repo_id}/files/{path}/blame
Get file blame information
getRepoFileBlame 3 params → 200400401403404500
GET
/api/v1/repos/{repo_id}/commits
List repository commits
getRepoCommits 5 params → 200400401403404500
GET
/api/v1/repos/{repo_id}/commits/{sha}
Get commit details
getRepoCommit 2 params → 200400401403404500
GET
/api/v1/repos/{repo_id}/compare
Compare two references
getRepoCompare 3 params → 200400401403404500
GET
/api/v1/repos/{repo_id}/ledger-status
Check repository Ledger status
getRepoLedgerStatus 1 param → 200400401404500
POST
/api/v1/repos/{repo_id}/create-ledger
Create repository Ledger
createRepoLedger 1 param → 200201400401404503
GET
/api/v1/teams/{team_id}/norms-repo/tree
Get team norms repository file tree
getTeamNormsTree 4 params → 200400401403404500
GET
/api/v1/teams/{team_id}/norms-repo/files/{path}
Get team norms file content or blame
getTeamNormsFileOrBlame 3 params → 200400401403404500
PUT
/api/v1/teams/{team_id}/norms-repo/files/{path}
Create or update team norms file
putTeamNormsFile 2 params body → 200400401403404500
GET
/api/v1/teams/{team_id}/norms-repo/commits
List team norms repository commits
getTeamNormsCommits 5 params → 200400401403404500
GET
/api/v1/teams/{team_id}/norms-repo/commits/{sha}
Get team norms commit details
getTeamNormsCommit 2 params → 200400401403404500
GET
/api/v1/teams/{team_id}/norms-repo/compare
Compare team norms repository references
getTeamNormsCompare 3 params → 200400401403404500
GET
/api/v1/teams/{team_id}/context-repo-status
Check team context repository status
getTeamContextRepoStatus 1 param → 200400401403404500
GET
/api/v1/repos/{repo_id}/git/info
Get git checkout information
getRepoGitInfo 1 param → 200400401403404500

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is ErrorResponse (2 properties). Each schema is shown below with its type and property counts.

ErrorResponse
object
Standard error response returned by all endpoints on failure.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sageox-git-api-openapi.yml Raw ↑

Other APIs Sageox publishes across the network.

Sageox Admin API
Sageox AgentX API
Sageox API Keys API
Sageox Auth API
Sageox CLI API
Sageox Devices API
Sageox Firmware Admin API
Sageox Firmware OTA API
Sageox Guidance API
Sageox Health API
Sageox LLM API
Sageox Logs API
Where this information came from

This is an independent, third-party profile of Sageox Git API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.