Skip to main content

​
I want to use Parly

Start with the App. That is the user-facing control surface for wallet connection, authentication, shielding, private execution, activity review, selective receipts, and verification handoff. It is where product truth becomes usable.

​
I want to run a relayer

Start with the relayer docs and the public relayer source. Parly ships a real relayer runtime. Operators do not need to design their own private-execution daemon from first principles before participating.

​
I want to integrate Parly in code

Start with the SDK. The SDK is the developer integration surface for deterministic authentication, recovery identity derivation, note handling, execution request construction, exact approval discipline, and outcome handling. This is the correct entry point for backend services, automation, service operators, and integrations that want protocol-accurate behavior.

​
I want to build an agent workflow

Start with the MCP docs. The MCP server exists for bounded agent workflows. It exposes agent-owned tools, keeps agent keys separate from relayer and treasury power, and supports MPP-compatible wrapping where needed. This is the right path for copilots, service agents, and headless automation.

​
I want to understand the system before using it

Start with How Parly Works and Architecture Overview. Those pages explain the launch surface, recovery model, selective verification, relay model, SDK/MCP boundary, and the role of each major component.

​
Public surfaces

App The main execution surface for shielding, recovery, private execution, activity review, selective disclosure, and verification handoff. Verify The public verification surface for one disclosed payout lane. Relayer The operator runtime for private execution. Registry The official discovery surface for relayer listing in the public app. SDK The developer integration layer. MCP Server The agent tooling layer.