Update index.json - add @targe/plugin-eliza — LLM token sharing via U…

[pabloleaf]

…SDC micropayments

This adds @targe/plugin-eliza to the registry — a plugin that integrates Eliza agents with
Targe, an LLM token sharing marketplace built on x402 and Base.

Note: elizaOS already operates x402.elizaos.ai, which uses the
same x402 payment standard this plugin is built on.

What this enables for Eliza agents:

• Call Claude, GPT, or Gemini via pool proxy — drop-in API format, pay per token in USDC, no API key required
• Register an idle LLM key to earn USDC — 90% of token revenue goes to the key owner's wallet
• Self-funding loop — earnings credit the same wallet used for pool calls. An agent that shares enough capacity can cover its own LLM costs permanently

Actions: TARGE_CALL_POOL, TARGE_REGISTER_KEY, TARGE_CHECK_BALANCE, TARGE_CHECK_EARNINGS

Provider: TARGE_CONTEXT — injects pool status and balance into every message context

Links:

• npm: https://www.npmjs.com/package/@targe/plugin-eliza
• GitHub: https://github.com/pabloleaf/plugin-targe
• Targe API: https://api.targe.io
• Agent card (ERC-8004): https://api.targe.io/.well-known/agent.json

Network: Base Mainnet, USDC payments, x402 protocol

Registry Update Checklist

Registry:

• I've made the left side of the colon of JSON entry in index.json match the potential NPM package name
• I've used github not github.com
• There is no .git extension
• It's placed it alphabetically in the list
• I've dealt with commas properly so the list is still valid JSON

If not an eliza-plugins official repo, i.e. new plugin:

The plugin repo has:

• is publically accessible (not a private repo)
• uses main as it's default branch
• I have include elizaos-plugins in the topics in the GitHub repo settings. If the plugin is related to AI or crypto, please add those as topics as well.
• add simple description in github repo
• follows this convention

plugin-name/
├── images/
│   ├── logo.jpg        # Plugin branding logo
│   ├── banner.jpg      # Plugin banner image
├── src/
│   ├── index.ts        # Main plugin entry point
│   ├── actions/        # Plugin-specific actions
│   ├── clients/        # Client implementations
│   ├── adapters/       # Adapter implementations
│   └── types.ts        # Type definitions
│   └── environment.ts  # runtime.getSetting, zod validation
├── package.json        # Plugin dependencies
└── README.md          # Plugin documentation

• an images/banner.jpg and images/logo.jpg and they
  • Use clear, high-resolution images
  • Keep file sizes optimized (< 500KB for logos, < 1MB for banners)
  • Follow the elizaOS Brand Guidelines
  • Include alt text for accessibility
• package.json has a agentConfig like the following

{
  "name": "@myNpmOrg/plugin-example",
  "version": "1.0.0",
  "agentConfig": {
    "pluginType": "elizaos:plugin:1.0.0",
    "pluginParameters": {
      "API_KEY": {
        "type": "string",
        "description": "API key for the service"
      }
    }
  }
}

Summary by CodeRabbit

• New Features
  • Added two mapping entries for the "@targe/plugin-eliza" plugin in the project manifest, enabling access to the plugin from configured sources.
  • No removals or other functional changes; this update solely introduces the additional mapping entries.

Greptile Summary

This PR adds @targe/plugin-eliza (pointing to github:pabloleaf/plugin-targe) to the elizaOS plugin registry, enabling Eliza agents to interact with the Targe LLM token-sharing marketplace via x402/USDC micropayments on Base Mainnet.

• The JSON entry itself is correctly formatted (no .git extension, uses github: not github.com:, key matches the npm package name)
• The entry is placed in the wrong alphabetical position — it is inserted between @elizaos/plugin-sui and @elizaos/plugin-tee inside the @elizaos namespace block. Since @targe sorts after @elizaos (and after @standujar but before @theschein among third-party namespaces), it should be moved to between @standujar/plugin-composio and @theschein/plugin-polymarket
• All PR checklist items are left unchecked by the author

Confidence Score: 3/5

• Safe to merge after fixing the alphabetical placement of the new registry entry.
• The change is a single-line registry addition with correct formatting (no .git, proper github: prefix, key matches npm name), but the entry is placed in the wrong alphabetical position — in the middle of the @elizaos block instead of among the other third-party namespace entries. This does not break JSON validity but violates the stated registry conventions.
• index.json — the new entry needs to be relocated to its correct alphabetical position among third-party namespace entries.

Important Files Changed

Filename	Overview
index.json	Adds @targe/plugin-eliza registry entry, but the entry is placed in the middle of the @elizaos section rather than in the correct alphabetical position among third-party namespace entries.

Sequence Diagram

sequenceDiagram
    participant Agent as Eliza Agent
    participant Plugin as @targe/plugin-eliza
    participant Targe as Targe API (api.targe.io)
    participant LLM as LLM Pool (Claude/GPT/Gemini)
    participant Base as Base Mainnet (USDC/x402)

    Agent->>Plugin: TARGE_CHECK_BALANCE
    Plugin->>Targe: GET /balance
    Targe-->>Plugin: USDC balance
    Plugin-->>Agent: Balance context injected (TARGE_CONTEXT)

    Agent->>Plugin: TARGE_CALL_POOL
    Plugin->>Targe: POST /proxy (x402 payment)
    Targe->>Base: Deduct USDC micropayment
    Targe->>LLM: Forward LLM request
    LLM-->>Targe: LLM response
    Targe-->>Plugin: Response + receipt
    Plugin-->>Agent: LLM output

    Agent->>Plugin: TARGE_REGISTER_KEY
    Plugin->>Targe: POST /register (API key)
    Targe-->>Plugin: Registration confirmed
    Note over Targe,Base: 90% of token revenue<br/>credited to owner wallet

    Agent->>Plugin: TARGE_CHECK_EARNINGS
    Plugin->>Targe: GET /earnings
    Targe-->>Plugin: Earnings in USDC
    Plugin-->>Agent: Earnings info

Loading

_{Last reviewed commit: 7e64787}

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

[coderabbitai]

Walkthrough

A new public plugin mapping entry has been added to index.json, registering the package "@targe/plugin-eliza" to point to its GitHub repository at "github:pabloleaf/plugin-targe".

Changes

Cohort / File(s)	Summary
Configuration index.json	Added new public mapping entry for "@targe/plugin-eliza" plugin package.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop, a skip, a mapping refined,
New plugin entries, perfectly aligned,
Through GitHub's pastures, our registry grows,
One simple addition—as the rabbit well knows! 🌟

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description includes a completed registry checklist with most items marked, but the checklist indicates unchecked items for 'I've used github not github.com' and image requirements, suggesting incomplete verification.	Verify that the entry uses 'github:' not 'github.com:' and confirm whether image requirements (banner.jpg, logo.jpg) have been checked in the actual plugin repository before merging.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly reflects the main change: adding @targe/plugin-eliza to the registry with focus on LLM token sharing via USDC micropayments.
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
• 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[greptile-apps]

Incorrect alphabetical placement

The @targe/plugin-eliza entry is placed in the middle of the @elizaos namespace block (between @elizaos/plugin-sui and @elizaos/plugin-tee). Since the @targe namespace sorts after @elizaos alphabetically (t > e), it should be placed among the other third-party namespace entries — specifically between @standujar/plugin-composio and @theschein/plugin-polymarket (around line 236-237 in the current file).

The checklist for this PR explicitly lists: "It's placed alphabetically in the list" as a requirement.

Please move the entry to its correct alphabetical position:

  "@standujar/plugin-composio": "github:standujar/plugin-composio",
  "@targe/plugin-eliza": "github:pabloleaf/plugin-targe",
  "@theschein/plugin-polymarket": "github:Okay-Bet/plugin-polymarket",