> ## Documentation Index
> Fetch the complete documentation index at: https://atlas.rebuildingus.org/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace integration activity

> What workspace admins can see about REST API and MCP adoption, and what Atlas keeps private.

## Overview

Workspace integration activity answers a simple admin question: **is this
workspace using Atlas through external access paths?**

It is for workspace owners, administrators, and customer-success teams who need to
understand adoption of REST API and MCP access. It is not a developer trace,
prompt log, security audit stream, or surveillance surface.

Use it to answer:

* Is the workspace using API or MCP access at all?
* Which surface is active: REST API, MCP, or both?
* When was the latest successful integration call?
* Which public route or MCP resource is most active?
* Is there enough usage to justify rollout, training, or renewal follow-up?

## What admins can see

Workspace admins can see:

* Total successful integration calls
* REST API calls
* MCP calls
* Top routes or resources
* Last-seen timestamps

These metrics are aggregated at the workspace level. They show adoption and
recency, not individual research behavior.

## What stays private

Atlas does not expose:

* Request bodies
* Prompt text
* Raw metadata JSON
* IP addresses
* Session replay
* Private workspace notes

That boundary lets Atlas show whether integrations are useful without exposing
the content of civic research or private workspace activity.

## What counts as usage

Atlas counts successful integration calls only.

| Surface  | What counts                                                                                               |
| -------- | --------------------------------------------------------------------------------------------------------- |
| REST API | Successful external API calls authorized for the workspace                                                |
| MCP      | Successful MCP transport requests after Atlas verifies account, workspace, permission, and package access |

Failed authorization attempts, rejected requests, browser page views, and normal
public browsing do not count as API or MCP activity.

## Last seen and top resources

`last_seen_at` is the newest successful API or MCP integration event for the
workspace.

`top_resources` shows the most-used routes or MCP resources by count. It is a
coarse adoption signal, not a transcript of what users asked or saw.

## Access requirements

Admins need access to the workspace to view its integration summary.

Free accounts can browse public Atlas data, but MCP and higher-volume API
workflows require a paid package. See [Plans & pricing](/docs/account/pricing).

## API reference

The same workspace activity summary is available through:

```http theme={null}
GET /api/orgs/{org_id}/usage-summary/integrations
```

Use the [generated OpenAPI reference](/docs/api/reference) for response fields and
authentication details.

## Related

* [Scopes and permissions](/docs/mcp/scopes)
* [Plans and pricing](/docs/account/pricing)
* [MCP troubleshooting](/docs/mcp/troubleshooting)