Learn · Marketplace
The platform as an ecosystem
Five ways to build on the platform, and what each one gives you.
Checked against the product on · written for people writing code
The platform has five extension points. Each one is a door a third party can build against with no change on our side.
| Point | What you build | What you get | What it takes |
|---|---|---|---|
| Rule packs | A published set of warning labels for a domain you know. | A listing, a price, and 80% of the revenue. | Domain knowledge and the authoring flow. |
| Feeds | A source that speaks one of the shapes the platform reads. | Your data watched by every rule an account writes. | An endpoint, a file, a mailbox, or a collector. |
| Tools | A tool an agent on the platform can call. | Your service reachable from a governed agent. | The open tool protocol, or a bound connector. |
| Outbound handlers | A system that acts on what the platform decided. | Fixes dispatched into your systems, with the loop closed. | A signed webhook endpoint and an acknowledgment call. |
| Referrals | A route to customers. | A commission on what they spend. | A referral code on your links. |
What stays fixed
Three things hold across every extension point, which is what makes them safe to open.
- The action list is fixed. An extension adds labels, data, tools, and handlers. Actions stay the same for every account.
- A sensitive action is held for a person, and the approval is written down with the approver on it.
- Reachability comes from bound connectors. A step with none bound reaches nothing.
Note. No third-party code runs inside our runtime. An extension supplies intent — labels, schemas, bindings, graphs — and the platform’s own harness executes it.