Skip to content

Commit 43782b4

Browse files
committed
docs: replace T&Cs with link to docs
1 parent f3f15de commit 43782b4

File tree

1 file changed

+9
-47
lines changed

1 file changed

+9
-47
lines changed

β€Žplugins/twitter/README.mdβ€Ž

Lines changed: 9 additions & 47 deletions
Original file line numberDiff line numberDiff line change
@@ -3,58 +3,20 @@
33
The **Twitter Plugin** provides a lightweight interface for integrating Twitter (X) functionality into your GAME SDK agents. Built on top of [`virtuals_tweepy`](https://pypi.org/project/virtuals-tweepy/) by the Virtuals team β€” a maintained fork of [`Tweepy`](https://pypi.org/project/tweepy/)) β€” this plugin lets you easily post tweets, fetch data, and execute workflows through agent logic.
44

55
## πŸ“œ GAME X API Usage Terms & Rules
6-
By using the GAME X API, you agree to the following terms. Violation of any rule may result in immediate revocation of access. We reserve the right to modify API behavior, limits, or access rights at any time, with or without notice.
7-
8-
### βœ… Allowed Usage (Green Flags)
9-
#### General
10-
- Keep under 50 posts/day
11-
- Follow/unfollow: <100/day
12-
- Use organic, varied languageβ€”avoid robotic or repetitive posts
13-
- Use a mix of images, videos, and text-based content
14-
- Include polls, threads, quotes, retweets to encourage engagement
15-
- Mark account as sensitive if needed
16-
- Always include the automated label for agent-generated content
17-
18-
#### Replies, Mentions, and DMs
19-
- Max 10 replies/hour to different users
20-
- Max 10 DMs/day to new users
21-
- Agent may only reply or DM when:
22-
- User mentions, replies, retweets, or DMs the agent
23-
- Only 1 automated reply/DM per interaction
24-
- Always validate post existence before replying (statuses/lookup)
25-
- Filter for sensitive usernames/media/content
26-
27-
#### βœ‰οΈ DM Rules
28-
- DMs must be triggered by valid user interaction
29-
30-
Only use:
31-
- GET /dm_conversations
32-
- GET /dm_events
33-
- POST /dm_events/new
34-
- No crawling, scraping, or off-platform storage of DM data
35-
- No DMs used to bypass rate limits or coordinate bot activity
36-
- One DM per user trigger, no spamming
37-
38-
### 🚫 Prohibited Activity (Red Flags)
39-
- ❌ Liking tweets, adding users to lists/collections
40-
- ❌ Engagement farming (e.g., repetitive β€œLike if…” prompts)
41-
- ❌ Auto-posting about trending topics
42-
- ❌ Duplicate phrases across posts/accounts
43-
- ❌ Tweet bursts (post every 10–15 mins, minimum)
44-
- ❌ Over-replying or over-DMing
45-
- ❌ Misleading or redirect-heavy links
46-
- ❌ Harassment, abuse, hate speech, or doxxing
47-
- ❌ Cloning multiple automated accounts for similar purposes
6+
By using our GAME API, you agree to the [Terms of Use](https://virtualsprotocol.notion.site/Terms-of-Use-2152d2a429e980f09a74c85c0a5974c4?source=copy_link) and [GAME X API Terms](https://virtualsprotocol.notion.site/Agents-on-X-Rulebook-1972d2a429e980ddaa85da3c903afade?pvs=74).
7+
8+
## πŸš€ API Access Tiers
9+
Virtuals sponsors the community with a **Twitter Enterprise API access plan**, using OAuth 2.0 with PKCE. This provides:
4810

4911
## πŸš€ API Access Tiers
5012
### Tier 1 β€” Default
51-
- Basic access
52-
- Standard rate limits
13+
- Higher rate limits: **50 calls / 5 minutes**
14+
- Smoother onboarding
15+
- Free usage via your `GAME_API_KEY`
5316

5417
### Tier 2 β€” Elevated
55-
- Higher rate limits
56-
- Request access via Discord β†’ @virtualsio
57-
- Requires verification
18+
- Even higher rate limits
19+
- Requires approval from the Virtuals team. Request access via Discord β†’ @virtualsio
5820

5921
---
6022
Use it standalone or compose multiple Twitter actions as part of a larger agent job.

0 commit comments

Comments
Β (0)