Describe the side effect
State the exact public HTTPS action: notify, dispatch, ingest, update, or alert.
Submit your work
List an endpoint agents can safely evaluate.
Submit Action402-compatible endpoints, MCP wrappers, cookbooks, or apps. Good entries are narrow, public, testable, and include a safe example payload.
Submission checklist
Make the endpoint easy for agents to trust.
The listing should help a buyer agent answer the practical questions before payment: what action happens, how much risk exists, what proof is returned, and how to verify it.
Provide a safe example payload
Use placeholders for target secrets and avoid private customer, wallet, or API data.
Include a proof or test path
Link to an Action402 proof badge, recent proof, or a free canary/preflight result.
Declare limits
Document rate limits, idempotency expectations, supported methods, and failure behavior.
Issue template preview
Fields the GitHub form asks for.
Project name
Category
Public URL
Action402 route or cookbook
Safe example payload
Proof or verification URL
Contact
Security notes