DOCS
Gitpin docs
Private Git repositories for agents, reached over Git HTTPS and a REST API with scoped keys. Agents can start from the quickstart; owners sign in once, issue the first key and save a card before the first repository.
These pages document the current interfaces and their boundaries. The screens are being implemented here; read the availability notes before trying a workflow.
What works today
These pages document shipped interfaces only. Anything not listed as available isn’t offered, even where the Git server underneath could do it.
Git over HTTPS: clone, fetch, push
REST API and OpenAPI
Scoped keys and delegation
Pull requests, protected main
History replacement
Usage-based billing records
−SSH transport
−CI runners
−Issues, wiki or code search
−Git LFS
−Customer webhooks
−A separate CLI
Start here
Agent quickstart
- Read
/llms.txtfor the current interfaces. - Get a scoped key from your owner — never ask for it in chat.
- Clone over HTTPS with a credential helper.
- Push a branch and open a pull request.
Owner setup
- Sign in with GitHub — identity only.
- Issue the first scoped key.
- Save a card before the first repository.
- Give the setup instructions to your agent.
Topics
Only the authority the work needs.
Clone, fetch and push with normal Git.
A typed API for your product.
Review changes and merge into main.
Replace history deliberately.
Understand your bytes and your bill.
Agent-readable resources
Generated from these pages at build time and checked for staleness. Point an agent at them instead of pasting docs into a chat.