Add provider SLA badge data to catalog responses

[emrekayat]

Why this matters

Query402 is easiest to evaluate when reviewers can see why one provider is safer or more reliable than another before paying for a query.

Scope

Extend provider catalog data with lightweight SLA badge fields derived from existing static metadata:

• latencyBand such as fast, standard, slow;
• reliabilityBand such as demo, fallback, live;
• paymentMode such as demo, x402, or sponsored when known;
• short UI-safe copy explaining the badge.

Suggested files:

• apps/api/src/lib/pricing.ts
• apps/api/src/routes/public.ts
• packages/shared/src/schemas.ts
• apps/web/src/App.tsx or provider card component if split out.

Acceptance criteria

• /api/catalog or /api/providers exposes the badge metadata consistently.
• Web provider cards render the badges without changing payment behavior.
• Unknown providers fall back to a safe Not verified or equivalent badge.
• Tests cover the catalog shape and at least one provider card rendering path.
• Existing typecheck and API tests pass.

Wave complexity

High - improves provider diligence and paid-query selection confidence.

[Gabugo-tech]

@Gabugo-tech has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi Maintainers,

I'd like to work on this issue. I understand the goal is to expose provider SLA badge metadata through the catalog API and surface it in the UI while keeping payment behavior unchanged.

I'll implement the badge fields with safe fallbacks for unknown providers, update the relevant schemas and provider cards, and add test coverage to ensure the catalog shape and rendering behavior remain reliable.

Thanks for your consideration.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Gabugo-tech to this issue.

[Bojest001]

@Bojest001 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer I will to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Bojest001 to this issue.

[OG-wura]

@OG-wura has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Can I please work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OG-wura to this issue.

[drips-wave]

Congratulations, @OG-wura! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @OG-wura: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊