An endpoint declares what it may do.
- Read by
- GET /v1/programmable-endpoints/{ref}
- Posture
- 8 dimensions
- Lifecycle
- suspend · resume
- Locators
- sort code · bank acct · BACS · crypto
- receive
- send
- lifecycle
- drain
- backing
- purpose
- gas
- liquidity
Eight dimensions, one contract
The posture declares what an endpoint may receive and send, how it retires, where leftover value drains, what backs it, what it is for, who pays the cost to move, and whether it draws on liquidity. Every combination is a different instrument.
Receiving, precisely
receive is scoped: internal only, external and internal, suspense, or returns only. An endpoint that should never take outside money cannot.
Retired, never stranded
lifecycle and drain decide how it ends: closed by command, at a time, or at an amount, with leftover value drained to its parent or returned. Value is never stranded on a dead endpoint.
Steered by one call
You never edit an endpoint in place. Suspend or resume it with a lifecycle command; the response returns the previous and current posture with a new stateVersion.
One endpoint’s posture, opened.
Each programmable endpoint declares what it may do — what it receives, what it sends, how it retires, what holds its value. Here is one endpoint’s posture; open any dimension to see the choices and what each means.