Give your agent a wallet you control.
에이전트가 일회용 카드나 기계 결제 프로토콜로 온라인 결제하고, 모든 요청을 직접 승인
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기Bio link kind of payment platform by leveraging x402 protocol on casper network
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Live: pico-payment-casper.vercel.app · Follow: @picocspr · Buildathon: Casper Agentic Buildathon 2026 — Final Round qualifier · Program: Casper Forward Cohort 1 🏁
Creators and publishers lose their audience at the checkout page: nobody enters card details to read one article or unlock one PDF worth $0.25. Subscriptions over-ask, ads under-pay, and AI agents — the fastest-growing consumers of paid content — can't fill in a Stripe form at all. Micropayments have always been the obvious answer and have always failed on friction and fees.
Pico turns any piece of content into a pay-per-unlock link with fees low enough that a $0.10 price still makes sense. Two rails, one paywall:
Creators paste a wallet key, set a price, share a link. That's the whole onboarding.
Built for the Casper Agentic Buildathon 2026. Full docs: docs/CASPER.md
NEXT_PUBLIC_CASPER_NETWORK=casper-test (default) or casper switches the rail between Casper Testnet and Mainnet/p/[id] link — deploy signed by the Casper Wallet extension, verified on-chain server-side before unlockGET /api/casper/content/[id] returns HTTP 402 with machine-readable payment requirements; retry with X-Casper-Deploy-Hash after paying| App | https://pico-payment-casper.vercel.app |
| On-chain payments | payer account activity |
| PicoRouter contract (Odra) | hash-b4b5d701…a0608c — 95/5 fee splitter, source, deploy tx |
Pico isn't just agent-compatible — it ships its own autonomous buyer and an MCP server, so the full agent economy loop runs inside this repo: an AI with a budget discovers content, reasons about value, pays on-chain, and consumes what it bought. No human, no browser.
agent/buyer.js)An autonomous purchasing agent with its own Casper account, a goal, and a hard budget:
# one-time: create the agent's keypair (PEM, gitignored)
npm run agent:keygen
# fund the printed public key with free testnet CSPR (1000 CSPR):
# https://testnet.cspr.live/tools/faucet
# let it shop
export ANTHROPIC_API_KEY=sk-ant-… # enables Claude-powered decisions
npm run agent -- --goal "learn AI prompt engineering" --budget 50
The agent browses /api/casper/discover, fetches the 402 quote for
each item, and asks Claude whether the content is worth the price
given its goal and remaining budget. Spending policy (per-item cap,
session budget, balance check) is enforced in code, before the
model is consulted — the AI chooses within its allowance, never
over it. Every purchase is a real native transfer on Casper, linked
from the console output to cspr.live. Without an API key it falls
back to a conservative heuristic; --yes skips reasoning entirely.
agent/mcp-server.js)Exposes the rail as Model Context Protocol tools so any MCP-capable assistant (Claude Code, Claude Desktop, custom agents) can buy Pico content mid-conversation:
| Tool | Does |
|---|---|
wallet_status | agent account, live on-chain balance, spend cap |
discover_content | the paid-content catalog |
get_quote | 402 payment requirements for one item |
pay_and_unlock | sign + broadcast the CSPR transfer, verify on-chain, return content |
# register with Claude Code
claude mcp add pico -- node agent/mcp-server.js
# env: PICO_BASE_URL, CASPER_AGENT_KEY_PATH, MCP_MAX_SPEND_CSPR (default 25)
agent/pricer.js) — seller-side autonomyThe buyer agent makes the fan side autonomous. This one makes the seller side autonomous too — closing the agent-economy loop:
# creator opts in per link + sets min/max on the dashboard, then:
DATABASE_URL=... npm run pricer # dry-run: propose + log, no writes
DATABASE_URL=... npm run pricer -- --apply # write the nudge to production
For every opted-in link, the agent reads the last 7 days of
widget_views vs payments (Pico's built-in conversion funnel), asks
Claude for a price nudge grounded in that funnel, and writes the
proposal to the price_reviews audit table with the reason. Human
control stays intact: the creator sets the bounds, the agent can only
nudge inside them, and a 24h cooldown prevents cascades. Falls back to
a simple heuristic if ANTHROPIC_API_KEY isn't set. Point a cron at
npm run pricer -- --apply to run nightly.
Crawling agents can learn to transact with Pico unassisted:
/llms.txt (human/LLM-readable how-to) and
/.well-known/x402 (machine-readable manifest of both rails).
npm run agent:keygen creates a raw
ed25519 keypair; the PEM stays on disk (gitignored) and signing
happens locally.This is a Next.js project bootstrapped with create-next-app.
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Pico is fully open source under the MIT licence — the Next.js app, the
PicoRouter Odra contract, the buyer and pricing agents, and the MCP server are all
in this repository. Nothing is held back except secrets: wallet keys (*.pem,
agent/keys/), environment files and build artefacts are gitignored, as they
should be.
Note: "private": true in package.json is the npm flag that prevents the app
from being published to the npm registry. It says nothing about this repository,
which is public.
Contributions are welcome — see CONTRIBUTING.md, the code of conduct and the security policy.