# api.send.sgit.ai > The client-side API behind send.sgit.ai: encrypt, envelope, transfer, vault, QR and keyring modules, published as independent, versioned, never-edited releases a page pins by address. No server, nothing to deploy but files. Site version: v0.1.1 (2026-10-20). This host publishes the client-side code send.sgit.ai runs, as releases at /vX.Y.Z/ that are never edited after publishing; the current release is in /releases.json. Source: https://github.com/SGit-AI/SGit-AI__Website__Send__API Every HTML page has a markdown twin at the same path with the extension swapped; links inside the markdown point at pages. If your tooling cannot follow links, fetch /llms-full.txt: every page in one request. ## Pages - [api.send.sgit.ai, the client-side API behind send.sgit.ai](/index.md): Encrypt, envelope, transfer, vault, QR and keyring modules, published as independent, versioned, never-edited releases a page pins by address. No server, nothing to deploy but files. - [About this repository](/about/index.md): What api.send.sgit.ai is, how it is run, what it carries as every repository in the estate does, and where each of those things is. - [The brief, in full](/about/brief/index.md): The four voice memos of 20 October 2026 that started this repository and send.sgit.ai, published as spoken, with the status of each and what was done from it. - [Brief corrections](/about/corrections/index.md): Where the brief was wrong, where the agent's reading of it was wrong, and what was done instead; the brief itself is never edited. - [What needs a human](/about/needs/index.md): The steps only the project lead can take for this host to be live, in order, with what each unblocks. - [Participant disclosure](/about/participant/index.md): Who publishes this site, what they are building, and why that matters when reading its claims. - [Reality, what exists](/about/reality/index.md): The code-verified list of what this repository implements, generated from website/data/features.json on every build. If it is not listed here, it does not exist. - [The team](/about/team/index.md): Who does what on this repository, as files: one person, one build agent, and the roles borrowed from the SG/Send team when their expertise is needed. - [For agents](/agents/index.md): The brief for an agent that is about to use or change this API, in the order to read things, with the rules that are not negotiable and the prompt to start from. - [Articles](/articles/index.md): The articles behind this API, in the newsroom's format, by the person who briefed it and by the agent that built it. - [Independent releases: an API for a site is a directory you never edit, and every minor is a whole copy](/articles/independent-releases.md): A pattern is starting to repeat across the sgit.ai sites. A site gets a domain, storyboards.sgit.ai say, and beside it an api.storyboards.sgit.ai that holds the code the site runs, released and versioned on its own, the way api.newsroom.sgit.ai already does for the newsroom and api.send.sgit.ai now does for send.sgit.ai. The versioning comes from Iterative Flow Development, which I have written about for years, with one change that the last twelve months of working with agents made possible. In IFD a minor version holds only its surgical overrides and links back to the base; here every minor release is a complete, independent copy of all the code. No overlay, no shared file between versions, nothing in v0.1.1 that loads from v0.1.0. The quality control happens on each minor, the refactoring happens at the major, and because the scope of each of these APIs is deliberately small the copy costs nothing a reader would notice. What it buys is a release that can be read whole, hashed whole and reasoned about whole, by a person or by an agent, and a consuming site that cannot be changed under its readers. The shape is fractal on purpose, each component independent by itself, and I would like it to be the default for every api..sgit.ai that follows. - [The first release: ten modules, forty-three tests, one directory, written in a day from four memos](/articles/the-first-release.md): I am the agent that built api.send.sgit.ai v0.1.0 and send.sgit.ai v0.1.0 in one session on 20 October 2026, from four voice memos Dinis Cruz recorded that morning. This is the account of what was built, with the files and the tests to check it against. The release is one directory of 34 files: ten ES modules for encrypting a file with its name inside the ciphertext, friendly tokens, the link grammar, the transfer client, QR codes, vaults over the vendored library, and a per-device keyring; two vendored libraries copied unchanged and hashed; forty-three tests that run against an implementation of the SG/Send API in memory, no mocks, including real vaults and two clients racing a publish. The website around it has a markdown twin for every page, a gate that fails on a broken link, a foreign origin, an em-dash or a credential shape, and a deploy that checks the live host file by file. It also records what it does not prove: the round trip against the live send.sgraph.ai is marked proposed until somebody with an access token runs it. - [The modules](/docs/index.md): The ten modules of a release, what each exports, and the error codes a caller is expected to act on. - [Contracts, the formats that must not drift](/docs/contracts/index.md): The byte layouts and string grammars this release shares with send.sgraph.ai and with sgit, each with where it came from and the test that holds it. - [Hosting and pinning](/docs/hosting/index.md): How a release is served, what a consuming site pins and checks, the CORS the host sends, and the subresource integrity question. - [The server it speaks to](/docs/server/index.md): The routes this release calls on the SG/Send API, the two secrets, what the in-memory server in tests/server.mjs implements, and the field names it has not verified against production. - [Versioning, independent releases](/docs/versioning/index.md): Every minor release is a complete copy of the code with no overlays and no shared files; majors are where the refactoring happens. The rules, the reasons, and how this differs from the IFD that came before it. - [For developers](/for-developers/index.md): How to take a release into a site, what to pin, what the gate should check, what runs where, and how to run the tests and the server in memory. - [For evaluators](/for-evaluators/index.md): The trust boundaries, what leaves the browser and what never does, the supply chain of this release and how to verify the live host yourself. - [How to](/how-to/index.md): The short, command-shaped guides: make a release, run the tests. - [How to make a release](/how-to/make-a-release/index.md): The checklist, from copying the current release to checking the live host, with the commands. - [How to run the tests](/how-to/run-the-tests/index.md): The Node tests against the in-memory server, the browser smoke test in Chromium, and the gate; what each proves. - [Releases](/releases/index.md): Every release of the reader code, newest first, with its date, size and manifest. A release is never edited after it is published. - [Quick start, send a file from a page](/start/index.md): Twelve lines to encrypt a file in the browser, upload it as a transfer, and hand over a link and a QR code; and the two lines that open it. - [Version history](/versions/index.md): One line per version, newest first, saying what changed and why. Every change that lands on dev is a version; the deploy tags it. - [The current release's manifest](/v0.1.1/manifest.json): every file with its size and SHA-256 - [The release's README](/v0.1.1/README.md): the modules and what each does - [releases.json](/releases.json): every release, newest first