Skip to main content
If you run Attensira for several brands, each brand is a workspace in one org. Clients (at /clients, in the sidebar when the org has more than one workspace) is the org home: one card per workspace. There is no limit on client workspaces on any plan. No plan counts workspaces; an org’s prompt slots, responses and credits are shared across all of its workspaces.

​
What each card shows

  • Loop status: working, idle or blocked, with the reasons.
  • Shipped: work shipped in the last 7 days.
  • Waiting: items waiting on approval, with open tasks counted separately.
  • Visibility: “named in X of N answers” over the last 7 days, summed across engines.
There is no week-over-week comparison on the page.

​
Loop status on the card

For now the card’s status is a summary derived from the workspace’s automations: It will read loop health instead once that is wired into the card; loop health is the fuller answer.

​
Approving across workspaces

Select suggested changes on several cards and approve them in one action.
  • Select all covers only the changes each card shows, up to 5 per card.
  • A selection over 100 changes is sent in batches.
  • Each change is approved exactly as it would be in that workspace’s Work page: the same approval mode, change caps and checks apply.
  • Failures are reported per item, so one refused change does not hide the others that went through.

​
Agency today

Agency today (at /clients/agency) is a second view of the same org, built for triage. /clients is unchanged.
  • Clients: every workspace on one line, with its questions over the last 30 days counted on the Scoreboard scale: Recommended with a link (green, named and linked), Mentioned (amber, named with no link) and Not mentioned (red, not named). Questions no engine has answered yet are counted as Not checked yet. Each line also shows how many items need you in that workspace. A workspace whose questions or needs-you items could not be read says so instead of showing a zero.
  • Needs you: every workspace’s needs-you items in one list, not grouped by workspace and sorted by urgency. A change that ships on its own unless you stop it comes first, soonest deadline first. Everything else follows, oldest first. Each row names its workspace.
The list works from the keyboard: j and k move down and up, a approves a row that can be approved from a list, d declines (as “not now”), and e or Enter opens the row in its own workspace. ? shows the keys. Every approve and decline is the same per-item action as in that workspace’s own queue, sent to that workspace. There is no bulk action on this view. Each card has a Client link control that creates the client reviewer link for that workspace.

​
Monthly statements

To rebill your clients, Settings → Agency (/settings/agency) lists one statement per client workspace for a month, with Download CSV. The month defaults to the last complete one, and you can pick this month so far or any of the eleven before it. A month still in progress is marked Month to date; one that has ended is marked Full month. Each row shows the client’s usage, changes shipped, receipts verified, prompts tracked, and the amount to bill at the price you set for that client. A count that could not be read shows Not read rather than a zero, and a client with no price set shows No price set. Usage that belongs to no single workspace is shared across them in proportion to each client’s own usage (evenly when none had any), so the rows add up to the org’s usage for the month. Statements are read-only: nothing here charges anyone. The CSV is named statements-YYYY-MM.csv and carries no Attensira name, so you can pass it on as it is.

​
Over the API

These are dashboard routes (signed-in session):
  • GET /v1/org/statements?period=YYYY-MM: the month’s statements, one per workspace. Without period it is the last complete month. ?time_zone= (an IANA name) cuts a local month instead of the billing month (UTC).
  • GET /v1/org/statements.csv: the same statements as a CSV, with the same query.
  • GET and PUT /v1/org/statements/rates/{id}: the price for one client workspace, {flat_fee_cents, usage_percent, per_change_cents, per_receipt_cents, per_prompt_cents}. A zero leaves that line unbilled. Only an org admin can change it.
  • GET /v1/org/overview: the cards.
  • GET /v1/projects/{id}/scoreboard: one workspace’s Scoreboard, which Agency today reads once per workspace. With an API key it is GET /v1/scoreboard; over MCP it is analyze with view: "scoreboard".
  • POST /v1/org/inbox/approve with {"items": [{"project_id": "...", "item_id": "..."}]}, at most 100 items. It answers {approved, failed, results: [{project_id, item_id, ok, state?, error?}]}.