ngl
IFFY

55 / 100

$COVENANT

0x2eef…16a1de· Robinhood Chain

ngl, not gonna lie

A real open-source x402 gateway exists, but payments were never seen working and the project is days old.

The site has a working wallet connect and a Paid APIs view, and the GitHub repo has real code (70 commits). The test wallet had no USDG, so no payment or session was completed and instant settlement is not shown. On chain the launch looks clean: no other launch-block buyers, the dev holds nothing and burned 8%. The X account and domain are only days old, and some replies call it a scam.

Ask the agent

Checked 1 h ago

Red flags0

No red flags found.

Watch out4

  • Instant-settlement claim not shown

    No payment or session was ever completed, so the core claim of paid calls settling instantly in USDG is neither confirmed nor disproved.

    screenshotscreenshotscreenshot
  • Brand-new X account and domain

    The X account is 5 days old with 192 followers, and the domain was registered 5 days ago. Both match the coin launch, so there is no track record.

    @Convenantx402registration
  • Some replies call it a scam

    7 replies call it a scam or rug, including a checker bot that rated it 'partly real'. These are opinions, not evidence of wrongdoing.

    @Larpcheckbot@Larpcheckbot@denimahesaa@huseyindemir48
  • Paid APIs view loads, payments not completed

    The agent connected a wallet and opened the Paid APIs list (/href, /news, /signals, /alerts). OPEN SESSION and PAY both stopped at 'insufficient USDG' because the test wallet had 0 USDG, so no signature request or settlement was seen.

    screenshotscreenshotscreenshot

Checks out4

  • Real open-source code exists

    The covenantx402/covenant repo has 70 commits and 88 files of real code, last pushed 6 hours ago. It is new, has a single contributor and 0 stars.

    covenantx402/covenantclaim source
  • Clean launch block

    Apart from the dev buy, nobody bought in the launch block, so there is no sign of bundled sniping.

    launchdev
  • Dev holds nothing and burned 8%

    The dev wallet holds 0.0% and sold only 0.4% of supply since launch. It sent 8.0% of supply to the burn address.

    devtransferburn
  • Site and coin match up

    The site lists the exact contract address and links back to the coin's X account.

    pagefirst screen

Ask the agent

Anything about $COVENANT. ngl answers from this check, or goes back to the site and tries what you ask.

Hands-on tests

  • WorksConnect wallet and open Paid APIs

    Wallet connects and Paid APIs view loads

    What it did:
    Clicked Connect Wallet (test wallet), then opened the Paid APIs view.
    What the site showed:
    Wallet connected as 0xa954…d14a, showing 0.00 USDG. Paid APIs view loaded with path list (/href, /news, /market-analytics, /signals, /alerts).
    Screenshot: Wallet connects and Paid APIs view loads
  • Couldn’t testOpen paid session (OPEN SESSION 0.01 USDG · 100 calls)

    Session open stops at zero-USDG balance check

    What it did:
    Clicked the OPEN SESSION (0.01 USDG · 100 calls) button several times.
    What the site showed:
    A 'Payment failed' banner: 'insufficient USDG: you have 0 USDG, this call costs 0.01 USDG'. The test wallet holds 0 USDG, so no wallet signature request was reached. Later clicks did nothing visible.
    Screenshot: Session open stops at zero-USDG balance check
  • Couldn’t testPay for a paid API call (PAY on /alerts row, and /news row)

    PAY stops at zero-USDG balance check

    What it did:
    Clicked PAY on the /alerts row (0.01 USDG) and again later; the path field shows /news.
    What the site showed:
    Same 'insufficient USDG: you have 0 USDG, this call costs 0.01 USDG' message. No wallet signature request appeared.
    Screenshot: PAY stops at zero-USDG balance check
  • BrokenRetry of clicks on failed element references

    Stale-ref clicks failed (tool-side, not site)

    What it did:
    Attempted to click stale element e1151 several times.
    What the site showed:
    'not on the page' errors from the tool, not site behavior.
    Screenshot: Stale-ref clicks failed (tool-side, not site)
New checkBrowse all checks