Send native x402 REST usage
Pay the send-native execution fee (native coin transfer)
0.05 USDC per call
per call
← All services
Daily transfers, volume and coverage →
User tweets
x402 resource x402 RESTtwitterapi-x402.vercel.app · twitterapi-x402.vercel.app · Other services
not indexed
Provider site ↗
Get user's latest tweets
Price per call
0.01 USDC per call
published unit: per call
Calls · 30d
—
not reported by any source
Payers · 30d
—
not reported by any source
Observed inflows · 30d
$0.00
0 transfers to the payout address
Inflow growth · 7d
—
not comparable (baseline under $1 or window incomplete)
Payment evidence
Price published
confidence: low
· read 2026-10-29
Observed inflows · last 30 days
$0.01USD observed / day
2026-09-29grey = not scanned · UTC days2026-10-28
| Window | Observed | Transfers |
|---|---|---|
| Last complete day (2026-10-28) | $0.00 | 0 |
| Last 7 days | $0.00 | 0 |
| Last 30 days | $0.00 | 0 |
| Growth, 7d against the 7 before | not comparable | |
Daily history →. Observed transfers show value arriving at the payout address; they do not establish service revenue.
Blockchain wallets
Full addresses · public payment evidenceReceiving wallets are payment addresses published for this service. Sending wallets transferred funds to an exclusive receiving address; this alone does not prove a purchase or identify an agent.
Receiving wallets · provider payment addresses
| Network | Full wallet address | Evidence |
|---|---|---|
| base | 0x78143cc8921f98084a16801a6C3Fb6bBd938a14A | Exclusive to this catalogue serviceFrom source record · source: payai |
Sending wallets · observed counterparties
No sending wallet addresses have been retained for this service. Buyer wallets are unknown; daily totals and reported payer counts do not reveal their addresses.
Coverage includes retained scans only, not every historical transaction. Earlier daily totals cannot recover sender addresses. Sender lists exclude shared receiving wallets, whose transfers could belong to another service. A provider address does not establish wallet ownership.
Competitors & category benchmark
Rank the whole category →
Closest competitors
Other services
- Send native 14,570 calls · 0.05 USDC per call —
- Submit 3,394 calls · 0.002 USDC per call —
- Hash 503 calls · 0.002 USDC per call —
- Horror Story API 467 calls · 0.01 USDC per call $4.61
- Gas now 442 calls · 0.001 USDC per call —
Sorted by source-measured calls, not by our opinion. The right-hand figure is observed inflow, which stays empty for peers whose address is shared.
Category benchmark
15,505 services in this category
| With a measured call count | 2,096 (13.5 %) |
|---|---|
| With a published price | 3,443 (22.2 %) |
| With attributable inflows | 91 (0.6 %) |
| Observed inflows · 30d | $115.94 |
| Median measured calls | 2 |
| Median price per call | $0.01 |
Similar services
All of Other services →Submit x402 REST usage
Chainlink For Agents: submit a signed operation payload.
0.002 USDC per call
per call
Hash x402 REST usage
Compute a SHA-256, SHA-384, or SHA-512 digest of UTF-8 text; returns hexadecimal output (default SHA-256).
0.002 USDC per call
per call
Horror Story API x402 REST usage
Access the exclusive horror story collection (pay-per-read).
0.01 USDC per call
per call
Chosen by category and by whether we have measured them, not by who pays us. A sponsored placement in this list is labelled as such.
Service details, payment routes and source evidence
Where you can pay
1 route from the provider's payment requirements| Network | Scheme | Amount | Asset |
|---|---|---|---|
| base | exact | 0.01 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 10000 = 0.01 USDC per call on base.
What you can call
access: payment per call (x402)endpoint
https://twitterapi-x402.vercel.app/api/twitter/user-tweets
Request
{
"type": "http",
"method": "GET",
"queryParams": {
"username": {
"type": "string",
"required": true,
"description": "Twitter username"
}
}
}
Examples are the provider's own, not a call we made.
Opportunity insights
2 findings from measured data-
Priced, but nothing observed arriving
A price is published, yet no transfer reached the payout address in the last 30 days (the address is scanned daily). Either the buyers pay elsewhere, the volume is below one cent, or the endpoint is dormant. Only 91 of 15505 services in this category have attributable inflows at all.
Services here that do show inflows → -
Category benchmark
91 of 15,505 services (0.6%) in Other services have attributable inflows; 2,096 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →
What the provider says
Get user's latest tweets
Quoted from PayAI · source record · read 2026-10-29
Facts and where they come from
- Price
-
0.01 USDC per call
Provider claim
Recorded value: 0.01 USDC per call.
- Unit
- per call
- Protocol
- x402, REST · transport: HTTP Provider claim
- Auth
- x402
- Source
- PayAI · Public discovery API (provider-published records)
- Last checked
- Not checked by us yet — the data is as the source published it
- First seen
- 2026-10-26
Money, and what it actually proves
Verified revenue · 30d
Unknown
Observed inflows · 30d
$0.00
Attribution
Exclusive
Receipt ledger
Not connected
Price published
· confidence low
The provider publishes a price. Nothing has been observed arriving at a payout address, and no receipt is on record.
Why revenue is “unknown”. A revenue figure needs a receipt: an amount a buyer actually paid for this service. We hold none for this entry, and we hold no funds at all. What we have instead is $0.00 arriving at the payout address in 30 days — that is volume, and a lower bound: transfers can be refunds, treasury moves, or payments for something else entirely.
Daily market statistics — the ledger view, day by day
No daily history has been archived for this service yet. Open the full daily history →
Payment rails
base
· exact · USDC
0x78143cc8921f98084a16801a6C3Fb6bBd938a14A
0.01 USDC
From source record
A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it.
Provenance
One row per statement. “Verified” means we checked it ourselves and the finding is quoted. “Provider claim” means we read it in the provider's own record. “Not found” is a statement about our search, not proof of absence.
| Statement | Status | What we found | Source | Checked |
|---|---|---|---|---|
| Endpoint | Provider claim |
https://twitterapi-x402.vercel.app/api/twitter/user-tweets
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
facilitator.payai.network | 2026-10-29 |
| Input output | Provider claim |
Request/response examples published with the listing
EvidenceBeispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters. |
facilitator.payai.network | 2026-10-29 |
| Payment | Provider claim |
1 rail: base · payee 0x78143cc8921f98084a16801a6C3Fb6bBd938a14A
EvidenceAus den `accepts`-Einträgen: Netzwerk, Asset, Empfängeradresse und Betrag. Die Adresse ist die Grundlage der späteren On-Chain-Zuordnung; sie ist noch nicht durch eine eigene 402-Antwort bestätigt. |
facilitator.payai.network | 2026-10-29 |
| Pricing | Provider claim |
0.01 USDC per call
EvidenceAtomic amount 10000 = 0.01 USDC per call on base. Netzwerk: base. |
facilitator.payai.network | 2026-10-29 |
| Protocol | Provider claim |
x402 (HTTP 402 payment challenge)
EvidenceIm x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 1, Typ http). |
facilitator.payai.network | 2026-10-29 |
| Provider | Provider claim |
twitterapi-x402.vercel.app
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
facilitator.payai.network | 2026-10-29 |
Endpoint checks
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.