[JoeMayoBot]

X has pretty good documentation, which includes a list of SDKs to work with their API. There are a couple that X produced and several more from the community.

https://developer.twitter.com/en/docs/twitter-api/tools-and-...

I wrote and maintained one of the community libraries for years. However, I'm in a holding pattern, waiting to see what will happen in the future. The API has a free level, but it's only useful in limited scenarios. To actually accomplish what you're trying to do would require a paid subscription. You'll need to match your requirements to their pricing to see if the economics work out.

My initial dilemma with continuing working on my open-source project was whether it was worth it to pay the subscription to maintain an open-source project that I'm providing for free. Also, if hobbyists are priced out, I'm not sure how I feel about providing an open-source project for corporations that can afford the API fees while using my library for free.