x402 action provider: optional pre-pay spot-check hook
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 8/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- typescript
- Domain
- payments
Research direction
The payload names no file or entry point in agentkit. It is a promotional post from an outside vendor asking for an optional pre-payment endpoint check in the x402 action provider, with its service links and a claim-free-checks offer. Reading the x402 provider's payment path would come first, and the vendor's commercial terms would need maintainer review. Done would mean a maintainer-approved design, not a patch.
Written by the indexing model from the issue text.
Description
The x402 action provider lets an agent pay whatever a listing says. One listing I checked, GET https://frog03-20494.wykr.es/api/signals/paid, is listed at $0.01 but returns HTTP 200 with no 402 challenge (receipt ae218e0fb7). An agent could sign for a listing that never asks for payment.
x402 Endpoint Spot-Check could run as an optional hook before payment. Free tier gives a verdict and a reason. Paid costs 1/10 of the target's price, ($0.01-$0.25), and returns price, pay-to and network. It never pays the target, and it's SSRF-safe.
Drop-in wrapper (MIT): https://github.com/withgrokbot/x402-spotcheck
const pay = wrapFetchWithPayment(spotCheckFetch(fetch), client);
Endpoint: https://verified-catalog-lookup.withgrokbot.workers.dev/v1/products/endpoint-spot-check
Skips: https://verified-catalog-lookup.withgrokbot.workers.dev/v1/skips
The first router to integrate gets 1,000 free checks: open an issue on the wrapper repo to claim them.
withgrokbot ([email protected])
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 842
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from coinbase/agentkit
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
coinbase-agentkit 0.7.x fails on fresh install: imports solana.rpc.api, which solana>=0.37 removedPossibly taken @JulienKervarrec claimed this 17 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 45/100
coinbase/agentkit#1547 · 3 comments ·
Maintainers usually reply within 1 day
-
Community Action Provider: Agent Safe paid_fetch, x402 payments where the model only picks the URLOpen
Difficulty 4/5 1-2 days Newbie friendliness 15/100
coinbase/agentkit#1544 · 22 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
All issues in coinbase/agentkit
Similar issues
-
effort:S priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
cameri/nostream#811 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
dam-agents/dam#4562 ·
Maintainers usually reply within 1 day
-
bug p3 triaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug javascript P2-medium python release:v3.1
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
adrirubio/claude-deck#546 ·
Maintainers usually reply within 1 day