# Cloudgeni Documentation

## Docs

- [Authentication](https://docs.cloudgeni.ai/api-reference/authentication.md): Authenticate programmatic Cloudgeni API calls with the organization-scoped API key header the backend actually expects.
- [API Introduction](https://docs.cloudgeni.ai/api-reference/introduction.md): Understand the small set of Cloudgeni API concepts you need before calling scan, repository, or cloud endpoints from automation.
- [Scanning API](https://docs.cloudgeni.ai/api-reference/scanning-api.md): Trigger repository and cloud scans with the endpoint shapes that match the current routes in node-server.
- [CLI Overview](https://docs.cloudgeni.ai/cli/overview.md): Use the Cloudgeni CLI to start, resume, and automate agent sessions from a terminal.
- [CIS Benchmarks](https://docs.cloudgeni.ai/compliance/cis-benchmarks.md): Use the CIS benchmark view where Cloudgeni actively exposes it, and read the coverage in the context of the provider-specific framework model.
- [ISO 27001](https://docs.cloudgeni.ai/compliance/iso27001-compliance.md): Read Cloudgeni’s ISO 27001:2022 mappings as an operational view of cloud findings, not as a substitute for your broader ISMS process.
- [SOC 2](https://docs.cloudgeni.ai/compliance/soc2-compliance.md): Use Cloudgeni’s SOC 2 mappings to organize cloud findings by control intent and prioritize the remediation work that actually matters.
- [FAQ](https://docs.cloudgeni.ai/faq.md): Short answers to the product questions that come up most often when teams are getting Cloudgeni into a usable state.
- [AI DevOps](https://docs.cloudgeni.ai/features/ai-devops.md): Use agent sessions to plan, draft, continue, and review infrastructure changes without leaving the Git-based delivery path.
- [Audit Logging](https://docs.cloudgeni.ai/features/audit-logging.md): Export and query audit logs for your organization.
- [Cloud Compliance](https://docs.cloudgeni.ai/features/cloud-compliance.md): Run framework-based cloud scans against connected accounts and review the results by requirement, severity, and remediation priority.
- [Cloud Monitors](https://docs.cloudgeni.ai/features/cloud-monitors.md): Review native cloud security findings from AWS Security Hub and Azure Defender without forcing them into a repository-first scanning model.
- [Cloud Resource Import](https://docs.cloudgeni.ai/features/cloud-resource-import.md): Select live cloud resources and hand them into the agent-session workflow to generate repository changes instead of rebuilding them manually.
- [Compliance Frameworks](https://docs.cloudgeni.ai/features/compliance-frameworks.md): Understand which cloud providers are mapped to which active frameworks in the current product and how those mappings should be interpreted.
- [Configuration Drift](https://docs.cloudgeni.ai/features/configuration-drift.md): Track where live infrastructure diverges from repository intent, then work those drifts through scans, triage, and repository-backed remediation.
- [Custom Policies](https://docs.cloudgeni.ai/features/custom-policies.md): Store organization-specific guidance as versioned policy definitions that Cloudgeni can use as durable context for security and infrastructure work.
- [Pull Request Reviews](https://docs.cloudgeni.ai/features/pull-request-reviews.md): Enable repository-level AI reviews for incoming pull requests and track them through the PR review and agent-session surfaces.
- [Static Analysis](https://docs.cloudgeni.ai/features/static-analysis.md): Run Checkov-backed repository scans, review file-level findings, and use them as the first signal before you start editing infrastructure.
- [Connect Cloud Accounts](https://docs.cloudgeni.ai/getting-started/connect-cloud-accounts.md): Choose the cloud connection method that matches the current UI and the least privilege model the product actually uses.
- [Connect a Git Provider](https://docs.cloudgeni.ai/getting-started/connect-git-provider.md): Set up GitHub, GitLab, or Azure DevOps the way the current app expects, then enable repository-level workflows from there.
- [Getting Started Overview](https://docs.cloudgeni.ai/getting-started/overview.md): Understand the few product surfaces that matter first: integrations, scans, findings, and agent sessions.
- [Cloudgeni Docs](https://docs.cloudgeni.ai/index.md): Use the published product docs to connect Git and cloud, run scans, review findings, and work through agent-backed infrastructure changes.
- [Azure Pipelines](https://docs.cloudgeni.ai/integrations/ci-cd/azure-pipelines.md): Use Azure Pipelines as a thin automation layer over the Cloudgeni API rather than expecting a separate managed pipeline integration.
- [GitHub Actions](https://docs.cloudgeni.ai/integrations/ci-cd/github-actions.md): Trigger Cloudgeni scans from GitHub Actions by calling the API directly instead of depending on a separate managed GitHub Action.
- [GitLab CI](https://docs.cloudgeni.ai/integrations/ci-cd/gitlab-ci.md): Trigger Cloudgeni scans from GitLab CI with direct API calls so the pipeline matches the current public scan surface.
- [Jenkins](https://docs.cloudgeni.ai/integrations/ci-cd/jenkins.md): Use a Jenkins shell step to call the Cloudgeni scan API directly and keep your pipeline integration explicit.
- [Azure DevOps Setup](https://docs.cloudgeni.ai/integrations/git-providers/azure-devops-setup.md): Connect Azure DevOps through the current OAuth flow, complete any follow-up confirmation, and verify repository access before enabling repository features.
- [GitHub Setup](https://docs.cloudgeni.ai/integrations/git-providers/github-setup.md): Connect GitHub through the product’s current app-install flow, verify repository sync, and then enable repository-level workflows.
- [GitLab Setup](https://docs.cloudgeni.ai/integrations/git-providers/gitlab-setup.md): Connect GitLab through OAuth, finish the required follow-up selection step, and verify project access before you rely on repository workflows.
- [Quickstart](https://docs.cloudgeni.ai/quickstart.md): Set up Cloudgeni with one Git provider and one cloud account, then run a workflow that matches the product as it exists today.
- [AWS Setup](https://docs.cloudgeni.ai/setup/aws-security-hub-setup.md): Connect an AWS account with read-only credentials, sync the account, and then use Cloud Monitors or Cloud Compliance from there.
- [Azure Setup](https://docs.cloudgeni.ai/setup/azure-defender-setup.md): Use Azure Quick Connect, verify the integration becomes active, and then use Azure-backed cloud monitoring or compliance views.
- [GCP Setup](https://docs.cloudgeni.ai/setup/gcp-service-account-setup.md): Prefer the keyless impersonation path for GCP, fall back to a service account key only when you have to, and verify inventory access before scanning.
- [OCI Setup](https://docs.cloudgeni.ai/setup/oci-setup.md): Connect OCI with a dedicated read-only user and API key, then use the account for inventory and benchmark-oriented review.
- [Common Issues](https://docs.cloudgeni.ai/troubleshooting/common-issues.md): Work through the most common setup and workflow problems without guessing where the failure actually is.
- [Connection Issues](https://docs.cloudgeni.ai/troubleshooting/connection-issues.md): Fix Git and cloud onboarding problems by checking the exact scope, mode, and follow-up step the current app really expects.

## OpenAPI Specs

- [openapi](https://docs.cloudgeni.ai/api-reference/openapi.json)