@tangleclaw/openclaw-ebay-research

OpenClaw plugin for read-only eBay market research — search current listings, fetch item detail, look up categories, query sold-listing history. Direct REST via the client_credentials OAuth flow (app token only — no seller account, no user OAuth, no MCP, no third-party gateway).

Built for OpenClaw agents that need to answer questions like:

• "What does a Nikon D750 sell for on eBay?"
• "What's the link to the best deal on a Nikon D750?"
• "Find me a used Nikon D750 under $500."
• "Tell me about this eBay listing: https://www.ebay.com/itm/..."
• "What did Nikon D750s actually sell for in the last 90 days?" (gated by Insights access)
• "What category should this go in on eBay?" (taxonomy lookup — useful for seller plugins too)

Every search result includes the canonical eBay itemWebUrl, so the agent can hand the operator clickable links — not just price text.

Status

v0.1.0 — scaffold + first three tools (auth_status, search_active_listings, get_item). Sandbox-tested where live keys are available; deploys in "demo mode" without keys (tools register but return a clear credentials-not-configured error until you drop a credentials JSON in place).

Tools

Install

1. Create an eBay developer app at https://developer.ebay.com/my/keys. You need either Sandbox keys (for testing) or Production keys (for real-world data). Note your App ID (Client ID) and Cert ID (Client Secret).

2. Write a credentials file at ~/.openclaw/secrets/ebay-research-credentials.json (mode 0600):

   {
     "client_id": "your-app-id",
     "cert_id": "your-cert-id",
     "environment": "sandbox"
   }
   

   Set environment to production once you've validated against sandbox.

3. Install the plugin into your OpenClaw gateway (typically inside the container):

   openclaw plugins install clawhub:@tangleclaw/openclaw-ebay-research
   openclaw plugins enable tangleclaw-ebay-research
   

   Why two commands? Community-installed OpenClaw plugins currently don't auto-enable on install — only bundled plugins do, due to a gating quirk in the OpenClaw runtime (filed upstream as openclaw/openclaw#87188, with empirical confirmation). The plugin's tools load fine after just install, but the ebay-research SKILL.md (the agent-bias layer that biases against narrating-without-calling, encodes recipes, surfaces itemWebUrl on every result, etc.) shows as blocked with Missing requirements: config:plugins.entries.tangleclaw-ebay-research.enabled. The plugins enable command flips that flag and activates the skill. This plugin already ships enabledByDefault: true in its manifest, so the second command will become unnecessary once #87188 ships.

4. Restart the gateway so it picks up the new plugin.

5. Try it — ask the agent: "what does a nikon d750 sell for on ebay?"

Configuration

Configurable via plugins.entries.tangleclaw-ebay-research.config.*:

Enabling Marketplace Insights (sold-listing data)

ebay_research_get_sold_history calls eBay's Marketplace Insights API, which is a gated surface — you must apply for access through the eBay Developer portal before it works:

1. Sign in at https://developer.ebay.com/ with your developer account.
2. Apply for Marketplace Insights API access (the listing is at the bottom of the API catalog page; approval is a separate process from regular app registration).
3. Once eBay grants access, set plugins.entries.tangleclaw-ebay-research.config.enableInsights = true and restart your OpenClaw gateway.
4. The plugin will request the additional buy.marketplace.insights OAuth scope automatically.

Until access is granted, leave enableInsights = false. The tool will still be visible to agents but will return a clear { status: "disabled", reason: "..." } response rather than hitting an authorization error.

How it works

• The plugin uses the client_credentials OAuth flow: at first tool call, it POSTs client_id + cert_id (HTTP Basic auth) to eBay's token endpoint and gets back an app-level access token (TTL ~2 hours). The token is cached at tokenPath and reused; when it expires, the plugin auto-refreshes silently.
• No user OAuth, no refresh tokens, no per-user consent — this token represents your eBay developer app, not any seller.
• Sandbox base URL: https://api.sandbox.ebay.com. Production: https://api.ebay.com. Decided by environment in your credentials file.
• All HTTP requests have a 30-second timeout.
• Errors return the eBay API's error code + message verbatim where possible.

Pairs well with

• @tangleclaw/openclaw-ebay-seller (sister plugin — read+write seller-side tools with OAuth + approval gating). The seller plugin's create_offer needs a category_id, which is exactly what this plugin's ebay_research_get_category_suggestions returns. Install both side-by-side.

More from @tangleclaw

• @tangleclaw/openclaw-google-oauth — Google Workspace tools for your OpenClaw agent (Gmail, Calendar, Drive, Docs, Sheets, Slides) via direct OAuth. Useful alongside this plugin when your agent needs to email Gmail summaries of eBay research, drop a sold-price comparison into a Drive spreadsheet, or schedule a Calendar reminder around a listing window. Install: openclaw plugins install clawhub:@tangleclaw/openclaw-google-oauth.

Out of scope (deferred to later versions)

• Bulk pricing-engine analysis across many SKUs.
• Buyer-side checkout / cart APIs.
• Trading API fallbacks (used only if a REST gap forces it).
• eBay Motors / specialty marketplaces.

License

MIT