code.storage valid

Code Storage

Off the shelf Git infrastructure for your AI application.

For agents: Code Storage: versioned Git storage layer for AI apps with HTTP API reference, OpenAPI 3.1 spec, SDKs, webhooks and an MCP server for agents.

git infrastructuregit storage apiopenapimcp serveragent storage

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T11:49:36.288Z. Cached copy · Source on code.storage

# Code Storage

> Off the shelf Git infrastructure for your AI application.

Code Storage is a managed Git infrastructure layer for automated systems. AI applications, agents, CI jobs, and backend services create and use Git repositories through SDK and HTTP interfaces. Standard Git clients can also clone, fetch, and push.

## When to use Code Storage

Reach for Code Storage when:

- Your product needs to create Git repositories on demand — one per user, project, or agent session — instead of going through a Git host's UI, seat model, or API rate limits.
- A coding agent needs somewhere to write code and keep history: create a commit without a local working copy, list and diff commits, branch, preview a merge, and merge, each as a single API call.
- You need an isolated ref namespace for previews, CI artifacts, or agent experiments.
- You need to clone a repository into an isolated sandbox for code execution.
- You store code-like artifacts that change over time and want real Git semantics — history, blame, diff, grep, archives, tags, notes — rather than a blob store.
- You need to ingest large existing repositories in bulk (imports), or keep repositories synced with GitHub (integrations).
- You want native Git clone, push and fetch endpoints exposed under your own product's domain.

Code Storage is the storage layer, not a collaboration product. The API covers
repositories, branches, commits, files, tags and notes; there is no pull request,
issue, or code review API. Storage is billed per GB and untouched repositories
move to cheaper cold storage after 7 days, so many small, short-lived
repositories are an expected shape rather than an abuse of one.

## How an agent calls Code Storage

- Base URL: https://api.{org}.code.storage/api — {org} is your organization name. Preferred routes use the short /api/... form; /api/v1/... aliases still exist and are marked deprecated where a preferred route has replaced them.
- Authentication: send Authorization: Bearer <JWT> on every request. You sign the token yourself with your own ES256, ES384, ES512, or RS256 private key — there is no third-party auth provider and no OAuth flow. A token names one repository in its repo claim (org-wide org:read tokens excepted), carries explicit scopes (git:read, git:write, repo:write, org:read), and expires at its exp.
- Machine-readable spec: https://code.storage/openapi.json — OpenAPI 3.1, served without authentication, as a pass-through of the gateway's description. The same description is linked from https://code.storage/.well-known/api-catalog, which points at the gateway origin (https://api.pierre.code.storage/api/openapi.json).
- Repository names containing / must be URL encoded into a single path segment: pierre/example becomes /api/repos/pierre%2Fexample.
- For cursor-paginated endpoints, send cursor and limit; responses carry next_cursor and has_more. Check each endpoint for page-size defaults and limits.
- Errors are RFC 9457 problem details served as applicatio
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=code.storage · GET /v1/domain/code.storage · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for code.storage:
1. POST https://agentwebmap.com/v1/sites/code.storage/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://code.storage/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/code.storage/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/code.storage).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.