Skip to content

Acceptable Use Policy

TwitterAPIs is a pay-per-use API for public Twitter/X data, and this page is its acceptable use policy: what the service may and may not be used for. It covers every way you can reach TwitterAPIs: an API key, the MCP server you run yourself, the hosted MCP endpoint you sign in to, and the keyless MCP endpoint that needs no account at all. It restates the acceptable-use section of our Terms of Service in plain language rather than adding to it, so where the two differ in wording, the Terms are the agreement and they govern.

1. What this covers, and which document governs

This policy explains, in plain language, what TwitterAPIs may and may not be used for. It covers every way you can reach the Service: an API key, the MCP server you run yourself, the hosted MCP endpoint you sign in to, and the keyless MCP endpoint that needs no account at all. It restates the acceptable-use section of our Terms of Service rather than adding to it. Where this page and the Terms differ in wording, the Terms are the agreement and they govern. Read the Terms of Service and our Privacy & Data Handling page.

2. Rules that apply to everyone

You agree not to use the Service to spam, harass, or abuse anyone on Twitter/X; to collect data in violation of Twitter/X's terms; to resell API access to third parties without our permission; to reverse-engineer, overload, or disrupt the Service; or for any unlawful purpose. These apply the same whether you are paying us, evaluating us on free credits, or calling the keyless endpoint.

3. The keyless endpoint, specifically

The keyless MCP endpoint needs no account, so there is nothing for us to attach a warning to and nobody for us to contact. Sending a request to it means you accept the Terms, and your client must send the acceptance value the endpoint returns back with each later call that day. It is read-only, capped, and offered so that you can evaluate the Service before deciding whether to sign up. Trying to get around its limits is prohibited. It is not an anonymity service, and it is not intended to be the way you run anything in production.

4. What happens if a rule is broken

If the traffic is tied to an account, we may rate-limit it, suspend the key, or close the account, depending on what happened. On the keyless endpoint there is no account to suspend, so the only measures available to us are rate limiting, blocking, and withdrawing the endpoint if it is being abused at a level we cannot otherwise contain. We would rather not do the last one, which is a large part of why this page exists.

5. Reporting a problem

If you believe someone is using the Service against this policy, or you think we have got a decision wrong, tell us and we will look at it. Email emma@twitterapis.com or use our contact page.

6. Changes to this policy

We may update this policy as the Service changes. Material changes are reflected in the Terms of Service as well, because the Terms are what you have agreed to. The date below is when this page was last revised.

Not sure whether your use case is allowed?

Ask us first

Next read

Continue exploring related pages:

Twitter API use cases

14 use cases from sentiment analysis to lead generation.

Twitter API answers

Short, sourced answers to the most common Twitter and X API questions.

Twitter timeline API

Pull an account's full posting history over one REST endpoint.

Twitter list API

Read list members and list timelines with the same Bearer key.

Last updated: October 2026