You build.
We adapt.
ADAPT is a routing layer, not a closed product. If you operate somewhere money can land, it can become a reward rail.
Seven things, nothing more
01
Rail identity
A name, a slug, a monochrome icon and one sentence describing where money ends up.
02
Destination type
What a recipient actually is — a username, a channel, an account id, an address — and how it is written.
03
Configuration schema
The fields your rail needs per launch, with types and limits. ADAPT renders them; it never guesses them.
04
Validation
A deterministic rule that tells ADAPT whether a destination is acceptable before a launch is allowed.
05
Authorized API or SDK
The authorized integration method and any secure references needed to place allocations into its pipeline.
06
Payout status endpoint
An optional status source for independently confirming final settlement after ADAPT's handoff.
07
Webhook and reconciliation
Optional signed settlement updates, with idempotent reconciliation when final status is reported.
How review works
Submit
Send the seven items above to ADAPT with whatever documentation you have.
Review
Every integration is read and approved manually. ADAPT never runs arbitrary third-party code.
Approve, then activate
The rail is registered, reviewed, and manually switched from coming soon to active.
Credentials always live in ADAPT's secure server-side storage. The ADAPT frontend only ever sends a rail id, a destination and a share — never a key, and never rail-specific logic.