Skip to content

Add Nightmarket skill — API marketplace for AI agents#6554

Open
streacy wants to merge 5 commits intoelizaOS:developfrom
streacy:add-nightmarket-skill
Open

Add Nightmarket skill — API marketplace for AI agents#6554
streacy wants to merge 5 commits intoelizaOS:developfrom
streacy:add-nightmarket-skill

Conversation

@streacy
Copy link

@streacy streacy commented Mar 5, 2026

What this adds

A new Nightmarket skill in packages/skills/skills/nightmarket/ that gives Eliza agents the ability to discover and call paid third-party API services through the Nightmarket marketplace.

How it works

Nightmarket is an API marketplace where AI agents find and pay for third-party services (data enrichment, analytics, AI models, content generation, etc.). Every call settles on-chain in USDC on Base using the x402 payment protocol — no API keys or subscriptions needed.

The skill includes:

  • SKILL.md — main skill doc with search, call, and payment flow instructions
  • references/api.md — full API reference (endpoints, headers, error codes)
  • references/crow-payments.md — CrowPay integration for automatic 402 payment handling
  • references/mcp.md — optional MCP server setup for tool-based access

Why this is useful for Eliza

Eliza agents can use this skill to autonomously access any external API on the marketplace without the user needing to configure API keys or billing for each service individually. The agent searches, pays per-call in USDC, and gets the response — all within a single interaction.

This complements Eliza's existing plugin ecosystem by giving agents access to a growing marketplace of paid services through a single, standardized interface.

Integration

Follows the existing packages/skills/skills/ directory structure and SKILL.md format used by other Eliza skills.

Greptile Summary

This PR adds a new nightmarket skill — a documentation-only package teaching Eliza agents how to discover and pay for third-party APIs through the Nightmarket marketplace using the x402 payment protocol (HTTP 402 + on-chain USDC settlement on Base).

The documentation is generally well-organized, but there are four issues that need addressing before merge:

  1. Wrong install targets: Both nightmarket and crow skill install commands reference Fallomai/skills instead of elizaos/eliza. After merge, users would be directed away from the official repo.

  2. Inconsistent payment-signature encoding: crow-payments.md specifies base64(JSON.stringify(response_body)) encoding for the payment-signature header, but SKILL.md omits this detail. An agent reading only SKILL.md will construct a malformed header.

  3. Wallet private key in config file: mcp.md instructs users to place raw WALLET_KEY in JSON config files without warning about the danger of accidentally committing it to version control.

Confidence Score: 2/5

  • Not safe to merge as-is — install commands direct users to wrong repository, and agent-facing documentation has inconsistencies that will cause payment flows to fail or confuse implementers.
  • Three verified issues require fixing: (1) both install commands point to an external repo, a functional correctness issue that will misdirect users after merge; (2) payment-signature encoding is specified in crow-payments.md but missing from SKILL.md, creating a logic gap; (3) wallet private key placement in config files without security warnings exposes users to accidental version-control leaks. These are all concrete, reproducible problems.
  • packages/skills/skills/nightmarket/SKILL.md and packages/skills/skills/nightmarket/references/mcp.md need the most attention for the install commands and security warning respectively.

Last reviewed commit: d1e131d

Greptile also left 4 inline comments on this PR.

(4/5) You can add custom instructions or style guidelines for the agent here!

Context used:

  • Rule from dashboard - Docs in README.md only; consolidate files; avoid bloat (source)

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 5, 2026

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3d0b03e7-36d0-4032-88a4-e351b0d34504

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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

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

@odilitime odilitime added the 2.x V3 label Mar 5, 2026
…, security warning

- Fix skill install commands to reference elizaos/eliza instead of Fallomai/skills
- Document payment-signature base64 encoding requirement in SKILL.md
- Add security warning about WALLET_KEY in MCP config
@streacy
Copy link
Author

streacy commented Mar 5, 2026

Addressed all review feedback:

  • Install paths fixed: Both skill install commands now reference elizaos/eliza instead of Fallomai/skills
  • Payment encoding documented: Added base64 encoding specification to SKILL.md CrowPay section
  • Security warning added: Added warning about never committing WALLET_KEY to version control in MCP config docs

Thanks for the thorough review!

streacy and others added 3 commits March 4, 2026 22:05
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants