Which addresses belong to which pool verified
Lists pool membership; every write form we tried was refused, and the console uses its own path for this.
In detail
Membership is a pair: a pool and a sending address. The console writes it through its internal /poolips with pool_id and localip, and reports one of three outcomes — created, stolen from another pool, or unchanged — because an address belongs to exactly one pool. That is the same uniqueness rule the throttle rules follow, and it means adding an address to a pool can silently remove it from another. Over REST the reading side works and returns the pairs. Writing did not: four plausible bodies were refused with 400 and an empty body, including the one the console itself uses. Either the endpoint expects a shape we did not find or it is read-only in this build; the catalogue records what was observed and the open question says how to settle it. Until then a control module has two working roads to pool membership: the console's own API, or the pool_ips table with a reload afterwards.