RevRule Sandbox — program the economics, watch the entitlements compute

This page runs the actual RevRule revenue engine in your browser, the same code that processed real money during acceptance testing. Pick a scenario, run a revenue event, and watch every micro-unit get assigned, explained, and recorded. Nothing here moves money. Every distribution the engine produces is a proposal, never an execution.

Proof this engine handles real money. It processed a $1.00 Stripe charge, two 0.10 USDC settlements on Base Sepolia (tx 1, tx 2), and a $1,000 royalty statement, with every split verified to the micro-unit. Sandbox runs below are simulated.

1. Pick a scenario

2. Run a revenue event

3. Make it yours

Define your own split. Add up to five participants with a name and a percentage each. The last participant automatically receives whatever remains, and the engine conserves the pool exactly. This uses the same engine as the scenarios above.

What you are looking at

RevRule observes economic events, computes who is owed what, and proposes payout instructions. Regulated partners move the money. The engine never holds funds and never controls settlement. Full source: github.com/Payloadhq/payload-flow.

Run this against the live API

Everything above runs in your browser and is simulated. The same engine is hosted as the RevRule API at https://payload-rail.fly.dev, and you can run your own graph against it for free:

  1. Get a free access key. Use the RevRule Console ("Get a free API key"), or one call: POST https://payload-rail.fly.dev/v1/access-keys with body {"label":"..."}. The key is returned once; it creates a free-tier account.
  2. Create your own graph with POST /v1/graphs (Bearer key), then activate it with POST /v1/graphs/{id}/activate. The API reference quickstart has a complete graph spec you can copy.
  3. Dry-run an event with POST /v1/graphs/{id}/simulate — the same event envelope as a real event, with zero side effects: no ledger entries are written and no state changes. When you are ready, post real events to POST /v1/graphs/{id}/events.

Full quickstart in one file: payload-rail.fly.dev/llms.txt · Endpoint reference: RevRule API Reference.