TOLL

What software pays for, recorded every six hours.

Snapshot
2026-09-15 16:57 UTC
Sweep
daily-2026-09-15 · finished 2026-09-15 07:10 UTC
Listed
16,167

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:8453

Compare with anotherEvery figure as JSONCite this page

the price, as of 2026-09-15 16:57 UTC · method · pinnable

Validation state
pass
as of 2026-09-15 06:54 UTC · method · pinnable · sweep daily-2026-09-15
Uptime, 7 / 30 / 90 days
100% / 100% / 100%
as of 2026-09-15 06:54 UTC · method · pinnable · 5 of 5 in 7d, 5 of 5 in 30d, 5 of 5 in 90d
Calls, trailing 30 days
2
as of 2026-09-15 16:57 UTC · method · pinnable
Unique payers, trailing 30 days
1
as of 2026-09-15 16:57 UTC · method · pinnable
Last called
2026-09-02 19:25 UTC
as of 2026-09-15 16:57 UTC · method · pinnable
First observed by TOLLderived
2026-09-10
as of 2026-09-10 19:08 UTC · method · pinnable · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.5 USDC
as of 2026-09-15 16:57 UTC · method · pinnable · on eip155:8453
Networks
1
as of 2026-09-15 16:57 UTC · method · pinnable

Counters

28 observations, 3 of them a change

How has the volume on this endpoint moved?

2345210 Sep11 Sep12 Sep13 Sep14 Sep15 Sep
Calls counted in the trailing 30 days on this endpoint, at every snapshot since 2026-09-10. Each point is a trailing-30-day sum as the registry published it, not a daily rate. The axis is truncated to the range of the data with a break at its foot.

In words

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.

Payment options as declared

the payment options, as of 2026-09-15 16:57 UTC · method · pinnable

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.5 USDCexact0x87F929…28DBa4

Preflight checks at the last sweep

the checks, as of 2026-09-15 06:54 UTC · method · pinnableendpoint answered HTTP 402

No named check failed.

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTCstatefailed checkssweep
2026-09-15 06:54 UTCpass0daily-2026-09-15
2026-09-14 06:21 UTCpass0daily-2026-09-14
2026-09-13 06:12 UTCpass0daily-2026-09-13
2026-09-12 08:29 UTCpass0daily-2026-09-12
2026-09-11 14:38 UTCpass0daily-2026-09-11

Registry presence

Presence in a registry, not liveness of the service (method). Newest first.

  1. listed in Coinbase

Declared input and output, as listed

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].}
}

Reports and replies about this endpoint

None yet. Anything submitted through the form below is published here with its outcome.

Report an error about reaction check, or reply as the named seller

No account, no token. Published unedited with its outcome, upheld or not. Do not include personal data.

Kind

Published as typed. Optional.

10 to 4,000 characters.

Verify with the payee wallet (optional, EVM)

Sign this message with the wallet named on the page and paste the signature; it is checked, stored, never published. TOLL reply about endpoint ea8c5c7a4445b889eff11a7d8e6e7cf2acb2c73344d34bb08803a342226c36ac from wallet 0x87F929c4eCac1556a507cE6b92eF95c52B28DBa4

The 0x address named as payee on this page, 42 characters.

The hex signature of the message above, starting 0x.