x-developer 2.6.5 → 2.6.7

package/skills/x-twitter-scraper/references/extract-x-community-data.md

@@ -1,4 +1,4 @@
-# X Communities API: Export Members, Moderators, and Posts
+# X Communities API: export members, moderators, and posts
 
 Xquik supports community discovery, metadata, members, moderators, posts, and
 search. Use the numeric community ID from `x.com/i/communities/{id}`.
@@ -6,22 +6,22 @@ search. Use the numeric community ID from `x.com/i/communities/{id}`.
 > Xquik is an independent third-party service. Not affiliated with X Corp.
 > "Twitter" and "X" are trademarks of X Corp.
 
-## X Community Dataset Matrix
+## X Community dataset matrix
 
-| Dataset | Extraction Type | Required Input | Useful Keys |
+| Dataset | Extraction type | Required input | Useful keys |
 | --- | --- | --- | --- |
 | Members | `community_extractor` | `targetCommunityId` | Community ID and user ID |
 | Moderators | `community_moderator_explorer` | `targetCommunityId` | Community ID and user ID |
 | Posts | `community_post_extractor` | `targetCommunityId` | Community ID and tweet ID |
 | Matching posts | `community_search` | Community ID and `searchQuery` | Community ID, query, tweet ID |
 
-## X Community Research Schema
+## X Community research schema
 
 Use a separate table for communities, member observations, and post
 observations. This prevents a current profile update from changing past
 research results.
 
-| Table | Primary Key | Recommended Context |
+| Table | Primary key | Stored context |
 | --- | --- | --- |
 | `communities` | Community ID | Name, description, rules, collected time |
 | `community_members` | Community ID, user ID, snapshot ID | Role and membership observation |
@@ -51,7 +51,7 @@ Moderators answer governance questions. Posts answer content questions.
 Community search answers topic questions inside one community.
 
 Use a direct read for a small application page. Use extraction jobs for durable
-or complete datasets. Estimate before creating bulk work.
+or exportable datasets. Estimate before creating bulk work.
 
 Keep member and post datasets separate. Their identifiers, update rates,
 privacy considerations, and analysis methods differ.
@@ -90,7 +90,7 @@ Community writes are separate account actions. They require a connected X
 account and explicit confirmation. Public community reads do not authorize
 joins, leaves, or moderation actions.
 
-## X Community Extraction Checklist
+## X Community extraction checklist
 
 1. Confirm the public community and numeric ID.
 2. Choose members, moderators, posts, or scoped search.
@@ -100,7 +100,7 @@ joins, leaves, or moderation actions.
 6. Separate raw content from derived analysis.
 7. Apply privacy, retention, and redistribution controls.
 
-## X Community Dataset Quality Checks
+## X Community dataset quality checks
 
 Report the requested result bound, returned rows, unique IDs, and collection
 time. Explain whether the dataset covers members, moderators, posts, or search
@@ -114,8 +114,8 @@ For topic analysis, publish the query version and language coverage. For network
 analysis, explain whether edges represent membership, replies, quotes, or
 reposts. Each edge has a different meaning.
 
-## Related X Community API Guides
+## Related X Community API guides
 
 - [Extraction types](extractions.md)
 - [Community endpoint routes](api-endpoints-x-api.md)
-- [X API alternative content hub](twitter-api-alternative-faq.md)
+- [X API alternative FAQ](twitter-api-alternative-faq.md)

package/skills/x-twitter-scraper/references/extractions.md

@@ -1,8 +1,8 @@
-# Xquik Extraction Tools
+# Xquik extraction tools
 
-23 bulk data extraction tools. Each requires a specific target parameter.
+Xquik provides 23 bulk data extraction tools. Each tool requires a specific target.
 
-## Privacy and Acceptable Use
+## Privacy and acceptable use
 
 Bulk extraction and export can collect large amounts of public identity,
 activity, and relationship data. Before creating a job, confirm the lawful
@@ -19,23 +19,17 @@ without renewed approval.
 The API accepts an omitted `resultsLimit`. This Skill must always send an
 explicit finite positive bound. Use the same bound for estimate and create.
 
-**Endpoint:** `POST /extractions`
+Call `POST /extractions`
 
-**Always estimate first:** `POST /extractions/estimate` with the same body to preview `creditsRequired`, `creditsAvailable`, and whether the job is allowed.
+Estimate first with `POST /extractions/estimate` with the same body to preview `creditsRequired`, `creditsAvailable`, and whether the job is allowed.
 
-## Contents
+## Tool types
 
-- [Tool Types](#tool-types)
-- [Response](#response)
-- [Retrieving Results](#retrieving-results)
-- [Exporting Results](#exporting-results)
-- [Estimating Usage](#estimating-usage)
+### Tweet-based tools
 
-## Tool Types
+These tools require `targetTweetId`.
 
-### Tweet-Based (require `targetTweetId`)
-
-| Tool Type | Description |
+| Tool type | Description |
 |-----------|-------------|
 | `reply_extractor` | Extract users who replied to a tweet |
 | `repost_extractor` | Extract users who retweeted a tweet |
@@ -44,7 +38,7 @@ explicit finite positive bound. Use the same bound for estimate and create.
 | `article_extractor` | Extract article content linked in a tweet |
 | `favoriters` | Extract users who favorited a tweet |
 
-**Example:**
+For example:
 ```json
 {
   "toolType": "reply_extractor",
@@ -52,9 +46,11 @@ explicit finite positive bound. Use the same bound for estimate and create.
 }
 ```
 
-### User-Based (require `targetUsername`)
+### User-based tools
+
+These tools require `targetUsername`.
 
-| Tool Type | Description |
+| Tool type | Description |
 |-----------|-------------|
 | `follower_explorer` | Extract followers of an account |
 | `following_explorer` | Extract accounts followed by a user |
@@ -62,7 +58,7 @@ explicit finite positive bound. Use the same bound for estimate and create.
 | `mention_extractor` | Extract tweets mentioning an account |
 | `post_extractor` | Extract posts from an account |
 
-**Example:**
+For example:
 ```json
 {
   "toolType": "follower_explorer",
@@ -72,14 +68,16 @@ explicit finite positive bound. Use the same bound for estimate and create.
 
 The `@` prefix is automatically stripped if included.
 
-### User Timeline Tools (require `targetUsername`)
+### User timeline tools
 
-| Tool Type | Description |
+These tools require `targetUsername`.
+
+| Tool type | Description |
 |-----------|-------------|
 | `user_likes` | Extract tweets liked by a user |
 | `user_media` | Extract media tweets from a user |
 
-**Example:**
+For example:
 ```json
 {
   "toolType": "user_likes",
@@ -87,16 +85,18 @@ The `@` prefix is automatically stripped if included.
 }
 ```
 
-### Community-Based (require `targetCommunityId`)
+### Community-based tools
+
+These tools require `targetCommunityId`.
 
-| Tool Type | Description |
+| Tool type | Description |
 |-----------|-------------|
 | `community_extractor` | Extract members of a community |
 | `community_moderator_explorer` | Extract moderators of a community |
 | `community_post_extractor` | Extract posts from a community |
 | `community_search` | Search posts within a community (also requires `searchQuery`) |
 
-**Example:**
+For example:
 ```json
 {
   "toolType": "community_extractor",
@@ -104,15 +104,17 @@ The `@` prefix is automatically stripped if included.
 }
 ```
 
-### List-Based (require `targetListId`)
+### List-based tools
 
-| Tool Type | Description |
+These tools require `targetListId`.
+
+| Tool type | Description |
 |-----------|-------------|
 | `list_member_extractor` | Extract members of a list |
 | `list_post_extractor` | Extract posts from a list |
 | `list_follower_explorer` | Extract followers of a list |
 
-**Example:**
+For example:
 ```json
 {
   "toolType": "list_member_extractor",
@@ -120,13 +122,15 @@ The `@` prefix is automatically stripped if included.
 }
 ```
 
-### Space-Based (require `targetSpaceId`)
+### Space-based tools
+
+These tools require `targetSpaceId`.
 
-| Tool Type | Description |
+| Tool type | Description |
 |-----------|-------------|
 | `space_explorer` | Extract participants of a Space |
 
-**Example:**
+For example:
 ```json
 {
   "toolType": "space_explorer",
@@ -134,14 +138,16 @@ The `@` prefix is automatically stripped if included.
 }
 ```
 
-### Search-Based (require `searchQuery`)
+### Search-based tools
+
+These tools require `searchQuery`.
 
-| Tool Type | Description |
+| Tool type | Description |
 |-----------|-------------|
 | `people_search` | Search for users by keyword |
 | `tweet_search_extractor` | Search and extract tweets by keyword or hashtag |
 
-**Example (people search):**
+For a people search:
 ```json
 {
   "toolType": "people_search",
@@ -149,7 +155,7 @@ The `@` prefix is automatically stripped if included.
 }
 ```
 
-**Example (tweet search):**
+For a tweet search:
 ```json
 {
   "toolType": "tweet_search_extractor",
@@ -158,7 +164,7 @@ The `@` prefix is automatically stripped if included.
 }
 ```
 
-### Tweet Search Filters
+### Tweet search filters
 
 `tweet_search_extractor` accepts structured filters. It combines them with
 `searchQuery` before collection.
@@ -216,7 +222,7 @@ The `@` prefix is automatically stripped if included.
 | `boundingBox` | string | Geographic bounding box |
 | `advancedQuery` | string | Raw X search operators appended to query |
 
-**Example with filters:**
+For example, apply filters:
 ```json
 {
   "toolType": "tweet_search_extractor",
@@ -229,9 +235,9 @@ The `@` prefix is automatically stripped if included.
 }
 ```
 
-`resultsLimit` (optional): Maximum results to extract. Stops early instead of fetching all. Pass this on both `POST /extractions/estimate` and `POST /extractions` when you only need a specific count.
+Set optional `resultsLimit` to stop after a specific result count. Pass the same value to `POST /extractions/estimate` and `POST /extractions`.
 
-### Profile Filters
+### Profile filters
 
 Profile-producing extractions also accept `minFollowers`, `maxFollowers`,
 `minFollowing`, `maxFollowing`, `minPosts`, `maxPosts`,
@@ -249,39 +255,39 @@ Profile-producing extractions also accept `minFollowers`, `maxFollowers`,
 }
 ```
 
-Statuses: `pending`, `running`, `completed`, `failed`.
+The status is `pending`, `running`, `completed`, or `failed`.
 
-## Retrieving Results
+## Retrieving results
 
 ```
 GET /extractions/{id}
 ```
 
-Returns paginated results (up to 1,000 per page). Each result includes:
+The endpoint returns up to 1,000 results per page. Each result includes:
 
 - `xUserId`, `xUsername`, `xDisplayName`
 - `xFollowersCount`, `xVerified`, `xProfileImageUrl`
 - `tweetId`, `tweetText`, `tweetCreatedAt` (for tweet-based extractions)
 
-## Exporting Results
+## Exporting results
 
 ```
 GET /extractions/{id}/export?format=csv
 ```
 
-Formats: `csv`, `json`, `md`, `md-document`, `pdf`, `txt`, `xlsx`. 100,000 row limit (10,000 for PDF).
+Choose `csv`, `json`, `md`, `md-document`, `pdf`, `txt`, or `xlsx`. Exports support 100,000 rows, except PDF supports 10,000.
 
 Exports include enrichment columns not present in the API response.
 
 The endpoint supports follower, following, post, engagement, profile, media,
 language, search, and date filters. It does not project individual fields.
 
-**Approval required:** Set the smallest approved `resultsLimit` when creating
+Get approval first. Set the smallest approved `resultsLimit` when creating
 the job. Before export, show the job, filters, format, row count, schema,
 recipients, storage, and retention. Materialize or transmit the dataset only
 after explicit approval. Delete it when the approved purpose ends.
 
-## Estimating Usage
+## Estimating usage
 
 ```
 POST /extractions/estimate
@@ -299,7 +305,7 @@ Same body as create. Response:
 }
 ```
 
-If `allowed` is `false`, do not create the extraction. It requires more credits
-than are currently available.
+If `allowed` is `false`, do not create the extraction. The current balance does
+not cover the estimate.
 
 For common mistakes and tool selection rules, see [mcp-tools.md](mcp-tools.md#common-mistakes).

package/skills/x-twitter-scraper/references/mcp-setup.md

@@ -1,6 +1,6 @@
-# Xquik MCP Server Setup
+# Xquik MCP server setup
 
-Connect AI agents and IDEs to Xquik through Model Context Protocol. Add the
+Connect MCP clients and IDEs to Xquik through Model Context Protocol. Add the
 remote URL and complete OAuth 2.1 in the browser. API-key fallback is
 client-specific. ChatGPT custom apps require OAuth and cannot present custom
 API keys.
@@ -11,7 +11,7 @@ API keys.
 | Endpoint | `https://xquik.com/mcp` |
 | Authentication | OAuth 2.1 discovery; API key fallback |
 | Hosted MCP version | `2.6.0` |
-| Skill bundle version | `2.6.4` |
+| Skill bundle version | `2.6.7` |
 
 Current clients negotiate MCP `2026-07-28` through `server/discover`.
 Use a current MCP SDK. It adds request `_meta` and protocol headers.
@@ -25,10 +25,10 @@ Xquik publishes these discovery documents:
 - Protected resource metadata: `https://xquik.com/.well-known/oauth-protected-resource/mcp`
 - Authorization server metadata: `https://xquik.com/.well-known/oauth-authorization-server`
 - MCP registry card: `https://xquik.com/.well-known/mcp/server-card.json`
-- Agent-readable auth guide: `https://xquik.com/auth.md`
+- Authentication guide: `https://xquik.com/auth.md`
 
-Xquik supports Client ID Metadata Documents (CIMD) and Dynamic Client
-Registration (DCR). Let each client use its documented registration flow. Both
+Xquik supports Client ID Metadata Documents and Dynamic Client Registration.
+Let each client use its documented registration flow. Both
 use Authorization Code with S256 PKCE and the `mcp:tools` scope.
 
 Use the [canonical client compatibility matrix](https://docs.xquik.com/mcp/overview#client-compatibility)
@@ -36,7 +36,7 @@ for current per-client support. Cline and Qwen Code support OAuth.
 Affected Goose releases need an environment-backed API key. Roo Code's archived final
 release is API-key-only. Pi has no native MCP client.
 
-> **Security:** Start OAuth from the MCP client. Do not open Xquik login routes
+> Start OAuth from the MCP client. Do not open Xquik login routes
 > directly. Do not proxy Xquik credentials through local bridge packages or
 > command-line adapters. If OAuth is unavailable, keep API keys in the client's
 > secure secret store and never commit them.
@@ -84,13 +84,8 @@ tools only. Custom MCP apps are web-only.
 
 ### Codex CLI
 
-Current Codex releases affected by
-[openai/codex#31573](https://github.com/openai/codex/issues/31573) must use the
-environment-backed API-key configuration in **Codex Config** below. Do not run
-`codex mcp login xquik` while that configuration is active.
-
-After your Codex release includes the upstream issuer fix, remove
-`bearer_token_env_var`, then run:
+Use Codex CLI 0.147.0 or later. These releases preserve and validate the RFC
+9207 `iss` callback value. Run:
 
 ```bash
 codex mcp add xquik --url https://xquik.com/mcp
@@ -98,22 +93,21 @@ codex mcp login xquik
 codex mcp list
 ```
 
-Affected releases discard the RFC 9207 `iss` callback value and fail before
-token exchange. If login reports
+If an older release reports
 `Authorization server response missing required issuer: expected https://xquik.com`,
-Xquik already returns the required issuer. Follow the [Xquik troubleshooting guide](https://docs.xquik.com/guides/troubleshooting#codex-oauth-issuer-validation-error).
+upgrade to 0.147.0 or later. If an upgrade is unavailable, use the API-key
+fallback below. Xquik already returns the required issuer. Follow the
+[Xquik troubleshooting guide](https://docs.xquik.com/guides/troubleshooting#codex-oauth-issuer-validation-error).
 
 ### Codex Desktop
 
-Current affected releases use the environment-backed API-key configuration
-below through the shared `config.toml`, then restart Codex Desktop. After your
-release includes the upstream fix, open **Settings > MCP servers**, add
-`https://xquik.com/mcp` as Streamable HTTP, select **Authenticate**, then
-restart.
+Open **Settings > MCP servers**. Add `https://xquik.com/mcp` as Streamable HTTP,
+select **Authenticate**, then restart. If the app bundles a Codex release older
+than 0.147.0 and shows the issuer error above, use the shared `config.toml`
+fallback below.
 
-### Codex Config
+### API-key fallback for older Codex releases
 
-Current affected releases need an environment-backed API key instead of OAuth.
 Load `XQUIK_API_KEY` from your password manager or operating-system secret
 store. Do not type the key into a shell command, save it in shell history, or
 put it in `config.toml`.
@@ -129,9 +123,8 @@ bearer_token_env_var = "XQUIK_API_KEY"
 Restart Codex, then run `codex mcp list`. Do not run `codex mcp login xquik`
 while using the API-key configuration.
 
-After your Codex release includes the upstream fix, remove
-`bearer_token_env_var` so the entry contains only the MCP URL, then run
-`codex mcp login xquik`.
+After upgrading to 0.147.0 or later, remove `bearer_token_env_var`. Leave only
+the MCP URL, then run `codex mcp login xquik`.
 
 ### OpenAI Agents SDK
 
@@ -160,7 +153,7 @@ async def run_xquik(api_key: str) -> str:
         return str(result.final_output)
 ```
 
-## Editors and Terminals
+## Editor and terminal clients
 
 ### Cursor
 
@@ -275,18 +268,19 @@ save. This interactive path works across Copilot CLI command variants.
 In an interactive Copilot CLI session, run `/mcp auth xquik`. Enterprise policy
 may block servers that are not on the organization allowlist.
 
-## API-Key Fallback
+## API key fallback
 
 Use this only when the client cannot complete OAuth and documents a secure
 secret-input or environment-variable mechanism. ChatGPT custom apps cannot use
-this fallback. Codex uses the `bearer_token_env_var` configuration above.
-Client schemas and environment syntax differ, so do not copy a generic header
+this fallback. Older Codex releases use the `bearer_token_env_var` configuration
+above.
+Client schemas and environment syntax differ, so do not copy one header
 object between clients or place a literal key in a configuration file.
 
 Full account keys expose 120 catalog routes. Of these, 119 support JSON or text.
 Active guest `paid_reads` keys expose 33 eligible GET routes.
 
-## MCP Server Architecture
+## MCP server architecture
 
 Hosted MCP v2.6.0 exposes 120 catalog routes through 2 structured API tools.
 Of these, 119 support JSON or text. Binary support downloads use REST.
@@ -296,7 +290,7 @@ Of these, 119 support JSON or text. Binary support downloads use REST.
 | `explore` | Search the API endpoint catalog (read-only, no network calls) | Included |
 | `xquik` | Send confirmed Xquik API requests | Varies by endpoint |
 
-`explore` searches the credential-scoped catalog. `xquik` executes authenticated
+`explore` searches the credential-scoped catalog. `xquik` sends authenticated
 operations with normalized snake_case responses. Authentication is injected, so
 tool code must never include credentials.
 
@@ -312,10 +306,10 @@ Private reads, writes, monitors, webhooks, persistent resources, and metered bul
 jobs require the user's explicit approval. Plan and credit changes stay
 dashboard-only.
 
-## After Setup
+## After setup
 
 Use `explore` before unfamiliar operations. Use `xquik` only for the narrowest
-confirmed request.
+approved request.
 
 | Workflow | Steps |
 |----------|-------|
@@ -328,7 +322,7 @@ confirmed request.
 Handle failures from structured error fields:
 
 - `401`: reconnect OAuth or replace the revoked API key.
-- `402`: report payment options. Never create checkout without confirmation.
+- `402`: explain the account state and direct the user to the dashboard.
 - `409 coverage_cursor_unavailable`: wait the exact `Retry-After` seconds, then retry the same cursor once.
 - `410 coverage_cursor_gone`: no `Retry-After`; restart without a cursor and deduplicate by ID.
 - `429`: honor `Retry-After`.