Add moltspay-eliza-plugin to registry

[Yaqing2023]

Plugin: moltspay-eliza-plugin

MoltsPay plugin for ElizaOS - enables AI agents to discover and pay for services using x402 protocol.

Features

• 🔐 8 actions: init, status, pay, fund, faucet, services, config, list
• 💳 Gasless USDC payments via x402 protocol
• 🔒 Built-in spending limits for safety
• 🌐 Bilingual support (EN/CN)
• ⛓️ Multi-chain: Base, Polygon, Base Sepolia (testnet)

Links

• npm: https://www.npmjs.com/package/moltspay-eliza-plugin
• GitHub: https://github.com/Yaqing2023/moltspay-eliza-plugin
• Docs: https://moltspay.com

Topics

Repo has required topic: elizaos-plugins ✅

Summary by CodeRabbit

• New Features
  • Added a new plugin source to expand available integrations, increasing the set of available plugins.
  • Change is additive only (no removals or breaking changes) and low risk for users.

Greptile Summary

This PR adds a single entry to the elizaOS plugin registry for moltspay-eliza-plugin, a payment plugin enabling AI agents to discover and pay for services using the x402 protocol with gasless USDC payments on Base, Polygon, and Base Sepolia networks.

Key observations:

• The JSON format is valid, uses the correct github: prefix, has no .git extension, and is properly comma-delimited ✅
• The entry is correctly placed alphabetically among the unscoped entries at the end of index.json (after all @-scoped entries, before plugin-connections) ✅
• The package name moltspay-eliza-plugin uses a {service}-eliza-plugin naming order, which is the inverse of the registry-recommended plugin-{name} convention — all other unscoped entries follow plugin-{name} (e.g., plugin-connections, plugin-moltbazaar)

Confidence Score: 4/5

• This PR is safe to merge — it is a minimal, well-formed registry entry with only a minor naming convention deviation.
• The change is a single-line addition to index.json. The JSON is valid, alphabetically sorted, and uses the correct github: reference format. The only minor concern is the unconventional package name ordering ({service}-eliza-plugin rather than plugin-{service}), but this is a style issue and not a blocker since the key is meant to match the actual npm package name.
• No files require special attention.

Important Files Changed

Filename	Overview
index.json	Adds a single entry mapping moltspay-eliza-plugin to github:Yaqing2023/moltspay-eliza-plugin. The format is valid JSON, uses the correct github: prefix (no .git extension), and is alphabetically placed correctly among unscoped entries. The only concern is that the package name uses {service}-eliza-plugin ordering instead of the registry-recommended plugin-{name} convention.

Sequence Diagram

sequenceDiagram
    participant User as ElizaOS User
    participant CLI as ElizaOS CLI
    participant Registry as registry/index.json
    participant GH as github:Yaqing2023/moltspay-eliza-plugin
    participant X402 as x402 Protocol
    participant Chain as Base/Polygon Blockchain

    User->>CLI: Install moltspay-eliza-plugin
    CLI->>Registry: Look up "moltspay-eliza-plugin"
    Registry-->>CLI: github:Yaqing2023/moltspay-eliza-plugin
    CLI->>GH: Fetch plugin source
    GH-->>CLI: Plugin code
    CLI-->>User: Plugin installed

    User->>CLI: Agent triggers pay action
    CLI->>GH: Execute payment action
    GH->>X402: Initiate x402 payment request
    X402->>Chain: Submit gasless USDC transaction
    Chain-->>X402: Transaction confirmed
    X402-->>GH: Payment receipt
    GH-->>CLI: Payment result
    CLI-->>User: Payment complete

Loading

_{Last reviewed commit: "Add moltspay-eliza-p..."}

Greptile also left 1 inline comment on this PR.

_{(2/5) Greptile learns from your feedback when you react with thumbs up/down!}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e20a45ab-9948-4277-b4ae-29a0e6c3acb6

📥 Commits

Reviewing files that changed from the base of the PR and between 58304c2 and 84ff199.

📒 Files selected for processing (1)

• index.json

✅ Files skipped from review due to trivial changes (1)

• index.json

---

Walkthrough

A single-line addition to index.json registers a new plugin source mapping: @moltspay/plugin-elizaos → github:Yaqing2023/moltspay-eliza-plugin. No control flow, error handling, or exported signatures were changed.

Changes

Cohort / File(s)	Summary
Plugin Source Addition index.json	Added new mapping @moltspay/plugin-elizaos → github:Yaqing2023/moltspay-eliza-plugin (one-line config addition).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 I hopped a line into the stack,
A tiny map, no code to crack.
New plugin sprung, a gentle cheer,
Quiet change — the meadow's near. ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description includes plugin details, features, and links, but lacks coverage of critical registry checklist items from the template (alphabetical placement verification, comma validation, repo accessibility, default branch, topics, images, and package.json structure).	Explicitly verify and document each checklist item from the template, particularly alphabetical placement, JSON validity, public repo status, main branch, required topics, and plugin directory structure compliance.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add moltspay-eliza-plugin to registry' is clear, concise, and accurately summarizes the main change—adding a single plugin entry to the registry.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Non-standard package naming convention

The entry key moltspay-eliza-plugin uses the {service}-eliza-plugin format, which is the reverse of the convention recommended by the registry guidelines and the PR checklist (plugin-{name} or @scope/plugin-{name}). The README's format requirements show @npm-package-name as the expected key format, with the PR template example explicitly showing @myNpmOrg/plugin-example.

While there are a few other unscoped entries in the registry (e.g., plugin-connections, plugin-moltbazaar), they all follow plugin-{name} — moltspay-eliza-plugin is the only entry that puts the service name first. If the npm package name is fixed as moltspay-eliza-plugin, this is acceptable, but the author may want to consider publishing under a scoped name like @moltspay/plugin-eliza or @moltspay/plugin-payments for better consistency with the ecosystem convention.

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

[Yaqing2023]

Hi maintainers! 👋

Just checking in on this PR. The plugin is fully functional and published on npm. Would appreciate a review when you get a chance.

Happy to make any changes if needed. Thanks!

[Yaqing2023]

Updated! ✅

Renamed package to @moltspay/plugin-elizaos per the naming convention feedback.

The npm package has been republished under the new scoped name and the registry entry has been updated accordingly.