Просмотр новости
Найдите то, что Вас интересует
Спутники
РН
SpaceX
Роскосмос
NASA
СпутникиРНSpaceXРоскосмосNASA
What’s your App ID?
None. SniperRank has not enrolled in the Developer Program or created an app because this request seeks policy clarification before implementation.
What endpoint are you using?
None. No X API requests have been made and no endpoints have been selected or used.
What API version are you on?
No API integration currently exists. Any contemplated implementation would use the official current X API.
Are you using a library or SDK? Which one?
None. SniperRank has not implemented an X API integration.
What is the issue?
Pre-implementation policy clarification for an intended X API research use case, described below.
Steps to reproduce the issue
Not applicable; this is a policy-clarification request, not a technical defect.
What is the error message?
Not applicable.
When did it start?
During pre-launch compliance review, before X API access or research began.
What have you tried to troubleshoot?
We reviewed X’s Developer Agreement, Developer Policy, Restricted Use Cases, Display Requirements, support documentation, and X Staff guidance directing developer-policy questions to this forum.
Hello X Developer Policy team,
SniperRank (@Sniperank, https://sniperank.com) is a pre-launch research service that intends to use the official X API to research a predefined set of named public financial-market commentators.
SniperRank would identify objectively testable claims from public Posts, evaluate those claims against independently obtained evidence under a documented methodology, and create independent claim evaluations. Those evaluations may be aggregated by named commentator into comparative historical claim-performance metrics, including leaderboard-style presentations.
The service may be commercial and subscription-supported. Subscribers may pay for SniperRank-created evaluations, analysis, audit history, and aggregate research metrics informed partly by public Posts obtained through the X API.
SniperRank would not sell or provide customers with API access, raw API responses, bulk X Content, or downloadable X datasets.
SniperRank needs to maintain provenance and audit references for the Posts underlying its evaluations. This creates a retention question when a Post is edited, deleted, or otherwise becomes unavailable.
SniperRank would not infer sensitive or psychological characteristics, perform advertising segmentation, or use its research for credit, employment, insurance, housing, or other consequential eligibility decisions.
Its research metrics and comparative presentations would be informational. They would not constitute financial, investment, or trading advice; personalized recommendations; trading signals; or buy/sell/hold guidance.
No X API data has been retrieved, historical research has not begun, and no public scores have been published. Functionality implicated by the following questions will remain disabled unless X confirms that the intended use is permitted.
1. Individual profiling
Does evaluating objectively testable public claims and publishing aggregate historical claim-performance metrics associated with named public commentators constitute prohibited “individual profiling” under X’s Restricted Use Cases when the analysis is limited to attributable public statements and observable outcomes and does not infer sensitive or psychological characteristics or determine eligibility?
2. Commercial research
May a commercial, subscription-supported research service charge for independently created evaluations, analysis, audit history, and aggregate research metrics informed partly by public Posts obtained through the X API, provided customers are not sold or given API access, raw API responses, bulk X Content, or downloadable X datasets?
3. Deleted or unavailable Post provenance
If a source Post becomes unavailable, after removing any X Content that X requires to be removed, may the research service privately retain only the Post ID and/or original permalink as a non-public provenance and audit reference, or must those identifiers also be deleted?
Could an X Staff member also confirm whether its response in this forum constitutes the written policy clarification or approval required for the described use, or whether an additional private or account-specific approval process is required?
Thank you.
2 posts - 2 participants
Read full topic
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | X APIを利用した有料LINE・Discord案件検索通知サービスの利用可否について | 0 | 16.06 | 28-08-2026 |
| 2 | Do human-reviewed AI reply suggestions need additional approval? | 0 | 9.98 | 27-08-2026 |
| 3 | Approval route requested: owner-reviewed AI-assisted X reply preparation | 0 | 10.42 | 27-08-2026 |
| 4 | Not able read paid subscriber posts using API v2 | 0 | 4.62 | 30-08-2026 |
| 5 | X Can't post link | 0 | 9.12 | 30-08-2026 |
| 6 | X API v2 returns HTTP 500 with empty response body across multiple endpoints | 0 | 8.24 | 27-08-2026 |
| 7 | Approval request: AI-powered mention-triggered reply bot (@MarlowStudent, App ID 32973549) | 0 | 9.98 | 30-08-2026 |
| 8 | Developer org display name stuck on Xpressomancer + xAI team link fails with invalid_link | 0 | 17.69 | 30-08-2026 |
| 9 | Request for X Live / Livestream API Access | 0 | 6.14 | 29-08-2026 |