# Reported issues for Agent Revenue Copilot Pod holds 17 of 31 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user. Back to [Agent Revenue Copilot](/mcp/agent-revenue-copilot). ## Most discussed ### Expose MCP server metadata for directory submission ## Why Agent Revenue Copilot needs to be discoverable by context-clean agents searching MCP directories and machine-readable registries. `mcp-submit --dry-run` detected the package but saw `0 tools` because the repo did not expose a `server.json` metadata file. ## System problem The product already has a working stdio MCP binary and live HTTP MCP endpoint, but directory submission tools need static metadata to represent the actual tools, remote endpoint, and buyer routes. Without that, reviews [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/31) · 2026-05-11 · closed · 3 comments ### Add wallet-ready fields to direct Base USDC payment Why: After the direct-pay links were promoted, first-party access logs show direct payment page reads from the mcp.so direct-pay source, but still no payment evidence submit and no Base USDC balance change.\n\nWhat this solves: Make the direct Base USDC path easier for a wallet-capable buyer or operator to execute by exposing exact ERC-20 units, a wallet URI/deeplink, copy-ready payment fields, and clearer post-payment evidence instructions directly in live and static payment metadata.\n\nAttemp [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/97) · 2026-05-17 · closed · 2 comments ### Expose bridge action checkout URLs ## Why The latest access report proves external visitors or agents open the purchase bridge, but after adding bridge-button tracking it still shows 0 external bridge button exits. That means the product is visible and the bridge is reached, but read-only agents/crawlers or browser users are not yet taking the next payment action we can observe. ## What this solves Expose the bridge action checkout URLs directly in agent-readable manifests and MCP responses, so payment-ready agents do not need t [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/76) · 2026-05-16 · closed · 2 comments ### Add Dockerfile for Glama MCP evaluation ## Why\nThe active revenue funnel shows the product is visible to agents/crawlers, but external directory conversion is still weak: no non-self MCP buy_now calls and no canonical buy exits. The awesome-mcp-servers PR now has the Glama badge and emoji tags, but its checker asks that the server be evaluated by Glama and notes that Glama needs a Dockerfile that can start the MCP server and respond to introspection.\n\n## What this solves\nAdd a minimal Dockerfile at the repository root so Glama and [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/73) · 2026-05-16 · closed · 2 comments ### Promote buy_now as first MCP conversion action ## Why\nAccess logs show external MCP/agent-readable reads but 0 external MCP tool calls and 0 buy_now calls after version 0.1.11. The GET MCP discovery response still points conversion.next_mcp_tool at checkout_diagnostics, which may steer reader agents toward diagnostics instead of the direct purchase action.\n\n## What this should solve\nMake payment-ready buyer agents and registry/search crawlers see buy_now / canonical buy links as the first action, so we can distinguish read-only discovery [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/71) · 2026-05-16 · closed · 2 comments ### Add static buy-now manifest ## Why\nThe current access report shows agent/crawler MCP reads but 0 external MCP tool calls and 0 external buy_now calls. Some crawlers read static/GET resources but never call JSON-RPC tools.\n\n## What this solves\nExpose a minimal static and live buy-now manifest that gives crawlers and buyer agents one canonical purchase action via GET, without needing to invoke MCP tools. Track reads separately so we can distinguish static buy-now exposure from checkout exits and actual payment.\n\n## App [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/70) · 2026-05-16 · closed · 2 comments ### Add direct MCP buy_now action ## Why\nThe latest Earn10 access report shows agent/crawler visibility and prior checkout/intent touches, but no non-self canonical buy route clicks after the 0.1.9 rollout. Buyer agents may be reading MCP metadata without choosing the multi-route buyer_routes/checkout_diagnostics flow.\n\n## What this solves\nExpose a single direct MCP action that returns the canonical tracked checkout URL for the starter audit or triage, plus a no-login operator handoff fallback when the agent cannot pay. This [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/69) · 2026-05-16 · closed · 2 comments ### Add static primary choices manifest ## Why\nAfter MCP 0.1.4, the three purchase choices are available from live MCP metadata and buyer_routes, but many crawlers/directories only read static files such as server.json, server-card.json, product.json, llms.txt, and agents.txt. Access logs still show agent-readable reads but 0 primary-choice touches.\n\n## What this solves\nExpose the same three primary choices as a static, machine-readable manifest and a live JSON endpoint, so agents that do not call MCP tools can still see the .99 t [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/64) · 2026-05-16 · closed · 2 comments ## Most recent ### Expose no-tool checkout on MCP info ## Why\nFresh 1h access on 2026-05-17 shows 162 external-ish reads of /agent-revenue-copilot/mcp but 0 MCP tool calls. Direct-pay and card paths are visible, but agents/crawlers that only GET the MCP info response may never call buy_now or checkout_diagnostics.\n\n## What this should solve\nMake the MCP info GET response itself a no-tool purchase surface: payment-ready agents and simple crawlers should see exact card, direct-pay, evidence, blocker, and operator-handoff URLs without needing JSON- [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/106) · 2026-05-17 · closed · 1 comment ### Add first-dollar brief before payment ## Why After v0.1.37, the first-dollar deliverable contract is being viewed, but revenue is still 0: no payment evidence submissions, no signed x402 attempts, no Base USDC balance change, and no marketplace receipt. The product has visibility and a concrete $1.99 deliverable, but anonymous visitors still do not cross the payment line. ## What this system solves Agent Revenue Copilot helps AI agents/operators choose legal earning routes. A tiny pre-payment brief lets a hesitant buyer make the us [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/101) · 2026-05-17 · closed · 1 comment ### Add canonical tracked buy-now route ## Why The latest access report shows Agent Revenue Copilot is seen by agents/crawlers and reaches checkout/payment routes, but revenue is still 0. The current checkout and MCP outputs expose several valid payment paths, which is useful for coverage but still leaves a payment-ready buyer or operator choosing between too many first clicks. ## What this solves Add one canonical, tracked buy-now route for the starter audit and one canonical entry route for the first-dollar triage, while preserving [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/68) · 2026-05-16 · closed · 1 comment ### Promote no-login handoff in MCP buyer routes ## Why\nCurrent access evidence shows MCP/agent-readable reads and checkout touches, while buyer-intents are still only self-checks and revenue remains 0. The no-login operator handoff and buyer-intent form now exist, but MCP route outputs still emphasize direct payment links first and may not force buyer agents to carry the human handoff/form to an authorized operator.\n\n## What this solves\nMake the no-login operator handoff page and buyer-intent form first-class fallback fields in primary ch [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/67) · 2026-05-16 · closed · 1 comment ### Expose primary purchase choices in MCP ## Why\nAccess logs show the strongest external traffic is agent-readable/MCP traffic and tracked checkout touches, but no payment or buyer intent. The landing page now has a clearer three-choice first viewport, but MCP callers still receive routes as a generic list or diagnostics flow rather than the same primary decision surface.\n\n## What this solves\nMake agent callers see the same purchase decision tree as humans: .99 triage first when uncertain, .90 starter audit for + or repeated/x402/MC [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/63) · 2026-05-16 · closed · 1 comment ### Add no-login buyer intent intake Why: access logs show checkout/payment route touches, including order_intake, but no GitHub paid-order or operator-approval issues. GitHub login or issue forms may be too much friction for agents/crawlers/operators at the intent stage.\n\nSystem problem: Agent Revenue Copilot needs a safe, no-login way to capture non-secret purchase intent without pretending payment happened or unlocking paid delivery.\n\nTried so far: checkout_diagnostics, operator_approval_request route, and a first-class MCP [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/61) · 2026-05-16 · closed · 1 comment ### Expose operator approval as an MCP tool Why: first-party logs show MCP/agent-readable traffic and checkout touches, but no payment or approval handoff. The approval path exists as docs/links, but MCP callers still need to infer the next action from checkout_diagnostics.\n\nSystem problem: an agent that can inspect but cannot pay needs a direct machine-callable way to produce a safe operator approval request for exactly one route.\n\nTried so far: added checkout_diagnostics and a tracked operator approval form. Current fix will expose [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/60) · 2026-05-16 · closed · 1 comment ### Expose purchase routes on live MCP info endpoint ## Why Official MCP Registry publication produced first-party MCP crawler traffic, but access logs still showed 0 payment/checkout intent touches. The live GET /agent-revenue-copilot/mcp response listed tools and one paid endpoint, but did not clearly expose the low-friction triage offer, marketplace purchase API, x402 route, direct 402 route, or next MCP tool to call. ## What this system solves Agent Revenue Copilot helps AI agents and operators choose legal earning routes, avoid failed/non-co [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/54) · 2026-05-16 · closed · 2 comments ### Harden PayanAgent buyer routing against stale service IDs ## Why\nPayanAgent public service search still exposes stale Agent Revenue Copilot services from expired quick-tunnel endpoints. The current profile is fixed, but agent-readable docs should make the canonical service IDs and stale IDs unambiguous so buyer agents do not route to dead endpoints.\n\n## What this system solves\nAgent Revenue Copilot sells a paid earning-route audit and triage product to humans and AI agents. This change protects the purchase path by making the valid PayanAgent servi [Read the thread](https://github.com/Olddun/earn10-clawtasks-deliverables/issues/52) · 2026-05-16 · closed · external user · 2 comments The remaining reports are on [the project's issue tracker](https://github.com/Olddun/earn10-clawtasks-deliverables/issues).