Your first five minutes.

Begin with one appliance and one maintenance task. The ledger holds the facts; Muse helps you work with them.

1. Create and save your keys

Open Account, review the terms and create a ledger when beta enrollment is open. Save both keys in a password manager. The owner key manages access, export and deletion. The connector key reads and updates equipment and maintenance records. Neither is sent by email.

2. Connect with Muse

Where Muse offers custom connectors, add a raw API connector using this site’s OpenAPI definition. Use the API base URL https://home-ledger.bergapp.net and supply the connector key as a bearer credential in Muse’s secure credential field. Do not paste keys into conversation text. Never give Muse your owner key.

3. Record equipment

Try: “Add our HVAC system in the utility room. The filter is 20 × 25 × 1.” The model/notes are facts you provide; the service does not look up or verify manufacturers.

4. Choose a schedule

Try: “Schedule a filter change every three calendar months, first due June 15, 2026.” Use your manufacturer’s guidance. The system does not recommend safe intervals.

5. Complete and retrieve

Try: “Record that I changed the filter on June 15, 2026.” Use a date on or before today. The next due date becomes September 15, 2026. Ask “When did I last change it?” to retrieve the stored service history.

How dates work

Dates are calendar dates, never device timezone timestamps. All date inputs use YYYY-MM-DD. Recurrence starts from the actual completion date. January 31 plus one calendar month becomes February 28 (February 29 in leap years). A later completion on February 28 makes the next due date March 28. Day intervals count whole days, including across daylight-saving changes. Future-completion checks allow the latest current civil date worldwide (UTC+14), so users ahead of UTC can record today.

A due query includes overdue active schedules unless a start date is explicitly supplied. Archiving hides a schedule from due queries while preserving history. Restoring keeps its previous due date, so it may immediately appear overdue. There are no automatic reminders.

API details

All connector operations are documented in OpenAPI. Record mutations require a unique Idempotency-Key; retry identical requests with the same key for 30 days. Before completing or archiving a task, read its current version and send expected_version. A conflict means the record changed: retrieve it and ask the user if the intended action is still needed.

API keys expire: connector keys after 90 days, owner keys after 365 days. Rotate in Account before expiry. Each account is limited to 60 requests/minute, 1,000/day, 50 equipment records, 100 schedules and 5,000 service entries.

Corrections and exports

This beta preserves completed service entries without editing. If a record is wrong, pause its schedule and contact support with the request ID, not your key. You may create a corrected schedule. JSON exports are available in Account. Import and multi-user sharing are not included.

For reviewers and developers

Start with a new isolated account. Register equipment, schedule work, read due items, complete one task, retry it with the same key, and retrieve its history. Confirm a second account cannot access the first account’s records. Use synthetic data only. Account management uses an owner key and is intentionally outside the connector specification.