x402 Cloud: how does an endpoint get approved for the discovery index? (active endpoints not appearing in `x402 discover`)

[GTCC777]

Big fans of x402 Cloud — thank you for building it. We've deployed two token-safety scanners that trading agents would ideally hit before a swap:

• x402.bankr.bot/0x7132eb021647675076fdf37f333d8a015770f095/memecoin — Solana honeypot/rug scanner
• x402.bankr.bot/0x7132eb021647675076fdf37f333d8a015770f095/evmtoken — EVM token safety scanner

Both are:

• active (confirmed via bankr x402 list)
• paid-verified — real on-chain USDC settlement on Base confirmed
• serving a correct 402 (structurally identical to indexed peers: x402Version: 2, same accepts, same router payTo, same facilitator)
• fully configured — description, JSON schema (input + output), tags, and category: security

They resolve fine via the schema API (GET /x402/endpoints/schema/<wallet>/<name>), but 24h+ after deploy they never appear in bankr x402 search / GET /x402/endpoints/discover for any query — including text lifted verbatim from their own descriptions. A fresh minimal endpoint deployed the same way behaves identically.

Your launch materials note that "every approved x402 Cloud endpoint is automatically indexed in the agent discovery layer." That suggests there's an approval step between deploy and discovery that we aren't clearing, but we couldn't find it documented (no list/status/reindex/publish route, and no criteria in the docs).

Could you help clarify:

1. How does an endpoint get approved for the discovery index — is it automatic, queued/async, or manual review?
2. Are there criteria we're missing? (We have schema + tags + category set.)
3. Could you approve these two? They're a clean fit for the pre-trade safety gate your trading agents need — we'd love agents to be able to scan-before-swap.

Happy to provide anything useful (logs, configs, etc.). Thanks!

[GTCC777]

Following up with specifics. I have two x402 Cloud endpoints — evmtoken and memecoin under wallet 0x7132eb021647675076fdf37f333d8a015770f095 — that are active and already serving paid requests, and they resolve correctly in the catalog (/x402/endpoints/schema/...) with full description, schema, category (security) and tags. But they do not appear in x402 discover for any query.

Could you approve/index these two, and/or share what gets an active Cloud endpoint into the discovery index? I tried re-publishing via the in-product agent but its endpoint tool hangs, so I suspect the approval step is manual. Happy to adjust anything on my end. Thanks!