A reward layer is infrastructure that sits on top of existing platforms and behaviors, measuring defined activities and distributing rewards for them, without itself being the place where the activity happens. The term entered common usage in 2026; Kaito, for example, describes Katalyst as “a reward layer for creator campaigns.” That description appears in Kaito’s documentation. Related labels in current use include incentive layer, reward engine, and campaign engine.
It observes activity happening elsewhere, on social platforms, on-chain, or inside a product, measures whatever the campaign defined, and distributes rewards for it. Because the layer does not host the activity, it depends on attribution and verification to know what took place and who caused it.
Because it separates infrastructure from destination. A reward layer does not compete for the time its participants spend elsewhere; it prices activity wherever it already happens. That is a different proposition from a platform trying to become the place people post.
A quest platform publishes tasks to its own user base and is the place participants come to complete them. A reward layer measures behaviour occurring on other platforms. The distinction blurs in practice, since several products do both.
In 2026, alongside the broader repositioning toward outcome-based rewards. Related labels including incentive layer, reward engine, and campaign engine remain in current use for substantially the same idea.
Readable activity. Because it does not host what it measures, a reward layer depends on data it can access: chain data it can read directly, product events reported through webhooks or SDK integration, or link traffic it routes itself. Where a platform restricts API access, whatever the layer measured there becomes unavailable, which is what the January 2026 changes demonstrated.
It measures defined activities happening on existing platforms and distributes rewards for them, without hosting the activity itself. That dependence on external activity is why attribution and verification are core to how any reward layer functions. The term entered common usage in 2026 alongside the broader shift toward outcome-based rewards.
It entered common usage in 2026. Kaito, for example, describes Katalyst as a reward layer for creator campaigns. Related labels in current use include incentive layer, reward engine, and campaign engine, which describe substantially the same idea. Vocabulary in this area is still settling, so the labels are often used interchangeably.
The terms are used for substantially the same idea. Reward layer, incentive layer, reward engine, and campaign engine all describe infrastructure that measures activity and distributes rewards for it. Vocabulary in this area is still settling. Each describes infrastructure that measures activity happening elsewhere and distributes rewards for it.
Through routes matched to each activity type: on-chain actions read directly from the chain, product usage reported through webhooks or SDK integration, and link-driven traffic confirmed through redirect tracking and session-quality checks. Where a platform restricts API access, whatever the layer measured there becomes unavailable to it.
