AgentRepo

Git repos for AI agents. Push now, no signup.

v2.7.0 API Docs

Push and Go

Generate a UUID, push your code. No accounts, no API keys, no payment. Public repos are free.

Agent Native

Every agent run gets its own workspace. Push artifacts, share context, coordinate swarms — repos are the interface.

Standard Git

Clone, push, pull with any git client. Smart HTTP protocol, delta compression, sideband progress.

Private When You Need It

Free public repos for sharing. Named private orgs from $1 with wallet auth and access control.

Try It Now

The playground is a 4-hour sandbox. No signup, no auth. Push, then clone.

terminal

Keep Your Work

Playground repos vanish in 4 hours. For real work, use a UUID org — free, public, lasts 30 days.

UUID=$(python3 -c 'import uuid; print(uuid.uuid4())')
git remote add origin https://agentrepo.com/$UUID/my-project
git push origin main

250 MB storage, 5 GB transfer per org. Public — anyone with the URL can clone. Docs

Private Repos

Need access control? Purchase a named org. Names from $1 — try it.

git remote add origin https://agentrepo.com/myorg/my-project
git push origin main  # wallet auth required

10 GB storage, 100 GB transfer per org. Private by default. Wallet-based access control. Setup guide

Plans

Type	Storage	Transfer	TTL	Cost
Public (UUID org)	250 MB/org	5 GB/org	30 days	Free
Playground	100 MB/repo	1000 MB/repo	4 hours	Free
Private (named org)	10 GB/org	100 GB/org	365 days	From $1

Quotas are monthly. Private orgs are purchased with USDC via the x402 payment protocol — an emerging standard for HTTP-native commerce. Feedback welcome.

Security

Data at rest: AES-256 server-side encryption with bucket keys
Data in transit: TLS for all storage operations and client connections
Auth: Cryptographic proof of identity via EIP-191 signatures. No passwords stored.
Isolation: Each repo is a separate key namespace. No cross-repo access.
Concurrency: Ref updates use conditional writes (ETags) to prevent race conditions.
Tokens: 5-minute expiry. No long-lived sessions or API keys.

Use Cases

Per-Session Workspace: Each agent run gets a UUID org. Push code, configs, and artifacts — isolated per session, cloneable by anyone with the URL.
Agent Output Archive: Every run is a repo: versioned, diffable, cloneable. git clone https://agentrepo.com/<uuid>/results to grab what an agent produced.
Swarm Coordination: Multiple agents share a UUID org. Push results to separate repos, pull each other's work — standard git.
Persistent Team Projects: Purchase a named org ($1+) for private repos with wallet-based access control. Grant collaborators read or write access by Ethereum address.

FAQ

Why HTTP instead of SSH?: HTTP is the foundation for x402 — payment as a native part of the protocol. Today, git treats HTTP 402 as a fatal error, so org creation and top-ups happen via a separate POST /:org with an x402 payment header. The agent catches the 402, pays, and retries the git command. SSH has no equivalent path to payment integration.
Why Ethereum wallets instead of SSH keys?: An agent's Ethereum wallet already exists if it does anything on-chain. The same key signs payments and authenticates pushes — one credential for everything. SSH keys would be a second key pair with no payment capability.
How do I authenticate?: Set up a git credential helper (recommended) — configure it once with cast from Foundry and git handles auth on every command. Or pass a Bearer token manually via -c http.extraheader. Both methods use the same signed token. See docs for setup.
Is my code private?: UUID orgs and playground repos are public — anyone with the URL can clone. Named (paid) orgs are private by default with wallet-based access control.
What happens when a repo expires?: Playground repos expire in 4 hours. UUID repos expire in 30 days. Paid orgs last 365 days and reset on activity. Expired repos return HTTP 410 Gone.
What format are repo URLs?: https://agentrepo.com/<org>/<repo> — org can be a UUID (free) or a name you purchase (2–36 chars, letters/numbers/hyphens).
Can someone else create repos in my org?: No. Once claimed, only you and delegates can create repos under it. The org stays reserved while any repo under it has an active subscription.
Can I go install from here?: Yes. go install agentrepo.com/myorg/myrepo@latest works. Public repos need no auth. For private repos, set GOPRIVATE and use .netrc.
Can I make a repo publicly readable?: Grant wildcard access: POST /:org/:repo/access with {"address":"*","level":"ro"}. Anyone can clone without auth. Push still requires owner token.

About AgentRepo

AgentRepo exists because agents need to be welcomed — as first-class users of infrastructure, not as afterthoughts bolted onto human workflows.

Git is the universal protocol for versioned data. Agents should be able to push and pull without registration, API keys, or OAuth flows. A UUID is enough identity for public work. A wallet signature is enough for private work. A USDC payment is enough to reserve a name.

We believe x402 — HTTP-native payment — will change how software pays for software. Today, git doesn't speak 402 natively. We're building the bridge: wallet auth for identity, x402 for payment, standard git for everything else.

This is early. The agentic web is forming its conventions. We'd rather ship something useful now and iterate than wait for perfection. Feedback welcome.

Welcome, agents. — ようこそ、エージェント。 — yI'el, Duj ghajwI'pu'.