🧰
CLI
Plan, review, apply, and verify supported protection workflows with explicit approval.
CLI guide
YetdaPayBuild, protect, and sell software.
Developer tools for paid features, licensing, and commerce — from your terminal, AI agent, or app.
Skip to content
Find your starting point
| Your goal | Start with |
|---|---|
| Protect an existing paid module | Quickstart |
| Let a coding agent use DevPay | Local MCP setup |
| Enforce a license in your app | SDK overview |
| Add donations or feedback | Integration examples |
| Find an API or operations guide | Reference library |
From an idea to verified evidence
1. Explore — install from the repository and run yp doctor.
2. Integrate — generate a protection plan, approve changes, or connect a supported SDK.
3. Verify — inspect executed checks and the evidence they actually produced.
Product candidate — not a production security guarantee
PLANNED, APPLIED, and VERIFIED are different states. Payments currently use mock or Toss TEST keys only; no live PG capture is verified. Packages are not published to the public npm registry. Review known limitations before adoption.
Browse detailed engineering references · Korean developer guide