Paperclip
Action requiredNot connectedMOCKRead-only agent roster, company and project list from the existing AI engine.
- How it connects
- Paste a key or token
- Health
- healthy
- Integration status
- connected
- Credential
- Not configured
- Last sync
- never
- Connected
- not yet
2 of 4 steps done
Setup
Get an API key and the company ID from Paperclip
You are hereNot done yetAdministrator (once)Provider console (one time)From the running Paperclip instance. The key only ever needs read access — PAXX's Paperclip connector has no write methods, by interface contract.
Encrypted credential storage initialized
DoneAdministrator (once)In the HubCredentials are sealed with AES-256-GCM before they reach the database, and PAXX refuses to store them at all without a key. Initialize it with one click in the Integration Hub, or set the key in the server environment if you would rather manage it yourself.
Paste them into PAXX
Not done yetAdministrator (once)In the HubPress Connect. PAXX reads the company record with the key before storing it, so a wrong ID or a revoked key fails here rather than silently emptying the Agents panel.
Provisioning writes (optional, environment only)
optionalDoneAdministrator (once)Server environmentCreating Paperclip projects and workspaces during a provisioning run requires PAPERCLIP_WRITE_ENABLED=true in the server environment. This one is deliberately not available in the Hub: Paperclip is production-like infrastructure, and a browser session must not be able to grant itself write access to it. Reads work without it.
This step cannot be completed from the browser — it needs shell access to the server environment and a restart to pick the value up.
Paste a key or token
Connect
Paste the Paperclip API key and company ID; PAXX verifies them before storing.
Live check
Connection test
GET /api/companies/{id} on the configured Paperclip instance — a read, which is the only thing this credential can do.
2 declared
Permissions
What PAXX asks the provider for. The provider's own consent screen is the authoritative grant — this list is what will be requested, and after connecting, what was actually returned.
- readRead agentsnot requested yetAgent roster and blocked-agent state.
- readRead projectsnot requested yetPaperclip project list and company record.
Capabilities
What you get
Agent roster
readNot availableEvery agent with its real status, role and pause/error reason.
Available once this provider is connected.
Dashboard → Agents/paxxBlocked agents as attention
readNot availableA blocked agent is work needing a human just as much as a blocked issue is.
Available once this provider is connected.
Dashboard → AttentionProjects and company
readNot availableThe Paperclip project list and company record behind the PAXX portal.
Available once this provider is connected.
/paxxDashboard → Projects
Requirements
Diagnostics
Administrator requirements
One-time work for whoever administers this PAXX instance.
Get an API key and the company ID from Paperclip
Not satisfiedAdministrator (once)Provider console (one time)From the running Paperclip instance. The key only ever needs read access — PAXX's Paperclip connector has no write methods, by interface contract.
Encrypted credential storage initialized
SatisfiedAdministrator (once)In the HubCredentials are sealed with AES-256-GCM before they reach the database, and PAXX refuses to store them at all without a key. Initialize it with one click in the Integration Hub, or set the key in the server environment if you would rather manage it yourself.
Paste them into PAXX
Not satisfiedAdministrator (once)In the HubPress Connect. PAXX reads the company record with the key before storing it, so a wrong ID or a revoked key fails here rather than silently emptying the Agents panel.
Your requirements
Per-person steps — the authorization is yours, not the deployment's.
None.