Agent Access lets an external agent report back to a Filepad workspace — pushing activity events, raising signals, and reading its mailbox — without becoming the main Filepad runtime.
How it works
- A workspace admin creates an Agent Access key in the workspace.
- The key is granted narrow scopes such as
events.writeorsignals:write. - The external agent authenticates every
/agent-api/v1request with an OAuth bearer token. - Filepad validates the token, checks scopes, and applies per-connection rate limiting before touching any data.
Agent keys are workspace-scoped. A key for workspace A cannot access workspace B.
What agents can do
- Push activity events (
events.write) - Raise signals — findings the agent wants surfaced to the workspace (
signals:write) - List and read individual signals
- Read and acknowledge its mailbox (
notifications:read) - Report agent-hook invocations for observability
Scopes
| Scope | What it unlocks |
|---|---|
events.write | Push activity events and agent-hook invocations |
signals:write | Create signals |
notifications:read | Read and acknowledge mailbox items |
Agent API
External agents use OAuth bearer tokens with /agent-api/v1.