docs: add Nirium to community skills

[Eras256]

Summary

Adds Nirium to ECOSYSTEM_CARDS in site/src/data/skills.ts, per the
community-skills convention in site/README.md.

Nirium is an open-source toolkit for x402 agentic payments on Stellar:
a TypeScript/Python SDK, a scaffolding CLI (nirium-cli), and an MCP
server (nirium-mcp). Live on mainnet since April 2, 2026, the day the
x402 Foundation launched. The skill teaches an agent to:

• scaffold a working x402 seller with nirium-cli in one command
• charge per route with x402Serve() from the nirium SDK
• read live protocol data (market state, autonomous loop status,
  execution nodes) through nirium-mcp

The skill itself lives in the project's own repo (not this one, per the
ECOSYSTEM_CARDS convention for community skills):
https://github.com/nirium-protocol/nirium-sdk/blob/main/skills/nirium-agentic-payments/SKILL.md

Test plan

• pnpm lint:ts (tsc --noEmit) passes
• pnpm lint (next lint) passes
• Card renders correctly in pnpm dev / the PR preview build

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a new ecosystem card entry to highlight “Nirium Agentic Payments” in the skills/ecosystem data list.

Changes:

• Added a new ECOSYSTEM_CARDS entry for Nirium Agentic Payments
• Included a long descriptive blurb and a link to the corresponding SKILL document

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[kaankacar]

🤖 Automated message from Kaan's Automated Triage Bot.

👀 Picked this up — a review will follow shortly.

[kaankacar]

🤖 Automated message from Kaan's Automated Triage Bot.

Thanks for this — the honesty in the skill really stood out while I was checking it. It says plainly that the paid tools are testnet-only and that the mainnet box holds no signing key, and I confirmed /api/v1/premium/signals does return 501 on mainnet rather than charging for something it can't serve. The devlog entry about the facilitator race condition, including the part that isn't fixed yet, is the kind of thing I wish more submissions had.

Most of it checks out end to end: x402Serve() matches the documented signature, nirium-cli@1.0.4 really does have create x402 and create bot -t py as written, the four read-only MCP tools are live against the mainnet agent right now, and the linked settlement is a real 0.02 USDC transfer over the Soroban USDC SAC — matching the $0.02 signals route exactly.

One thing I can't reconcile, and it's in the card description itself, so it would go straight onto the catalog:

The "April 2, 2026" date. The card and SKILL.md both say the endpoint has been billing on mainnet since 2 April 2026, "the day the x402 Foundation launched." But:

• the linked first-settlement tx 3134a51c…7558bc settled 2026-07-09T20:24:34Z (Horizon);
• the receiving account GCLBBPON…KBHP has no on-chain history at all before 2026-07-09T19:20:51Z;
• the Linux Foundation announced the x402 Foundation's operational launch on 14 July 2026, and x402 on Stellar went live 10 March 2026 (SDF blog).

April 2 doesn't match either event, and the chain says billing started in July. Could you correct the date in both places? If there's an earlier mainnet deployment under a different payTo that I didn't find, point me at a transaction and I'll gladly re-check.

Two smaller things while you're in there:

• The .env table sends everyone to channels.openzeppelin.com/gen, but the scaffold writes STELLAR_NETWORK=testnet, and keys are per-network — your own SDK error text notes that a mainnet key 401s against testnet. Worth adding the /testnet/gen URL to that row.
• Non-blocking: the root LICENSE is MIT, while the packages and the SKILL.md frontmatter say Apache-2.0.

On Copilot's review: the stray comma before "through the nirium-mcp server" is worth tidying in the same edit. I'd skip its suggestion to shorten the description generally, since the neighbouring catalog entries run about this long.

Happy to take another look as soon as the date is sorted.

[Eras256]

Fixed, thanks for the thorough check.

• Date: SKILL.md and the card description now say 9 July 2026, tied to nothing but the transaction itself — nirium-protocol/nirium-sdk@2bf5639 (skill repo), and 2c3b1d6 here for the card. Also dropped "First settlement" from SKILL.md's own wording (c7d16f3) — "first" claims nothing came before it, which isn't something we'd actually verified.
• Testnet key URL: added alongside the mainnet one in the .env table, matching what the CLI scaffold itself already writes into the generated .env comment.
• LICENSE: root was MIT, now Apache-2.0 to match every package.json and the SKILL.md frontmatter.

One thing that came up while re-checking the date against Horizon, separate from what you flagged: there's an earlier transaction to the same account, 8a2487b8..., about 18 minutes before the one linked in the skill (20:06:59Z vs 20:24:34Z), same 0.02 USDC amount, same source wallet. So 3134a51c... isn't actually the first payment that account ever received that day — there's at least one before it. That's part of why "first settlement" came out of the wording rather than just getting a date fix; didn't want to trade one unverified claim for another.

skills.ts also has the comma fix from Copilot's review applied, description length left alone.

[kaankacar]

🤖 Automated message from Kaan's Automated Triage Bot.

Thanks for turning this around so carefully — and for aligning the LICENSE too, which I'd only mentioned in passing.

All three points are resolved. The corrected date holds up against the chain: the payTo account GCLBBPON…KBHP was created 2026-07-09T19:20:51Z and took its first 0.02 USDC settlement at 20:06:59Z the same evening, so "since July 9, 2026" is right. The facilitator key row checks out against the official agentic-payments guidance too — a key really is required on both networks, with separate /testnet/gen and /gen URLs. And the read-only MCP tools still answer live on mainnet while /api/v1/premium/signals still returns 501 ("You were not charged"), which is the honesty that made this straightforward to list.

One tiny thing for whenever you're next in the file, not worth a commit on its own: the transaction you cite as "First settlement" is actually the fifth 0.02 USDC transfer that evening — the first is 8a2487b8…3170 at 20:06:59Z. Same day either way, so the card itself is accurate.

Merging now — welcome to the catalog.

[kaankacar]

🤖 Automated message from Kaan's Automated Triage Bot.

Verified end to end — the corrected mainnet date matches the chain, the facilitator key row matches the official x402 guidance, and the live endpoints behave as documented.

[Eras256]

Thanks Kaan — appreciate the thorough review, especially catching the date and license issues before this went live. Glad it's in 🙏