reaction check derived
launchcheck-x402.fly.devCommunicationsderived
POST https://launchcheck-x402.fly.dev/v1/reaction-check
passabsent from every registrycounted above 0% of Communications
0.5 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-02 12:31 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-09-02 19:25 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.5 USDC
- Networks
- 1
How has the volume on this endpoint moved?
TOLL files reaction check under communications: a POST endpoint on launchcheck-x402.fly.dev, listed in neither registry at the last pull.
Per call, reaction check declares 0.5 USDC on Base.
reaction check takes a json body with the fields content, constraints, contentType, desiredAction, productContext and targetAudience.
A response from reaction check, as declared, includes meta, report and requestId.
The daily sweep got a valid payment challenge from reaction check on 2026-10-02, as at every sweep since 2026-09-11.
launchcheck-x402.fly.dev lists no other endpoint.
reaction check drew a single call from a single payer in the trailing 30 days.
The last call to reaction check came 41 days before the snapshot, 2026-09-02.
reaction check sits nearest in price to pdl people enrich (stableenrich.dev) and run (x402.miroshark.xyz) among listings in communications.
reaction check is near the top of prices in communications; 99% of comparable listings are cheaper.
The wallet paid by reaction check is the payee of 3 endpoints on one host.
Seller tags: launch, copy-review, landing-page and product-announcement.
reaction check was missing from the Coinbase registry at the pull of 2026-10-02, confirmed at the pull of 2026-10-03; that is registry presence, not liveness.
Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.
the payment options, as of 2026-10-02 12:31 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.5 USDC | exact | 0x87F929…28DBa4 |
the checks, as of 2026-10-02 17:13 UTC · methodendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-02 17:13 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 09:52 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 09:19 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 21:24 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-23 08:17 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 08:30 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 08:52 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-19 06:49 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-17 06:41 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 06:38 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 06:54 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 06:21 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 06:12 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 08:29 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 14:38 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-02 19:25 UTC · method
The input and output block
{
"input": {
"body": {
"content": "Stress-test launch copy before you publish. LaunchCheck reviews messaging through eight audience lenses, flags positioning friction and unsupported claims, and returns concrete changes plus a fact-preserving rewrite.",
"constraints": [
"Do not invent metrics"
],
"contentType": "landing-page",
"desiredAction": "Run a paid reaction check.",
"productContext": "An x402-paid API for structured pre-launch copy review.",
"targetAudience": "Founders, product teams, and AI agents."
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"meta": {
"model": "example-model",
"cached": false,
"engine": "openai-compatible",
"generatedAt": "2026-07-26T12:00:00.000Z"
},
"report": {
"score": 74,
"verdict": "revise",
"topRisks": [
{
"fix": "State the specific pre-launch decision the review helps make.",
"title": "Differentiation is vague",
"evidence": "The copy lists checks without explaining why they beat a generic critique.",
"severity": "medium",
"whyItMatters": "Readers may not see why the specialized review is worth using."
}
],
"inputIntegrity": {
"status": "clean",
"evidence": []
},
"likelyQuestions": [
"Why use this instead of a generic model?"
],
"requiredChanges": [
"Clarify the specialized value."
],
"executiveSummary": "Clear value, but the differentiation needs stronger evidence.",
"suggestedRewrite": "Stress-test launch copy before you publish with eight audience lenses, evidence checks, concrete fixes, and a fact-preserving rewrite.",
"audienceReactions": [
{
"lens": "Skeptical technical buyer",
"friction": "Differentiation is unclear.",
"reaction": "mixed",
"confidence": 0.82,
"likelyThought": "Useful, but why not use a generic model?"
},
{
"lens": "Busy nontechnical decision-maker",
"friction": "Differentiation is unclear.",
"reaction": "mixed",
"confidence": 0.82,
"likelyThought": "Useful, but why not use a generic model?"
},
{
"lens": "Price-sensitive solo user",
"friction": "Differentiation is unclear.",
"reaction": "mixed",
"confidence": 0.82,
"likelyThought": "Useful, but why not use a generic model?"
},
{
"lens": "Privacy and security-conscious evaluator",
"friction": "Differentiation is unclear.",
"reaction": "mixed",
"confidence": 0.82,
"likelyThought": "Useful, but why not use a generic model?"
},
{
"lens": "Existing customer scanning for regressions",
"friction": "Differentiation is unclear.",
"reaction": "mixed",
"confidence": 0.82,
"likelyThought": "Useful, but why not use a generic model?"
},
{
"lens": "First-time visitor with low context",
"friction": "Differentiation is unclear.",
"reaction": "mixed",
"confidence": 0.82,
"likelyThought": "Useful, but why not use a generic model?"
},
{
"lens": "Enthusiastic early adopter",
"friction": "Differentiation is unclear.",
"reaction": "mixed",
"confidence": 0.82,
"likelyThought": "Useful, but why not use a generic model?"
},
{
"lens": "Support-minded operator anticipating questions",
"friction": "Differentiation is unclear.",
"reaction": "mixed",
"confidence": 0.82,
"likelyThought": "Useful, but why not use a generic model?"
}
],
"strongestElements": [
"The pre-launch use case is clear."
],
"optionalImprovements": [],
"claimsNeedingEvidence": []
},
"requestId": "2e847847-52da-46c6-b627-f95dbd66919f"
}
}
}Cite this page
This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "reaction check on launchcheck-x402.fly.dev". https://tollindex.com/e/launchcheck-x402-fly-dev-v1-reaction-check-ea8c5c. Accessed [access date].
BibTeX
@misc{toll-e-launchcheck-x402-fly-dev-v1-reaction-check-ea8c5c-2026-10-13,
author = {TOLL},
title = {reaction check on launchcheck-x402.fly.dev},
howpublished = {\url{https://tollindex.com/e/launchcheck-x402-fly-dev-v1-reaction-check-ea8c5c}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.