I don't know about POTA spots on pota.app, having not participated in POTA, but I presume that it's like SOTA spots on SOTAwatch. SOTA spots are on a completely different network than the DX spotting networks. There probably are no technical standards for providing or consuming data outside of the SOTAwatch website, except a back door for preauthorized summit activators to send in a spot or alert by text or email, because there is no great need for such a thing. Most people just use the web site to check for spots and alerts, or submit spots and alerts.
Because the network is separate, the filtering is provided by the users themselves. They know to not try sending DX spots via SOTAwatch, or look for such spots on SOTAwatch, because there would be no point to doing so. As far as I know, SOTAwatch doesn't work with contest logging software, by design.
In order to be spotted on SOTAwatch, an operator would need to be clearly trying to activate a summit.
Anyone can submit a spot for another operator on SOTAwatch, and spotting oneself is allowed also (unlike on DX spotting networks). Prearranged contacts aren't legal for DXCC or contest points, but they are fine for SOTA, and that's what the SOTAwatch alerts are all about. Alerts are for planned future activities, so that activators can notify chasers that they plan to activate a summit in the future when they presumably won't have internet access. Also, advance notice of activations serves to drum up interest, which leads to more chasers, which makes activating summits more enjoyable for the activators. The majority of alerts are from the operators who are planning to activate the summits, which makes sense. Submitting an alert for another operator is uncommon, but allowed.