reaction check derived
launchcheck-x402.fly.devCommunicationsderived
POST https://launchcheck-x402.fly.dev/v1/reaction-check
passlisted in Coinbase#3 by calls of 3 on this host
0.5 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 2
- 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?
At launchcheck-x402.fly.dev, reaction check takes POST requests, is listed in the Coinbase registry, and falls under communications by TOLL's rules.
reaction check is priced at 0.5 USDC on Base.
The request to reaction check is 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.
reaction check answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.
reaction check shares launchcheck-x402.fly.dev with 2 other listed endpoints and is 3rd by calls.
reaction check takes 9% of the calls counted across launchcheck-x402.fly.dev.
One payer accounts for all 2 calls to reaction check over 30 days.
The last call to reaction check came 13 days before the snapshot, 2026-09-02.
Closest in price to reaction check within communications: pdl people enrich at stableenrich.dev and alerts at whaletape.xyz.
reaction check is near the top of prices in communications; 93% of comparable listings are cheaper.
The wallet paid by reaction check is the payee of 3 endpoints on one host.
The seller's own tags are launch, copy-review, landing-page and product-announcement.
the payment options, as of 2026-09-15 16:57 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.5 USDC | exact | 0x87F929…28DBa4 |
the checks, as of 2026-09-15 06:54 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 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.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-02 19:25 UTC · method · live
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
The pinned URL below renders this page from the snapshot of 2026-09-15 16:57 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "reaction check on launchcheck-x402.fly.dev", snapshot of 2026-09-15 16:57 UTC. https://tollindex.com/e/launchcheck-x402-fly-dev-v1-reaction-check-ea8c5c/at/2026-09-15T16-57Z. Accessed [access date].
BibTeX
@misc{toll-e-launchcheck-x402-fly-dev-v1-reaction-check-ea8c5c-2026-09-15T16-57Z,
author = {TOLL},
title = {reaction check on launchcheck-x402.fly.dev},
howpublished = {\url{https://tollindex.com/e/launchcheck-x402-fly-dev-v1-reaction-check-ea8c5c/at/2026-09-15T16-57Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 16:57 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.