Skip to main content

Changelog

What's changed on the Era Developer Platform, including the Era API, newest first.

  1. New

    New `holder` parameter on Knowledge record endpoints and MCP tools lets callers address a group's records

    The seven Knowledge record REST endpoints and five Knowledge MCP record tools now accept an optional `holder` naming a group the caller belongs to; omitting it preserves the previous behaviour byte-for-byte, except that the undeclared-member refusal now lists `holder` among declared members.

    MCP tools (`knowledge__remember`, `knowledge__forget`, `knowledge__confirm_or_reject_inference`, `knowledge__recall_history`, `knowledge__get_financial_context_and_overview`) accept `holder: {kind: "group", group_id}`. REST writes (`POST /api/knowledge/assertions`, `POST /api/knowledge/assertions/compound`, `POST /api/knowledge/assertions/{slug}/confirm`, `DELETE /api/knowledge/assertions/{slug}`) accept `holder: {kind: "group", groupId}` in the body. REST reads (`GET /api/knowledge/assertions`, `GET /api/knowledge/assertions/{slug}/history`, `GET /api/knowledge/context`) accept `holderKind` and `holderGroupId` as query parameters, which must be sent together. Writes require Contributor; reads require Viewer. A Viewer's write is refused with `HolderNotWritable` (MCP `ACCESS_DENIED`, REST `403`). A group the store does not admit — a stranger, former member, delegated session, or deleted space — is answered identically to a group that does not exist: a 404 listing no record on writes, an empty list on reads. On `GET /api/knowledge/context`, `holder` scopes only the assertions and goals; profile, accounts, totals, months, categories, home currency, personalization, and questions remain the caller's own. A `group_id` that names no group is refused once, before any handler call: MCP returns one `VALIDATION_ERROR` naming `holder.group_id`; REST returns `400` naming `holder.groupId` (body) or `holderGroupId` (query). Sending only one of `holderKind`/`holderGroupId` is a `400` naming the one left out. The regenerated OpenAPI spec and orval client are published; the five MCP schema snapshots gain the optional `holder` and updated descriptions.

  2. New

    The Era API is in public preview, with docs at /docs/era-api

    Read and manage your Era accounts, transactions, categories, tags and rules over REST with an API key. The reference and a public OpenAPI document are published.

    The reference at /docs/era-api covers accounts and balances, transactions, categories, tags and automation rules, including previewing, enabling and disabling a rule. Reads need the banking:read scope and writes need banking:write. A write changes only what Era keeps: it can't move money, and nothing at your bank changes. The API serves its own OpenAPI document for the public operations at /api/openapi/public.json, with no key required, so you can generate a client from the contract. The API is in public preview, so an endpoint, a field or how a call behaves can still change, and this changelog records what does. Create a key from the API keys page in your Era account.

Era Financial Advisors LLC is an SEC-registered investment adviser (CRD #334404). Registration does not imply a certain level of skill or training. Investment advisory services are discretionary and AI-assisted; they are not a substitute for personalized financial advice. Brokerage and custodial services are provided by Alpaca Securities LLC, a separate entity and member of FINRA/SIPC. Era Thesis and Era Agency accounts are currently available to US residents only; Era Context connects accounts across the US, the UK, Canada, France, Germany, Spain, and 40+ countries in all. Nothing on this website is an offer or solicitation to buy or sell securities. Past performance does not guarantee future results. Please review our Form ADV and Form CRS before investing.

Download on the App StoreGet it on Google Play
era© 2026 Tinwell Labs Inc. DBA Era