Skip to main content
The Machine Payments Protocol (MPP) is an open standard for machine-to-machine payments over HTTP. Xquik implements MPP on 32 X-API read-only endpoints, allowing you to pay per call without creating an account or subscribing.

How it works

MPP uses HTTP 402 (Payment Required) as a payment challenge. When you call an eligible endpoint without a subscription or API key, the server returns a 402 with payment instructions. Your client pays via Tempo (USDC), then retries the request with a payment credential.
Client                              Xquik
  │                                   │
  │  1. GET /api/v1/x/tweets/123      │
  │──────────────────────────────────▶│
  │                                   │
  │  2. 402 Payment Required          │
  │     WWW-Authenticate: Payment     │
  │     (challenge with amount, etc.) │
  │◀──────────────────────────────────│
  │                                   │
  │  3. Pay via Tempo (USDC)          │
  │           (off-chain)             │
  │                                   │
  │  4. Retry with credential         │
  │     Authorization: Payment ...    │
  │──────────────────────────────────▶│
  │                                   │
  │  5. 200 OK + Payment-Receipt      │
  │◀──────────────────────────────────│
No account, no API key, no subscription. The payment itself is your authentication.

Payment method

MPP payments on Xquik use Tempo with USDC (a dollar-pegged stablecoin). Tempo provides near-zero transaction fees, making micropayments practical for per-call pricing. You need a funded Tempo USDC wallet. See the MPP quickstart for setup instructions.

Payment intents

Xquik uses 2 payment intents depending on the endpoint:
IntentHow it worksUsed by
chargeFixed cost per call. Single on-chain settlement.Tweet lookup, user lookup, follower check, article extraction, trends, community info
sessionPay per result returned. Client deposits funds, sends off-chain vouchers per item.Tweet search, user tweets, media download, quotes, replies, retweeters, favoriters, thread, likes, user media, community members/moderators/tweets/search, list followers/members/tweets, user batch/search/followers/following/mentions/verified-followers/followers-you-know
With charge, you pay a flat amount per request. With session, you pay proportional to the number of results (tweets found, media items downloaded).

Eligible endpoints

EndpointMethodPriceIntent
/api/v1/x/tweets/{id}GET$0.00015 per callcharge
/api/v1/x/tweets/searchGET$0.00015 per tweetsession
/api/v1/x/users/{id}GET$0.00015 per callcharge
/api/v1/x/followers/checkGET$0.00105 per callcharge
/api/v1/x/articles/{id}GET$0.00105 per callcharge
/api/v1/x/media/downloadPOST$0.00015 per media itemsession
/api/v1/x/users/{id}/tweetsGET$0.00015 per tweetsession
/api/v1/x/tweets/{id}/quotesGET$0.00015 per tweetsession
/api/v1/x/tweets/{id}/repliesGET$0.00015 per tweetsession
/api/v1/x/tweets/{id}/retweetersGET$0.00015 per usersession
/api/v1/x/tweets/{id}/favoritersGET$0.00015 per usersession
/api/v1/x/tweets/{id}/threadGET$0.00015 per tweetsession
/api/v1/x/users/{id}/likesGET$0.00015 per tweetsession
/api/v1/x/users/{id}/mediaGET$0.00015 per tweetsession
/api/v1/trendsGET$0.00045 per callcharge
/api/v1/x/trendsGET$0.00045 per callcharge
/api/v1/x/communities/{id}/infoGET$0.00015 per callcharge
/api/v1/x/communities/{id}/membersGET$0.00015 per usersession
/api/v1/x/communities/{id}/moderatorsGET$0.00015 per usersession
/api/v1/x/communities/{id}/tweetsGET$0.00015 per tweetsession
/api/v1/x/communities/searchGET$0.00015 per communitysession
/api/v1/x/communities/tweetsGET$0.00015 per tweetsession
/api/v1/x/lists/{id}/followersGET$0.00015 per usersession
/api/v1/x/lists/{id}/membersGET$0.00015 per usersession
/api/v1/x/lists/{id}/tweetsGET$0.00015 per tweetsession
/api/v1/x/users/batchGET$0.00015 per usersession
/api/v1/x/users/searchGET$0.00015 per usersession
/api/v1/x/users/{id}/followersGET$0.00015 per usersession
/api/v1/x/users/{id}/followers-you-knowGET$0.00015 per usersession
/api/v1/x/users/{id}/followingGET$0.00015 per usersession
/api/v1/x/users/{id}/mentionsGET$0.00015 per tweetsession
/api/v1/x/users/{id}/verified-followersGET$0.00015 per usersession
All other endpoints (monitors, webhooks, extractions, draws, write actions, etc.) require a subscription.

MPP vs subscription

MPP (pay-per-use)Subscription ($20/month)
Account requiredNoYes
API key requiredNoYes
PaymentPer call via Tempo (USDC)Monthly credit/debit card
Available endpoints32 X-API read-onlyAll endpoints
Write actionsNot availablePost tweets, like, retweet, follow, DM, profile updates
Monitors & webhooksNot availableReal-time account monitoring
Extractions & drawsNot availableBulk data extraction, giveaway draws
Best forAI agents, one-off lookups, low-volume readsFull platform access, production integrations

Next steps

MPP quickstart

Make your first pay-per-use API call.

Authentication

All authentication methods including MPP headers.

Billing & usage

Subscription pricing and MPP per-call costs.