Ecosystem: add Satelink (Services/Endpoints)

[Satelink-Protocol]

Adds Satelink to the ecosystem page under Services/Endpoints: a DePIN RPC gateway where one $0.10 USDC settlement on Base (CDP facilitator, x402 v2) buys a 1,000-call Polygon JSON-RPC bundle — no account, no subscription, fully autonomous onboarding.

Proof of live operation:

• x402 v2 402 with spec-compliant payment requirements + Bazaar discovery extension: POST https://rpc.satelink.network/rpc/polygon (past the free tier)
• Settled bundle purchases verifiable on Base: payTo 0x966E1Ae22996545015b1414B35234b10719d7Ad4 (e.g. tx 0x0e0a72d430278782aa6b1415152d0b7fddc43d9423669032edf522ad9ec7a4f3) — payment credits the bundle and serves the RPC call in the same round-trip
• Machine-readable service manifest: https://rpc.satelink.network/.well-known/satelink.json — pricing, market comparison (/v1/compare) and capabilities (/v1/capabilities) APIs included

Entry follows the partners-data convention (metadata.json + 512px logo).

[cb-heimdall]

🟡 Heimdall Review Status

Requirement	Status	More Info
Reviews	🟡 0/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 2 if repo is sensitive 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 1 Sum 2

[Satelink-Protocol]

One data point for maintainers, since issues are disabled on this repo — filed here because it affects how agents discover the endpoints on the ecosystem page:

Bazaar ingestion appears to have stopped picking up our settle-carried v2 discovery extensions after 2026-07-10. A 2026-07-09 settlement created a catalog entry near-real-time (lastUpdated ~200ms after settlement), but two subsequent mainnet settlements (2026-07-10/11, txs 0x1f08e12aef…, 0x0e0a72d430…, payTo 0x966E1Ae2…) produced no new entry and no update — verified by full catalog scans of all ~25.9k resources, during a window in which other services' entries were ingested. The settle paymentPayload carries x402Version: 2, the correct resource.url, and an extensions.bazaar block that @x402/extensions' own validateDiscoveryExtension accepts ({valid: true}); extractDiscoveryInfo resolves it to https://rpc.satelink.network/rpc/polygon. Meanwhile the stale 2026-07-09 entry (/rpc/:var1, $0.001) strands any agent that discovers us through the catalog — payments built from it now fail amount_too_low.

Questions: does ingestion now require anything beyond a settle-carried v2 extension (review gate, allowlist, minimum settlements)? And is there a supported way to correct/remove a stale entry? Happy to share correlation IDs or run diagnostics against our origin.