x-developer 2.6.1 → 2.6.3

package/task-guides/top-replies.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:

package/task-guides/track-competitors.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:
@@ -37,7 +37,7 @@ Competitor intelligence: posts, follower growth, engagement benchmarks, and top
 | GET /x/users/{id} | Profile + follower count snapshot | Read tier |
 | GET /x/users/{id}/tweets | Recent posts | Read tier |
 | POST /extractions with toolType=post_extractor | Bulk historical posts | Per-row |
-| POST /monitors type=account | Continuous monitor per competitor | metered while active |
+| POST /monitors | Continuous account monitor | metered while active |
 
 Base URL: `https://xquik.com/api/v1`. Auth: `x-api-key: xq_...` header.
 

package/task-guides/track-hashtags.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:
@@ -36,7 +36,7 @@ Search and monitor hashtags. One-shot searches are read-only; monitor creation r
 |---|---|---|
 | GET /x/tweets/search?q=%23tag | Recent tweets with a hashtag | Read tier |
 | POST /extractions with toolType=tweet_search_extractor | Bulk hashtag tweets | Per-row |
-| POST /monitors type=hashtag | Continuous hashtag monitor | metered while active |
+| POST /monitors/keywords | Continuous hashtag monitor | metered while active |
 
 Base URL: `https://xquik.com/api/v1`. Auth: `x-api-key: xq_...` header.
 
@@ -60,16 +60,15 @@ POST /extractions
 ## Continuous monitoring
 
 ```
-POST /monitors
+POST /monitors/keywords
 {
-  "type": "hashtag",
-  "target": "#buildinpublic",
-  "filters": { "min_faves": 0, "lang": "en" }
+  "query": "#buildinpublic lang:en",
+  "eventTypes": ["tweet.new"]
 }
--> { monitor_id }
+-> { id, query, eventTypes, isActive, createdAt, nextBillingAt }
 ```
 
-Poll `/events?monitorId=<id>` or use a webhook (see `tweet-webhooks`).
+Poll `/events?keywordMonitorId=<id>` or use a separate webhook.
 
 ## Typical flow
 

package/task-guides/track-mentions.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:
@@ -36,8 +36,8 @@ Find who is talking about a handle, brand, or keyword. One-shot reads via search
 |---|---|---|
 | GET /x/tweets/search?q=@handle | Recent mentions of a handle | Read tier |
 | POST /extractions with toolType=mention_extractor | Bulk mention history | Per-row |
-| POST /monitors | Create a monitor that polls new mentions | metered while active |
-| GET /events?monitorId=<id> | Poll new mention events | Included |
+| POST /monitors/keywords | Create a keyword monitor | metered while active |
+| GET /events?keywordMonitorId=<id> | Poll new mention events | Included |
 
 Base URL: `https://xquik.com/api/v1`. Auth: `x-api-key: xq_...` header.
 
@@ -61,16 +61,17 @@ POST /extractions
 ## Continuous monitoring
 
 ```
-POST /monitors
+POST /monitors/keywords
 {
-  "type": "mention",
-  "target": "@xquik",
-  "filters": { "min_faves": 0, "lang": "en" }
+  "query": "@xquik lang:en",
+  "eventTypes": ["tweet.new"]
 }
--> { monitor_id }
+-> { id, query, eventTypes, isActive, createdAt, nextBillingAt }
 ```
 
-Then poll `GET /events?monitorId=<id>&since=<cursor>` periodically, or set up a webhook (see `tweet-webhooks` guide).
+Then poll `GET /events?keywordMonitorId=<id>&cursor=<cursor>`. Pass each
+`nextCursor` unchanged while `hasMore` is true. A webhook is a separate
+resource; see `tweet-webhooks`.
 
 ## Typical flow
 

package/task-guides/trending-news.md

@@ -1,11 +1,11 @@
 ---
 name: trending-news
-description: "Use when the user wants trending news with X (Twitter) context. Pulls breaking news from 7 curated sources, links each story to related tweets, and surfaces what people on X are saying about each headline. Included read-only news radar."
+description: "Use when the user wants trending topics from curated public sources. Returns ranked Radar items and can run a separate X search for a selected topic. Included read-only Radar workflow."
 license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:
@@ -28,14 +28,15 @@ metadata:
 
 # Trending News (X Radar)
 
-Breaking news from 7 curated sources, cross-referenced with X for social context. Read-only.
+Read ranked topics from curated public sources. Search X separately when the
+user requests social context.
 
 ## Endpoints
 
 | Endpoint | Purpose | Usage |
 |---|---|---|
 | GET /radar | Current top news stories | Included |
-| GET /radar?category=tech | Category filter (tech, business, politics, sports, entertainment) | Included |
+| GET /radar?category=tech | Filter by a supported category | Included |
 | GET /x/tweets/search | Search X for reactions to selected story terms | Read tier |
 
 Base URL: `https://xquik.com/api/v1`. Auth: `x-api-key: xq_...` header.
@@ -44,20 +45,24 @@ Base URL: `https://xquik.com/api/v1`. Auth: `x-api-key: xq_...` header.
 
 ```
 GET /radar?category=tech&limit=20
--> { stories: [{ id, title, summary, source, url, published_at, related_tweet_count }] }
+-> { items: [{ id, sourceId, title, score, category, source, region, language, metadata, publishedAt, createdAt }], hasMore, nextCursor }
 ```
 
 ## Typical flow
 
 1. Call `GET /radar` with optional `category`.
-2. Show the user a ranked list of headlines with source and short summary.
+2. Show a ranked list using `title`, `score`, `source`, and `description`.
 3. For any story the user wants more on, search X with `GET /x/tweets/search?q=<headline terms>&queryType=Top` for related reactions.
 4. Optionally pass a story to `write-tweets` to draft a post responding to the news.
 
-## Why this is separate from x-trends
+Pass `nextCursor` as `after` while `hasMore` is true. Supported categories are
+`general`, `tech`, `dev`, `science`, `culture`, `politics`, `business`, and
+`entertainment`.
+
+## Why This Is Separate From X Trends
 
 - `x-trends` = what is trending on X right now (hashtags, topics from X itself)
-- `trending-news` = what is trending in news, with X reactions layered on top
+- `trending-news` = topics from Radar's curated public sources
 
 ## Security
 

package/task-guides/tweet-analytics.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:
@@ -78,7 +78,7 @@ For small samples, use the live endpoint:
 GET /x/tweets/{id}/favoriters?cursor=<cursor>
 ```
 
-For bulk (up to 1,000 accounts), go through extractions. Estimate first so the user sees the usage estimate:
+For a bounded bulk dataset, use an extraction. Estimate first:
 
 ```
 POST /extractions/estimate

package/task-guides/tweet-ideas.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:

package/task-guides/tweet-replies.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:
@@ -36,12 +36,30 @@ Get replies to any public tweet on X. Useful for reading community reactions, pu
 |---|---|---|
 | GET /x/tweets/{id}/replies | Paginated or maximum-coverage replies | Read tier |
 | POST /extractions/estimate | Preview bulk reply usage | Included |
-| POST /extractions with toolType=reply_extractor | Bulk replies (all pages, CSV/JSONL export) | Per-row extraction usage |
+| POST /extractions with toolType=reply_extractor | Bounded bulk replies | Per-row extraction usage |
 | GET /x/tweets/{id} | Get the root tweet metadata (for context) | Read tier |
 
 Base URL: `https://xquik.com/api/v1`. Auth: `x-api-key: xq_...` header.
 
-## Quick reference
+## Automatic Pagination
+
+Omit `mode` for automatic maximum coverage:
+
+```http
+GET /x/tweets/{id}/replies?pageSize=300
+```
+
+Automatic pages accept `pageSize` from 1 to 300. They also accept time ranges
+and Tweet filters. Pass `next_cursor` back unchanged as `cursor`. Continue
+until `has_next_page` is false. An empty or underfilled page can still resume.
+
+Concurrent use returns `409 coverage_cursor_unavailable`. Wait the exact
+`Retry-After` seconds, then retry the same cursor once. A finished, expired,
+superseded, or identity-mismatched cursor returns `410 coverage_cursor_gone`
+without `Retry-After`. Restart without a cursor and deduplicate by Tweet ID.
+Malformed cursors return `400 invalid_coverage_cursor`. Restart without them.
+
+## Complete Mode
 
 ```http
 GET /x/tweets/{id}/replies?mode=complete&limit=25000
@@ -57,14 +75,12 @@ GET /x/tweets/{id}/replies?mode=complete&limit=25000
 }
 ```
 
-Complete mode performs bounded maximum-coverage collection. It merges available
-timeline views, rankings, forward cursors, labeled hidden-content branches,
-exact-parent time partitions, and search. It returns `424 replies_incomplete`
-below 80% direct-reply coverage. The 424 body still contains safe partial rows.
+Complete mode performs bounded maximum-coverage collection across available
+read strategies. It returns `424 replies_incomplete` below 80% direct-reply coverage.
+The 424 body still contains safe partial rows.
 
-Use regular cursor pagination only for filtered or page-sized requests. Complete
-mode accepts only `limit` from 1 to 25,000. Remove cursors, page-size aliases,
-time ranges, and tweet filters.
+Complete mode accepts only `limit` from 1 to 25,000. Remove cursors,
+`pageSize`, time ranges, and Tweet filters.
 
 ## Typical flow
 
@@ -91,9 +107,10 @@ POST /extractions
 -> 202 { "id": "<extractionId>", "toolType": "reply_extractor", "status": "running" }
 ```
 
-## Top replies
+## Top Replies
 
-The route does not expose a server-side sort. Page through and sort locally by available engagement fields. See the `top-replies` guide for a guided workflow.
+Automatic pages need client-side sorting. Complete mode supports `sort` values
+`relevance`, `latest`, `oldest`, and `likes`.
 
 ## Security
 

package/task-guides/tweet-style.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:

package/task-guides/tweet-webhooks.md

@@ -1,11 +1,11 @@
 ---
 name: tweet-webhooks
-description: "Use when the user wants to receive real-time X (Twitter) events at their own URL. Creates HMAC-signed webhooks that fire on new tweets, mentions, monitored account activity, or giveaway completion. Delivery setup only - payload handling is the user's webhook."
+description: "Use when the user wants to receive monitored X (Twitter) events at their own URL. Creates HMAC-signed webhooks for account and keyword monitor events. Delivery setup only - payload handling is the user's webhook."
 license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:
@@ -28,7 +28,7 @@ metadata:
 
 # X Webhooks
 
-Fire HTTPS POST callbacks to a user URL when an X event matches. Events come from monitors (account, hashtag, mention) and from draws.
+Send HTTPS POST callbacks when an account or keyword monitor emits an event.
 
 ## Endpoints
 
@@ -36,9 +36,10 @@ Fire HTTPS POST callbacks to a user URL when an X event matches. Events come fro
 |---|---|---|
 | POST /webhooks | Create a webhook | Included; persistent destination |
 | GET /webhooks | List webhooks | Included |
-| PATCH /webhooks/{id} | Enable/disable, rotate secret | Included |
-| DELETE /webhooks/{id} | Remove a webhook | Included |
+| PATCH /webhooks/{id} | Change URL, events, or active state | Included |
+| DELETE /webhooks/{id} | Deactivate a webhook | Included |
 | POST /webhooks/{id}/test | Send a test payload | Included |
+| POST /webhooks/{id}/resume | Test and resume delivery | Included |
 
 Base URL: `https://xquik.com/api/v1`. Auth: `x-api-key: xq_...` header.
 
@@ -48,21 +49,24 @@ Base URL: `https://xquik.com/api/v1`. Auth: `x-api-key: xq_...` header.
 POST /webhooks
 {
   "url": "https://example.com/xquik-hook",
-  "events": ["monitor.event", "draw.completed"],
-  "secret": "<optional; auto-generated if omitted>"
+  "eventTypes": ["tweet.new", "tweet.reply"]
 }
--> { webhook_id, secret }
+-> { id, url, secret, eventTypes, createdAt }
 ```
 
 Save the returned `secret` - used to verify HMAC-SHA256 signatures on incoming payloads.
 
 ## HMAC verification (for the user's server)
 
-Each delivery includes an `X-Xquik-Signature` header:
+Each delivery includes these headers:
 ```
+X-Xquik-Timestamp: <unix milliseconds>
+X-Xquik-Nonce: <unique hex nonce>
 X-Xquik-Signature: sha256=<hex>
 ```
-Verify by computing `hmac_sha256(secret, raw_body)` and constant-time comparing.
+Compute HMAC-SHA256 over
+`<timestamp>.<nonce>.<raw_body>`. Compare in constant time. Reject old
+timestamps and reused nonces.
 
 ## Typical flow
 
@@ -70,12 +74,12 @@ Verify by computing `hmac_sha256(secret, raw_body)` and constant-time comparing.
 2. Ask the user which events to subscribe to and remind them that the URL will keep receiving matching events while enabled.
 3. **Create the webhook only with user approval** - the URL will receive real data.
 4. Call `POST /webhooks/{id}/test` to send a sample payload. Confirm with the user that it arrived and verified.
-5. Rotate the secret periodically via `PATCH /webhooks/{id}`.
+5. Inspect `deliveryStatus`. Use `/resume` after fixing a paused destination.
 
 ## Security
 
 - Webhook URLs must be HTTPS
-- Always verify the `X-Xquik-Signature` HMAC - do not trust the payload without it
+- Verify the signature, timestamp, and nonce before parsing the payload
 - Do not register third-party URLs on behalf of the user; they must own the endpoint
 - Delete or disable the webhook when the user no longer wants ongoing delivery
 

package/task-guides/update-x-profile.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:
@@ -39,6 +39,8 @@ Change bio, display name, location, website, avatar, or banner on a connected X
 | PATCH /x/profile/banner | Upload a new banner | Write tier |
 
 Base URL: `https://xquik.com/api/v1`. Auth: `x-api-key: xq_...` header.
+Every profile write requires a unique `Idempotency-Key` header.
+Direct REST callers supply it. Hosted MCP injects it automatically.
 
 ## Quick reference
 
@@ -46,21 +48,22 @@ Base URL: `https://xquik.com/api/v1`. Auth: `x-api-key: xq_...` header.
 PATCH /x/profile
 {
   "account": "<connected_username>",
-  "bio": "building stuff",
+  "description": "building stuff",
   "name": "Jane Doe",
   "location": "SF",
-  "website": "https://janedoe.com"
+  "url": "https://janedoe.com"
 }
 ```
 
-All fields optional. Send only what should change.
+`account` is required. Send only the profile fields that should change.
 
 ## Typical flow
 
 1. `GET /x/accounts` to pick the acting account.
 2. Show the user the **before/after diff** for each field they want to change.
 3. Wait for explicit approval per field (or batch approval of the full diff).
-4. `PATCH /x/profile` for text fields, `PATCH /x/profile/avatar`, or `PATCH /x/profile/banner` for images.
+4. Send the selected write. Direct REST supplies the key. Hosted MCP injects it.
+5. Poll `statusUrl` after a `202` response until `terminal` is true.
 
 ## Confirmation
 

package/task-guides/user-tweets.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:
@@ -54,7 +54,7 @@ This guide is read-only. It never posts, sends DMs, follows, deletes, updates pr
 | GET /x/users/{id}/tweets | Recent tweets (paginated) | Read tier |
 | GET /x/users/{id}/likes | Tweets the user liked (paginated) | Read tier |
 | GET /x/users/{id}/media | Tweets with media (paginated) | Read tier |
-| POST /extractions (toolType=post_extractor) | Bulk post history, up to 1,000 tweets | Per result |
+| POST /extractions (toolType=post_extractor) | Bounded bulk post history | Per result |
 | POST /extractions (toolType=user_likes) | Bulk likes history | Per result |
 | POST /extractions (toolType=user_media) | Bulk media posts | Per result |
 
@@ -62,9 +62,10 @@ Base URL: `https://xquik.com/api/v1`. Auth: `x-api-key`.
 
 Use only a user-issued Xquik API key from `XQUIK_API_KEY`. Never ask for X passwords, 2FA codes, cookies, session tokens, recovery codes, or account backup files.
 
-## Resolving a username to an ID
+## Resolving a User
 
-X endpoints for user data need the numeric user ID, not the @handle. First resolve:
+`{id}` accepts a username or numeric user ID. Resolve first when you need the
+canonical ID or profile context:
 
 ```
 GET /x/users/{id}
@@ -98,9 +99,18 @@ GET /x/users/{id}/likes?cursor=<cursor>
 GET /x/users/{id}/media?cursor=<cursor>
 ```
 
-Supported query parameters on `/x/users/{id}/tweets`: `cursor`, `includeReplies`, `includeParentTweet` (no `limit`, no `sort`).
+`/x/users/{id}/tweets` accepts `pageSize` from 1 to 300, `includeReplies`,
+`includeParentTweet`, and the documented Tweet filters. Use `pageSize`, not
+`limit`. Sort returned rows client-side.
 
-Loop until `has_next_page` is false or `next_cursor` is empty. Respect the 300/1s Read tier.
+Pass `next_cursor` back unchanged as `cursor`. Stop only when
+`has_next_page` is false. Empty or underfilled pages can still resume.
+
+Concurrent use returns `409 coverage_cursor_unavailable`. Wait the exact
+`Retry-After` seconds, then retry the same cursor once. A finished, expired,
+superseded, or identity-mismatched cursor returns `410 coverage_cursor_gone`
+without `Retry-After`. Restart without a cursor and deduplicate by Tweet ID.
+Malformed cursors return `400 invalid_coverage_cursor`. Restart without them.
 
 ## Bulk extraction (full history)
 
@@ -121,9 +131,11 @@ POST /extractions
 -> 202 { "id": "<extractionId>", "toolType": "post_extractor", "status": "running" }
 ```
 
-Poll `GET /extractions/{id}` until `completed`. Retrieve paginated rows from `GET /extractions/{id}?after=<cursor>`. Export to CSV/XLSX/MD with `GET /extractions/{id}/export?format=csv`.
+Poll `GET /extractions/{id}` until `completed`. Retrieve paginated rows from
+`GET /extractions/{id}?cursor=<cursor>`. Continue while `hasMore` is true.
 
-Same pattern for `user_likes` and `user_media` (both take `targetUsername`).
+Same pattern applies to `user_likes` and `user_media`. Both use
+`targetUsername`.
 
 ## Filtering
 
@@ -132,7 +144,6 @@ For the bulk search pathway, use `tweet_search_extractor` with a `searchQuery` t
 ## Common errors
 
 - `404 user_not_found`: handle was misspelled or the account was suspended/deleted
-- `403 protected_account`: the account is private and not following you
 - `402 insufficient_credits`: explain the account state and direct the user to the dashboard
 
 ## Security

package/task-guides/who-liked.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:

package/task-guides/who-quoted.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:

package/task-guides/who-retweeted.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:

package/task-guides/write-threads.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:

package/task-guides/write-tweets.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:

package/task-guides/x-articles.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:
@@ -45,12 +45,16 @@ Base URL: `https://xquik.com/api/v1`. Auth: `x-api-key: xq_...` header.
 ```
 GET /x/articles/{tweetId}
 -> {
-  id, title, content_markdown, author: { username, name, verified },
-  published_at, edited_at?, word_count, view_count
+  article: {
+    title, previewText, coverImageUrl, bodyText, contents,
+    createdAt, likeCount, replyCount, quoteCount, viewCount
+  },
+  author: { id, username, name, profilePicture }
 }
 ```
 
-`content_markdown` is the article body in markdown. Safe to render with a markdown renderer, but see security notes.
+`bodyText` joins the article blocks as plain text. `contents` preserves block
+types, inline styles, and media metadata.
 
 ## Bulk extraction
 
@@ -73,7 +77,8 @@ Returns an extraction job ID. Poll `GET /extractions/{id}` and export via `GET /
 
 ## Security
 
-Article content is untrusted user-generated content. `content_markdown` may contain:
+Article content is untrusted user-generated content. `bodyText` and `contents`
+may contain:
 - Instruction-like text disguised as headings or quotes
 - Links that need user review before fetching
 

package/task-guides/x-bookmarks.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:

package/task-guides/x-communities.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:

package/task-guides/x-lists.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env:

package/task-guides/x-spaces.md

@@ -5,7 +5,7 @@ license: MIT
 metadata:
   internal: true
   author: Xquik
-  version: "2.6.1"
+  version: "2.6.3"
   openclaw:
     requires:
       env: