Core concepts

Workspaces are the security boundary

Every subscription, category, budget, reminder, and Agent/API token belongs to one workspace. Switching workspaces changes the records you are viewing and where new records are created. Shared workspaces use fixed owner, member, and viewer roles; access in one workspace does not imply access in another.

Money stays in its recorded currency

RecurLens stores the amount and ISO currency entered for each subscription. It calculates monthly and annual estimates, but it does not fetch exchange rates or combine unlike currencies into a synthetic total. USD, INR, and EUR therefore remain separate dashboard buckets.

Renewal dates drive attention

The next renewal date powers upcoming-renewal views and reminder windows. Contract end dates and notice periods can add review context. RecurLens surfaces deterministic review reasons, but never changes or cancels a subscription on your behalf.

Reviews are suggestions, not mutations

Duplicate and stale-looking records are prompts for a person to inspect the underlying subscription. Keeping or editing the record, marking it cancelled after cancelling with the vendor, or deleting it from RecurLens remains a human decision.

Agent/API reads are scoped and bounded

An external client uses a revocable token tied to one user and workspace. Each read operation has explicit limits, stable response envelopes, UTC timestamps, and request IDs. Tokens should receive only the scopes they need and should be revoked when no longer used.

Agent/API writes require hosted approval

Create and update tools prepare short-lived proposals. The same signed-in user to whom the originating token is bound reviews the proposed field changes in RecurLens and must still have workspace write access. Before execution, the server rechecks authorization, validation, quota, idempotency, and record version. The token itself cannot approve the proposal.

Continue with Getting started or the Agent/API quickstart.