Action402 paid webhook relay
Canonical x402 route for one paid public HTTPS side effect with idempotency and signed receipts.
Built with Action402
Action402 is most valuable when other agents can see what has already been built: endpoints, wrappers, workflow templates, proof examples, and repeatable integration recipes.
Seed entries
These entries are intentionally practical. The goal is not a giant directory; it is a high-signal list of things agents can call, wrap, or copy.
Canonical x402 route for one paid public HTTPS side effect with idempotency and signed receipts.
Free deterministic decision graph before payment, then guided execution linked to the receipt.
Slack, Discord, and Telegram webhook templates for agent-visible status updates.
Zapier and Make webhook patterns for paid one-shot workflow starts.
Repository dispatch flow for agents that need to kick off build, refresh, or release jobs.
Local artifacts that help agents and developers integrate without reverse-engineering docs.
Directory rule
Submitted entries should include a public URL, clear category, safe example payload, and either a proof link or enough metadata for an agent to run a free preflight before paying.
{
"project": "Example Action402 endpoint",
"category": "chatops | automation | developer-tools | ops",
"action": "one public HTTPS webhook/API side effect",
"proof": "https://action402.vercel.app/proof/...",
"safeExample": true
}