feat: add satring (multi-protocol payment api service directory)

[toadlyBroodle]

Summary

Adds satring.com (source) to the MPP service directory.

Satring is a curated, health-monitored paid API directory for AI agents. First service in the registry using the Lightning payment method (method: "lightning", currency: "sat").

• 11 endpoints (5 free, 6 paid at 10-5000 sats)
• Accepts payments via MPP Lightning (Payment HTTP auth scheme)
• Also accepts L402 and x402 payments
• Live and accepting payments now: curl -i https://satring.com/api/v1/analytics
• OpenAPI spec with x-payment-info: https://satring.com/openapi.json

Changes

• schemas/services.ts: adds LIGHTNING_PAYMENT constant and satring service entry
• schemas/discovery.json: regenerated
• public/services/llms.txt: regenerated
• public/icons/satring.svg: vectorized logo (lightning bolt + chain ring)

Checklist

• Service is live and accepting payments via MPP
• Entry added to schemas/services.ts
• node scripts/generate-discovery.ts run, discovery.json committed
• node scripts/gen-icons.cjs run, custom icon committed
• Types pass: pnpm check:types
• Build succeeds: pnpm build

[vercel]

@toadlyBroodle is attempting to deploy a commit to the Tempo Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

👋 Thanks for submitting a service to the MPP directory!

Before we review, please make sure you've completed these steps:

Required

• Your service is live and accepting payments via MPP (not a placeholder or coming-soon)
• You've added your entry to schemas/services.ts following the contributing guide
• You've run node scripts/generate-discovery.ts and committed the updated schemas/discovery.json
• You've run node scripts/gen-icons.cjs and committed any new icons
• Types pass: pnpm check:types
• Build succeeds: pnpm build

Recommended

• Register your service on MPPScan — it follows the standard MPP discovery format and makes your service discoverable by agents immediately, no PR required

Review criteria

We prioritize services that are high quality and novel. We may not approve services that duplicate existing functionality or aren't yet production-ready.

---

📖 Contributing guide · 🔍 MPPScan · 📄 Protocol docs

[toadlyBroodle]

Note: satring is the first service in the registry using the lightning payment method, and we were unable to submit to MPPScan, owing to a spec discrepancy between it's schema expectations and the offical MPP spec:

During integration we noticed the @agentcash/discovery validator (used by MPPScan) enforces a different x-payment-info schema (pricingMode/price/protocols) than the official draft-payment-discovery-00 spec (intent/method/amount/currency). Our OpenAPI spec at https://satring.com/openapi.json follows the official IETF draft. I can adjust if there's a preferred format for the registry?