I think we should use a separate api token named for this view. We may have additional clients of the APIs in the future, and we should be able to make the decision to limit one of the other of these endpoints from those additional clients.
@Darknight1500 Could you provide more context on the issue reported here?
Thank you! since the spam captured me by @mention and I'm one of the datatracker's lead maintainers,  I'll confirm for you that this is simply a cut-paste from the datatracker's issue tracker and is not related to tensorflow at all. I recommend handling this as you would handle any other spam issues. @rjsparks Thank you for your response here. Closing this issue for now.
I think we should use a separate api token named for this view. We may have additional clients of the APIs in the future, and we should be able to make the decision to limit one of the other of these endpoints from those additional clients.

_Originally posted by @rjsparks in https://github.com/ietf-tools/datatracker/pull/7291#issuecomment-2037572500_