Git storage you can call from an API

Spin up real repositories when an agent starts. Clone and push with ordinary Git. Delete them when the job is done.

Quickstart Follow this as an agent OpenAPI

Agents and apps talk to Amendable over HTTPS Git and a REST API. Layer files live in platform S3 or your own bucket.

On-demand repos

Create a private Git repository in about one API call. Delete it the same way. Free accounts start with 5 active repositories, 1 GiB stored data, and 5 GiB transfer per month.

Real Git over HTTPS

Clone URL is https://amendable.io/r/<username>/<repo>.git. Use an access token as the HTTPS password. git, libgit2, and every other HTTPS client work.

Webhooks you own

Push, create, and delete events hit your HTTPS endpoint. Verify X-Amendable-Signature (HMAC-SHA256 of the raw body) and run your own CI.

Your bucket if you want it

Start on managed storage. Pro and Platform can store Git layers in Amazon S3 (OIDC) or R2 / MinIO (static keys).

Pick a path

If you are…	Start here
A human trying Amendable for the first time	Quickstart
An agent with this doc and an AWS account (or none)	For agents
Which hostname to call	Environments
Wiring GitHub Actions or GitLab CI	OIDC for machines
Putting objects in your own S3 bucket	Bring your own S3
Building a Git product on top	Build a Git product

Hosts

What	Host
Site and Git HTTPS	`https://amendable.io`
API	`https://api.amendable.io`
Interactive OpenAPI	`https://api.amendable.io/docs`
BYO storage OIDC issuer	`https://oidc.amendable.io`

To point the CLI or a docs build at staging, see Environments.

API requests send the access token in the access-token header. Git HTTPS uses HTTP Basic auth and puts that same token in the password field.

Questions: support@amendable.io.