Skip to content

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.
Agents and apps talk to Amendable over HTTPS Git and a REST API. Layer files live in platform S3 or your own bucket. Amendable notifies your HTTPS webhook endpoint when refs change.

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 can store Git layers in an Amazon S3 bucket you own (OIDC). R2, MinIO, and other stores are coming soon.

Auditable history

Each push is an immutable layer. Force-push can rewrite Git history. Earlier layers stay, so you can still see who changed the repo and how.

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
An agent that needs one file, not a clone Fetch files
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

Questions: support@amendable.io.