Overview

Trusty Sweep is the consumer control layer for digital waste, digital pressure and digital spend. Consumers connect Gmail, Google Drive, Outlook, OneDrive and Dropbox; Sweep discovers what consumes storage and money, preserves what matters in Trusty Vault, and executes verified, reversible, receipted Sweeps.

The developer platform is the same engine, externalized through a governed API. Nothing here is a second implementation.

What you can build

• Embedded storage intelligence: show your users their pressure, reclaimable bytes and time-to-full inside your product, with Sweep Connect handling provider OAuth, consent and token custody.
• Portability: move or copy a user’s data between providers, or to bring-your-own S3-compatible storage, with metadata mapping, lossiness reporting and a Portable Asset Manifest for every object.
• Agent actions: let an AI agent analyze, plan and (with delegated authority and step-up approval) execute Sweeps through MCP or A2A.
• Spend and revenue intelligence: trials, renewals, meter traps, spend map, and creator revenue reconciliation, read through the same API.

How a Sweep happens

plan → validate → authorize → commit → verify → receipt

1. Plan: POST /v1/plans builds a Shadow Sweep from inventory metadata, hashes and provider revision markers. It never touches provider state.
2. Validate: POST /v1/plans/{id}/validate compares preconditions with live state. Drift marks the plan stale; a stale plan cannot commit.
3. Authorize: POST /v1/plans/{id}/authorize evaluates Action Authorization (who may do what) and Commercial Authorization (may Sweep charge for it). The result binds to the plan hash.
4. Commit: POST /v1/plans/{id}/commit is the single gate. The execution runs durably; Vault verification always precedes source removal.
5. Verify & receipt: measured before/after state, per-object results and a signed receipt at GET /v1/executions/{id}/receipt.

Principles you can rely on

Principle	Guarantee
Vault verified first	No adapter, job or agent path can trash a preserved object before its Vault commitment is verified.
Reversible by default	Source actions use provider trash/recycle semantics; non-preserved objects only ever receive reversible actions.
No raw provider tokens	Sweep Connect keeps provider credentials inside Sweep’s connector boundary. You receive a cxn_… connection.
Two authorizations	Action Authorization and Commercial Authorization are distinct; neither substitutes for the other.
Deterministic truth	Pricing, rating, state transitions, arithmetic and authorization are code. AI only classifies, extracts and explains.
Test mode is isolated	sk_test_ keys operate on a simulated tenant. Nothing can reach production user state.

Where things live

• Base URL: https://api.trustysweep.com
• MCP: https://mcp.trustysweep.com/mcp
• A2A Agent Card: https://api.trustysweep.com/.well-known/agent-card.json
• Receipt keys: https://api.trustysweep.com/.well-known/sweep-receipts.json
• OAuth metadata: https://api.trustysweep.com/.well-known/oauth-authorization-server
• Source: github.com/TrustyCap-Technologies/sweep-platform (Apache-2.0)