x-developer 2.6.7 → 2.7.1

package/skills/x-twitter-scraper/references/api-endpoints-drafts.md

@@ -1,105 +0,0 @@
-# Xquik REST API endpoints: drafts
-
-## Require approval for drafts
-
-`GET` operations expose private saved content. State the exact draft scope and
-obtain explicit approval immediately before each read. `POST` and `DELETE`
-operations are non-default writes. Show the exact draft text or draft ID and
-obtain explicit approval immediately before each write. Never infer approval
-from an earlier request or retry a failed write automatically.
-
-### Create draft
-
-`POST /drafts`
-
-Save a tweet draft for later.
-
-Get approval first. Preview the complete text and metadata. Create the draft
-only after the user explicitly approves that exact payload.
-
-Send this request body:
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| `text` | string | Yes | The draft tweet text |
-| `topic` | string | No | Topic the tweet is about |
-| `goal` | string | No | `engagement`, `followers`, `authority`, or `conversation` |
-
-For a 201 response, the API returns:
-
-```json
-{
-  "id": "123",
-  "text": "draft text",
-  "topic": "product launch",
-  "goal": "engagement",
-  "createdAt": "2026-02-24T10:30:00.000Z",
-  "updatedAt": "2026-02-24T10:30:00.000Z"
-}
-```
-
----
-
-### List drafts
-
-`GET /drafts`
-
-List saved tweet drafts with cursor pagination.
-
-This is a private read. Show the requested page size and account scope. List drafts
-only after explicit approval for that exact read.
-
-Use these query parameters:
-
-| Parameter | Type | Required | Default | Description |
-|-----------|------|----------|---------|-------------|
-| `limit` | number | No | 50 | Results per page; maximum 50 |
-| `afterCursor` | string | No | - | Pagination cursor from previous response |
-
-For a 200 response, the API returns:
-
-```json
-{
-  "drafts": [
-    {
-      "id": "123",
-      "text": "draft text",
-      "topic": "product launch",
-      "goal": "engagement",
-      "createdAt": "2026-02-24T10:30:00.000Z",
-      "updatedAt": "2026-02-24T10:30:00.000Z"
-    }
-  ],
-  "afterCursor": "cursor_string",
-  "hasMore": true
-}
-```
-
----
-
-### Get draft
-
-`GET /drafts/{id}`
-
-Get a specific draft by ID.
-
-This is a private read. Show the draft ID. Fetch it only after explicit approval for
-that exact read, including any preview before deletion.
-
-For a 200 response, the API returns 1 draft object.
-
-Possible errors include `400 invalid_id` and `404 draft_not_found`.
-
----
-
-### Delete draft
-
-Send a delete request to `/drafts/{id}`.
-
-This action is destructive. Deletion is permanent and cannot be recovered through
-this API. Show the draft ID and text, then obtain explicit approval immediately
-before deleting it. Returns `204 No Content`.
-
-Possible errors include `400 invalid_id` and `404 draft_not_found`.
-
----

package/skills/x-twitter-scraper/references/api-endpoints-draws.md

@@ -1,101 +0,0 @@
-# Xquik REST API endpoints: draws
-
-## Protect giveaway participant data
-
-Draw creation and participant exports are metered or privacy-sensitive actions.
-Confirm the source tweet, eligibility rules, requested data type, export
-audience, and retention plan. Use the smallest necessary dataset. Do not
-export entries for surveillance, discrimination, harassment, or unrelated
-secondary use.
-Draw history and results are account-scoped private reads. Require exact-scope
-approval before listing draws or retrieving winners.
-
-### Create draw
-
-```
-POST /draws
-```
-
-Run a giveaway draw from a tweet. The draw selects random winners from replies.
-
-Get approval first. Show the source tweet, winner count, backup count,
-filters, and estimated usage. Also show the lawful purpose, participant-data
-handling, export audience, and retention plan. Record every field before
-persisting participant data.
-
-Send this body:
-```json
-{
-  "tweetUrl": "https://x.com/user/status/1893456789012345678",
-  "winnerCount": 3,
-  "backupCount": 2,
-  "uniqueAuthorsOnly": true,
-  "mustRetweet": true,
-  "mustFollowUsername": "burakbayir",
-  "filterMinFollowers": 100,
-  "filterAccountAgeDays": 30,
-  "filterLanguage": "en",
-  "requiredKeywords": ["giveaway"],
-  "requiredHashtags": ["#contest"],
-  "requiredMentions": ["@xquik"]
-}
-```
-
-All filter fields are optional. Only `tweetUrl` is required.
-
-The API returns:
-```json
-{
-  "id": "42",
-  "tweetId": "1893456789012345678",
-  "tweetUrl": "https://x.com/user/status/1893456789012345678",
-  "tweetText": "Like and repost to enter. We will select 3 winners tomorrow.",
-  "tweetAuthorUsername": "xquik",
-  "tweetLikeCount": 4200,
-  "tweetRetweetCount": 1800,
-  "tweetReplyCount": 1500,
-  "tweetQuoteCount": 120,
-  "status": "completed",
-  "totalEntries": 1500,
-  "validEntries": 890,
-  "createdAt": "2026-02-24T10:00:00.000Z",
-  "drawnAt": "2026-02-24T10:01:00.000Z"
-}
-```
-
-### List draws
-
-```
-GET /draws
-```
-
-Cursor-paginated. Returns compact draw objects.
-
-This is a private read. Show the exact account, requested page scope, and returned
-field scope. List draws only after explicit approval for that exact read.
-
-### Get draw
-
-```
-GET /draws/{id}
-```
-
-Returns full draw details including winners.
-
-This is a private read. Show the exact account, draw ID, and returned-data scope.
-Retrieve details only after explicit approval for that exact read.
-
-### Export draw
-
-```
-GET /draws/{id}/export?format=csv&type=winners
-```
-
-Choose `csv`, `json`, `md`, `md-document`, `pdf`, `txt`, or `xlsx`. Choose `winners` or `entries`; the default is `winners`. Entry exports support 100,000 rows, except PDF supports 10,000.
-
-Get approval first. Full entry exports can contain participant identity and
-activity data. Show the lawful purpose, exact draw, type, format, audience, and
-retention period. Export only after explicit approval for that exact request.
-Prefer winners-only output. Do not retain data beyond the approved purpose.
-
----

package/skills/x-twitter-scraper/references/api-endpoints-error-codes.md

@@ -1,67 +0,0 @@
-# Xquik REST API endpoints: error codes
-
-Default v1 responses put a legacy string code in `error`. Send
-`xquik-api-contract: 2026-04-29` to receive an object with `message`, `type`,
-and `code`. OpenAPI enumerates 112 codes, including `closed`, `expired`,
-`missing_url`, and `user_not_found`. This table highlights common codes.
-`closed` and `expired` map to 410. `missing_url` maps to 502.
-
-| Status | Code | Meaning |
-|--------|------|---------|
-| 400 | `invalid_input` | Request body failed validation |
-| 400 | `invalid_id` | Path parameter is not a valid ID |
-| 400 | `invalid_json` | Invalid JSON in request body |
-| 400 | `invalid_tweet_url` | Tweet URL format is invalid |
-| 400 | `invalid_tweet_id` | Tweet ID is empty or invalid |
-| 400 | `invalid_username` | X username is empty or invalid |
-| 400 | `invalid_tool_type` | Extraction tool type not recognized |
-| 400 | `invalid_format` | Export format not `csv`, `json`, `md`, `md-document`, `pdf`, `txt`, or `xlsx` |
-| 400 | `invalid_params` | Export query parameters are missing or invalid |
-| 400 | `invalid_coverage_cursor` | Automatic coverage cursor is malformed. Restart without it |
-| 400 | `missing_query` | Required query parameter is missing |
-| 400 | `missing_params` | Required query parameters are missing |
-| 400 | `no_media` | Tweet has no downloadable media |
-| 400 | `webhook_inactive` | Webhook is disabled; applies only to webhook tests |
-| 401 | `unauthenticated` | Missing or invalid API key |
-| 403 | `account_needs_reauth` | X account session expired; use dashboard re-auth flow |
-| 402 | `no_subscription` | No active plan |
-| 402 | `subscription_inactive` | Plan is not active |
-| 402 | `no_credits` | No credit balance record exists |
-| 402 | `insufficient_credits` | Credit balance is too low |
-| 403 | `api_key_limit_reached` | API key limit reached; maximum 100 |
-| 404 | `not_found` | Resource does not exist |
-| 404 | `user_not_found` | X user not found |
-| 404 | `tweet_not_found` | Tweet not found |
-| 404 | `style_not_found` | No cached style found |
-| 404 | `draft_not_found` | Draft not found |
-| 409 | `monitor_already_exists` | Duplicate monitor for same username |
-| 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 |
-| 422 | `login_failed` | Account connection failed; use dashboard re-auth flow |
-| 429 | - | Rate limited. Retry with backoff |
-| 429 | `x_api_rate_limited` | X data source rate limited. Retry |
-| 500 | `internal_error` | Server error |
-| 502 | `x_api_unavailable` | X data source temporarily unavailable |
-| 502 | `x_api_unauthorized` | X data source authentication failed. Retry |
-
-## Cursor recovery examples
-
-`409 coverage_cursor_unavailable` requires an integer `Retry-After` response
-header. Wait that many seconds, then retry the same cursor once.
-
-```json
-{
-  "error": "coverage_cursor_unavailable",
-  "message": "Cursor busy. Retry after the indicated delay."
-}
-```
-
-`410 coverage_cursor_gone` has no `Retry-After` header. Restart without a
-cursor and deduplicate by ID.
-
-```json
-{
-  "error": "coverage_cursor_gone",
-  "message": "Cursor finished, expired, or superseded. Restart pagination without cursor."
-}
-```

package/skills/x-twitter-scraper/references/api-endpoints-events.md

@@ -1,50 +0,0 @@
-# Xquik REST API endpoints: events
-
-### List events
-
-```
-GET /events
-```
-
-Use these query parameters:
-
-| Parameter | Type | Description |
-|-------|------|-------------|
-| `monitorId` | string | Filter by monitor ID |
-| `keywordMonitorId` | string | Filter by keyword monitor ID |
-| `eventType` | string | Filter by event type |
-| `limit` | number | Results per page from 1-100; defaults to 50 |
-| `cursor` | string | Previous `nextCursor` |
-
-The API returns:
-```json
-{
-  "events": [
-    {
-      "id": "9010",
-      "type": "tweet.new",
-      "monitorId": "7",
-      "monitorType": "account",
-      "username": "elonmusk",
-      "occurredAt": "2026-02-24T16:45:00.000Z",
-      "data": {
-        "tweetId": "1893556789012345678",
-        "text": "Hello world",
-        "metrics": { "likes": 3200, "retweets": 890, "replies": 245 }
-      }
-    }
-  ],
-  "hasMore": true,
-  "nextCursor": "MjAyNi0wMi0yNFQxNjozMDowMC4wMDBa..."
-}
-```
-
-### Get event
-
-```
-GET /events/{id}
-```
-
-Returns 1 event.
-
----

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

@@ -1,113 +0,0 @@
-# Xquik REST API endpoints: extractions
-
-## Protect extracted data
-
-Extraction creation and export can collect and disclose large datasets. First
-confirm the lawful purpose, exact target, `resultsLimit`, recipients, and
-retention period. Estimate usage, show the estimate, and obtain explicit
-approval for that exact bounded job. Never use extraction for private data,
-surveillance, discrimination, harassment, doxxing, or unrelated secondary use.
-Extraction history and results are account-scoped private reads. Require
-exact-scope approval before listing jobs or retrieving results.
-
-### Create extraction
-
-```
-POST /extractions
-```
-
-Run a bulk data extraction job. See `references/extractions.md` for all 23 tools.
-
-Get approval first. Call the estimate endpoint with the same body first.
-Create the job only when the estimate returns `allowed: true`. Then require
-approval for the target, bound, usage, and data-handling plan.
-
-Send this body:
-```json
-{
-  "toolType": "reply_extractor",
-  "targetTweetId": "1893704267862470862",
-  "resultsLimit": 500
-}
-```
-
-The API accepts an omitted `resultsLimit`. This Skill must always send an
-explicit finite positive bound. The bound stops early and limits usage.
-
-The request accepts single or batch targets, mixed targets, relation targets,
-deduplication controls, output metadata, and current result filters. See
-[Extraction Tools](extractions.md) and the OpenAPI schema. Send the same body
-to estimate and create.
-
-The API returns:
-```json
-{
-  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
-  "toolType": "reply_extractor",
-  "status": "running"
-}
-```
-
-### Estimate extraction
-
-```
-POST /extractions/estimate
-```
-
-Preview usage before running. Same body as create.
-
-The API returns:
-```json
-{
-  "allowed": true,
-  "creditsAvailable": "50000",
-  "creditsRequired": "150",
-  "source": "replyCount",
-  "estimatedResults": 150
-}
-```
-
-### List extractions
-
-```
-GET /extractions
-```
-
-Cursor-paginated. Use `limit`, `cursor`, `status`, and `toolType`. Pass each
-`nextCursor` unchanged while `hasMore` is true.
-
-This is a private read. Show the exact account, purpose, requested filters, and page
-scope. Also show recipients and the retention plan. List jobs only
-after explicit approval for that exact read.
-
-### Get extraction
-
-```
-GET /extractions/{id}
-```
-
-Returns job details with up to 1,000 results per page.
-Use `limit` and `cursor`. Optional result-shaping parameters are `outputMode`,
-`outputPreset`, and `fieldStyle`. `includeRaw` is deprecated.
-
-This is a private read. Show the exact account, job ID, purpose, and page scope. Also
-show recipients and the retention plan. Retrieve results only after
-explicit approval for that exact read.
-
-### Export extraction
-
-```
-GET /extractions/{id}/export?format=csv
-```
-
-Choose `csv`, `json`, `md`, `md-document`, `pdf`, `txt`, or `xlsx`.
-Exports can include enrichment columns not present in paginated API results.
-
-Use documented row filters for follower, following, post, engagement, profile,
-media, language, search, and date fields. The endpoint does not project fields.
-
-Get approval first. Show the job, filters, format, row count, schema,
-recipients, storage, and retention. Create or send the export only
-after explicit approval.
-
----

package/skills/x-twitter-scraper/references/api-endpoints-monitors.md

@@ -1,111 +0,0 @@
-# Xquik REST API endpoints: monitors
-
-## Require approval for monitors
-
-Monitor reads expose private configuration and require exact-scope approval.
-Creating, updating, enabling, disabling, or deleting a monitor changes a
-persistent and potentially metered resource.
-Before every write, show the exact account or keyword, event types, delivery
-plan, ongoing usage, and disable path. If delivery uses a webhook, show its
-exact URL and HMAC verification plan. Proceed only after explicit approval for
-that exact action. Never create monitoring from an ambiguous request.
-
-### Create monitor
-
-```http
-POST /monitors
-```
-
-Get approval first. This starts persistent monitoring. Confirm the exact
-username, event types, delivery plan, ongoing usage, and disable path first.
-Include the exact URL and HMAC verification plan for webhook delivery.
-
-Send this body:
-```json
-{
-  "username": "elonmusk",
-  "eventTypes": ["tweet.new", "tweet.reply", "tweet.quote"]
-}
-```
-
-The API returns:
-```json
-{
-  "id": "7",
-  "username": "elonmusk",
-  "xUserId": "44196397",
-  "eventTypes": ["tweet.new", "tweet.reply", "tweet.quote"],
-  "isActive": true,
-  "createdAt": "2026-02-24T10:30:00.000Z",
-  "nextBillingAt": "2026-02-24T10:30:00.000Z"
-}
-```
-
-Event types include tweet activity and profile-change events. Use the OpenAPI
-`EventType` enum for the current values. `webhook.test` is only a test payload.
-
-Returns `409 monitor_already_exists` if the username is already monitored.
-
-### List monitors
-
-```
-GET /monitors
-```
-
-Returns up to 200 monitors without pagination. The response includes `monitors` and `total`.
-
-This is a private read. List monitor targets and delivery configuration only after
-explicit approval for that account scope.
-
-### Get monitor
-
-```http
-GET /monitors/{id}
-```
-
-This is a private read. Show the monitor ID. Retrieve its configuration only after
-explicit approval for that exact read.
-
-### Update monitor
-
-```http
-PATCH /monitors/{id}
-```
-
-Get approval first. Show the current and proposed event types and active
-state. Apply only the explicitly approved change.
-
-Send `{ "eventTypes": [...], "isActive": true|false }`. Both fields are optional.
-
-### Delete monitor
-
-```
-DELETE /monitors/{id}
-```
-
-This action is destructive. This permanently stops tracking and deletes associated
-monitor data. Show the monitor ID, target, and lost data. Delete only after
-explicit approval immediately before the call.
-
-### Keyword monitors
-
-```
-GET /monitors/keywords
-POST /monitors/keywords
-GET /monitors/keywords/{id}
-PATCH /monitors/keywords/{id}
-DELETE /monitors/keywords/{id}
-```
-
-Create and manage ongoing keyword monitors. They are persistent resources. Confirm the query, event delivery, and ongoing usage before creating or enabling one.
-
-Create with `{ "query": "#buildinpublic", "eventTypes": ["tweet.new"] }`.
-Poll its events with `GET /events?keywordMonitorId=<id>`.
-
-Creating, updating, enabling, disabling, or deleting a keyword monitor requires
-explicit approval for the exact monitor. For creates and updates, show the
-proposed keyword, event types, and delivery changes. For enable or disable,
-show the active-state transition. For deletion, show the exact target and all
-associated data that will be permanently lost.
-
----

package/skills/x-twitter-scraper/references/api-endpoints-radar.md

@@ -1,50 +0,0 @@
-# Xquik REST API endpoints: radar
-
-### List radar items
-
-```
-GET /radar
-```
-
-Get trending topics and news from supported trend and news sources.
-
-Use these query parameters:
-
-| Parameter | Type | Description |
-|-------|------|-------------|
-| `after` | string | Previous `nextCursor` |
-| `source` | string | `github`, `google_trends`, `hacker_news`, `polymarket`, `reddit`, `trustmrr`, or `wikipedia` |
-| `category` | string | `general`, `tech`, `dev`, `science`, `culture`, `politics`, `business`, or `entertainment` |
-| `limit` | number | Items per page from 1-100; defaults to 50 |
-| `hours` | number | Look-back window from 1-72 hours; defaults to 6 |
-| `region` | string | `US`, `GB`, `TR`, `ES`, `DE`, `FR`, `JP`, `IN`, `BR`, `CA`, `MX`, or `global`; defaults to `global` |
-
-The API returns:
-```json
-{
-  "items": [
-    {
-      "id": "12345",
-      "title": "Claude 4.6 released",
-      "description": "Anthropic releases Claude 4.6.",
-      "url": "https://example.com/article",
-      "imageUrl": "https://example.com/image.png",
-      "source": "hacker_news",
-      "sourceId": "hn_12345",
-      "category": "tech",
-      "region": "global",
-      "language": "en",
-      "score": 450,
-      "metadata": { "points": 450, "numberComments": 132, "author": "pgdev" },
-      "publishedAt": "2026-03-05T10:00:00.000Z",
-      "createdAt": "2026-03-05T10:05:00.000Z"
-    }
-  ],
-  "hasMore": true,
-  "nextCursor": "NDUwfDIwMjYtMDMtMDRUMDg6MzA6MDAuMDAwWnwxMjM0NQ=="
-}
-```
-
-Each item contains `id`, `title`, `source`, `sourceId`, `category`, `region`, `language`, `score`, `metadata`, `publishedAt`, and `createdAt`. It may include `description`, `url`, and `imageUrl`. The response also returns `hasMore` and `nextCursor`.
-
----

package/skills/x-twitter-scraper/references/api-endpoints-support.md

@@ -1,53 +0,0 @@
-# Xquik REST API endpoints: support
-
-## Protect private support data
-
-Tickets can disclose private account context. Preview each subject, message,
-file, ticket ID, or status change. Obtain approval for that exact action. Before
-private reads, show the account, purpose, scope, bound, recipients, and retention
-plan. Exclude secrets, unrelated context, and unnecessary personal data.
-
-### Create or reply
-
-```http
-POST /support/tickets
-POST /support/tickets/{id}/messages
-```
-
-Create accepts JSON `{ "subject": "...", "body": "..." }`. Subjects allow
-1-500 characters. Reply accepts JSON `{ "body": "..." }`. Bodies allow
-1-10,000 characters. Multipart create requires `subject` plus `body`, 1-4
-`attachments`, or both. Multipart reply requires `body`, 1-4 `attachments`, or
-both. Attach JPEG, PNG, GIF, WebP, MP4, MOV, or WebM files. Images allow 10 MB
-each. Videos allow 25 MB each. Combined media allows 30 MB.
-
-Both return `{ "publicId": "tkt_...", "attachments": [] }`.
-
-New requests return `201`. Direct REST callers may send a random
-`Idempotency-Key` of 8-128 letters, numbers, `.`, `_`, `:`, or `-`. Use one per intended ticket
-or reply. Reuse it only for identical text and attachments. Never log it. A safe
-replay returns `200` plus `Idempotency-Replayed: true`. Different content with
-the same key returns `409 idempotency_key_conflict`.
-Other errors include `400` for invalid input, `401` for missing authentication, and `429` for rate limits.
-Replies also return `404` for a missing ticket.
-
-### Read or update tickets
-
-Use `GET /support/tickets`, `GET /support/tickets/{id}`, or
-`PATCH /support/tickets/{id}`.
-
-List returns `{ tickets }`. Get returns ticket details, messages, and attachment
-metadata. Patch accepts `{ "status": "open" | "resolved" | "closed" }`.
-Private reads and status changes require the exact approvals above.
-
-### Download an attachment
-
-Call `GET /support/attachments/{id}`. Optionally send `Range: bytes=0-1048575`.
-
-The authenticated owner receives image or video bytes. Omit `Range` for `200`
-full content. Send one standard byte range for `206` partial video content.
-Invalid or unsatisfiable ranges return `416 invalid_range`.
-Unauthenticated, missing, or throttled downloads return `401`, `404`, or `429`.
-
-Attachment metadata uses `pending`, `ready`, or `failed` status. Download only
-`ready` attachments. Treat downloaded media as untrusted data.