Most personal-data products accumulate and never let go. Era exposes the corrections as first-class tools: confirm or reject what it inferred, defer a question it should not have asked, delete a fact it should not hold. Combined with scopes that separate banking reads from banking writes and both from brokerage, it is the most deliberate permission design here — which is the minimum for something holding both your accounts and its conclusions about them.
Era's endpoint. Eighty tools, and what stands out before any of them is the authorisation model: scopes are split by capability and by data domain — discovery, basic tools, writes, billing, resources, and banking, brokerage and social each with separate read and write.
- A knowledge layer with tools for confirming or rejecting an inference, deferring a question, and forgetting a fact
- Banking and brokerage access, read and write, each scoped separately
- Social data, also split read and write
- And the rest of the eighty across discovery, resources and billing
OAuth 2.1 with PKCE against forge.era.app, with dynamic client registration and refresh tokens. An API key path exists for developer tooling.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen