passlisted in Coinbase#13 by calls of 26 on this host
0.01 USDC
per call, as the listing declares it on solana:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 4
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-09-15 17:57 UTC
- First observed by TOLLderived
- 2026-09-12
- Pricederived
- 0.01 USDC
- Networks
- 2
How has the volume on this endpoint moved?
twitter dispute shares palmyr.ai with 25 other listed endpoints and is tied 13th by calls with 2 others.
twitter dispute declares an input block that names no parameters.
A response output is declared and no example is given.
twitter dispute drew 4 calls from 2 unique payers in the trailing 30 days.
The last call to twitter dispute came on the day of the snapshot, 2026-09-15.
A call to twitter dispute costs 0.01 USDC on Solana, as declared.
twitter dispute takes 3% of the calls counted across palmyr.ai.
2 payment options span Solana and Base, to 2 different wallets.
twitter dispute is a POST endpoint at palmyr.ai, listed in the Coinbase registry and filed by TOLL under communications.
twitter dispute answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-12.
Closest in price to twitter dispute within communications: tomba email finder at x402.orthogonal.com and check at email-auth.use.x402atlas.com.
twitter dispute is priced above 32% of comparable listings in communications.
Within communications, 69% of endpoints with counters have fewer calls.
The wallet paid by twitter dispute is the payee of 28 endpoints across 2 hosts.
The seller's tags on twitter dispute are social, twitter, x and dispute, and its label is "social".
The price of twitter dispute is declared by 162 other listings in communications too.
the payment options, as of 2026-09-15 21:20 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | solana: | USDC | 0.01 USDC | exact | GqSs5L9a…PhSgkM |
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x79e999…323881 |
the checks, as of 2026-09-15 05:02 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-15 05:02 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 04:53 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 04:52 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 07:07 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-12 05:44 UTC | pass | 0 | new-2026-09-12T05-44-30-618Z |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-15 17:57 UTC · method · live
The input and output block
{
"input": {
"body": {},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"example": {}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 21:20 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "twitter dispute on palmyr.ai", snapshot of 2026-09-15 21:20 UTC. https://tollindex.com/e/palmyr-ai-social-twitter-dispute-65ea78/at/2026-09-15T21-20Z. Accessed [access date].
BibTeX
@misc{toll-e-palmyr-ai-social-twitter-dispute-65ea78-2026-09-15T21-20Z,
author = {TOLL},
title = {twitter dispute on palmyr.ai},
howpublished = {\url{https://tollindex.com/e/palmyr-ai-social-twitter-dispute-65ea78/at/2026-09-15T21-20Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 21:20 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.