We're GenTech Labs, a 10-service x402 gateway. Reopening as a resource-specific ticket per maintainer redirect on #764 (closed: "open a new ticket specifically for your resource").

Resource: https://api.gentechlabs.net/v1/defi/lp/0x7ebff188f2Eba16518C02864589b1403a5d1296a (payTo 0x7ebff188f2Eba16518C02864589b1403a5d1296a)

Symptom: settlements succeed via the CDP facilitator (Base USDC, five+ verified on-chain since Aug 19), but our resource never appears in Bazaar discovery/search.

We've ruled out the causes other reports were chasing — with a live, keyless check (no payment, no settlement):

• Built the PAYMENT-SIGNATURE payload with the official @x402/core client against our live 402 challenge: resource PRESENT, extensions.bazaar PRESENT, keys x402Version,payload,extensions,resource,accepted, accepted.network: eip155:8453.
• Base64 round-trip (exactly what the header carries): both fields survive intact. Gateway forwards the client payload unmodified.
• Control queries return results (defi-lp 7, wallet-analysis 13, token-security 10), so the discovery endpoint is live and healthy.

The one variable we share with failing cases: payTo is an external EOA, not a wallet provisioned through a CDP developer account (the open question from old #2112).

Ask: Is Bazaar indexing gated on the payee wallet being CDP-registered/allowlisted? If so, what's the path to request inclusion for an external EOA? We've verified the client, the extension, and the domain; the remaining variable is the payee-wallet relationship to a CDP account.

Happy to share full wire captures, the verified payment payload, or run any targeted test against a candidate fix.