Agent access.

Branner keeps your household records and exposes them through an HTTP API. Connect Hermes, OpenClaw, Claude, Codex, or any assistant that can make authenticated requests.

Connect in three steps

  1. Sign in, open Connections, and create an agent credential.
  2. Choose read-only access or allow record creation and updates. Store the key in your agent’s secret storage.
  3. Give your agent the instructions below. It can discover your property ID from the bootstrap response.
Use Branner as my household source of truth.
Base URL: this site's origin + /api/v1
Authorization: Bearer <my Branner key>

GET /bootstrap — household, properties, records, documents
GET /search?q=filter — search records and document text
GET /records/:id — read a record and its current version
GET /documents/:id/download — retrieve an original file
POST /records — add a record
PATCH /records/:id — update, including the current version
POST /records/:id/complete — complete maintenance, with version
POST /documents — upload multipart file + propertyId (+ recordId)
PATCH /documents/:id — link recordId or add extracted text
POST /documents/:id/analyze — AI reading, when configured
POST /documents/:id/accept — accept a suggestionId
GET /export — improvement ledger CSV

Do not infer warranty coverage, dates, or tax savings.
Preserve sources and distinguish uncertain suggestions.
Do not duplicate invoices and their payment proofs.
On HTTP 409, reread the record before editing again.
Household access comes from the key, never a user-supplied ID.
Do not share records or contact others without my approval.

Add a household item

POST /api/v1/records
Authorization: Bearer <key>
Content-Type: application/json

{
  "propertyId": "<from bootstrap>",
  "kind": "item",
  "title": "Kitchen dishwasher",
  "location": "Kitchen",
  "category": "Appliance",
  "notes": "Model transcribed from the appliance label.",
  "source": "owner-provided label photo",
  "data": { "brand": "Bosch", "model": "<verified model>" }
}

What records can contain

Types: item, contact, maintenance, improvement, and note. Common fields include title, category, location, notes, dueDate (YYYY-MM-DD), source, sourceDocumentId, and data.

Improvement data includes costCents, adjustmentCents, costType (actual or quote), classification (review, potential, or repair), contractor, date, and stillPresent. Use integer cents. Quotes do not count as spending. Maintenance data can include repeatDays; completion records the actor and date, then calculates the next occurrence from completion.

Access is explicit

Each credential belongs to one household. Read-only keys cannot change records. Agent keys cannot create other credentials or sharing links. Revoke a connection in the web app at any time. Browser tools, when supported, expose household search and note creation through the same authorized API.

Telegram deployment

Branner includes a webhook receiver with sender linking and a polling runner for local or private-site testing. Bot setup requires a Telegram bot token. Private Sites access can prevent external agents and Telegram webhooks from reaching the app, so external access needs a suitable deployment or a supported platform access credential. See the repository README for setup and tested limits.

Open your home