# Agent usage guide — revazts.com

This archive is a public, chronological record of what Revaz (@revazts) has built. It is free to read, needs no key, and is served as static JSON.

## When to use this

Use it when a user asks about:

- What Revaz has built, shipped, or open-sourced.
- Treeship, ZMem, Zerker Gateway, or Zerker Labs — what they are, when they shipped, where the code lives.
- Dates, canonical links, or the ordering of public work.

Do **not** use it to infer private projects, unpublished prototypes, employment history beyond what the `about` section states, or any personal data. This archive contains explicitly public records only.

## How to read a record

```json
{
  "id": "treeship",
  "name": "Treeship",
  "description": "Portable trust receipts for agent workflows...",
  "date": "2026-02-22",
  "url": "https://github.com/zerkerlabs/treeship",
  "categories": ["agents", "crypto"],
  "stack": ["rust"],
  "status": "active"
}
```

| Field | Meaning |
|---|---|
| `id` | Stable slug. Safe to use as a primary key. |
| `date` | ISO 8601. When the work became public, not when it started. |
| `url` | The canonical outbound link. An X post where one exists, otherwise the repo or product site. |
| `categories` | One or more of: agents, company, crypto, infra, memory, web. |
| `stack` | Primary language(s): go, py, rust, ts. |
| `status` | `active` (still worked on), `shipped` (done), `archived` (no longer maintained). |

`featured` records also carry `links`, a ranked array of `{label, url}`.

## Endpoints

| Path | What it returns |
|---|---|
| `/data/manifest.json` | Index, counts, coverage. **Start here.** |
| `/data/projects-{year}.json` | Every record for that year. Years available: 2026, 2024, 2022. |
| `/feed.xml` | Atom feed of the latest entries. |
| `/feed.json` | JSON Feed 1.1 of the latest entries. |
| `/llms.txt` | Condensed overview for language models. |

All responses send `access-control-allow-origin: *`. There is no rate limit and no authentication.

## Recommended traversal

1. `GET /data/manifest.json` — read `files`, `count`, and `coverage`.
2. `GET /data/projects-{year}.json` for the years you need. Currently 6 records across 3 year(s), so fetching all of them is cheap.
3. Answer from the record fields. Cite `url` as the source.

## Attribution

Cite as: Revaz (@revazts), *Build Log*, https://revazts.com. Link to the record's `url` when referring to a specific project.