원클릭으로 Manus에서 모든 스킬 실행

peage-agent-wallet

스타0

포크0

업데이트2026년 7월 17일 14:05

Hold and spend a prepaid fiat wallet on the peage rail (peage.intrane.fr) — create/fund/check a wallet, pay peage-metered APIs per call via the X-Peage-Wallet header, handle 402 responses, set spending caps, verify receipts. Use when an API answers 402 mentioning peage, when the operator wants pay-per-call API access without subscriptions, or when managing an existing pw_ wallet token.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

javimosch

javimosch/peage

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

peage: agent wallet

Base URL: https://peage.intrane.fr (hosted; no install). Full contract: GET /llms.txt. Money is integer cents (EUR) everywhere. Your credential is the wallet token pw_….

Setup (once)

curl -s -X POST https://peage.intrane.fr/v1/wallets -d '{"email":"<operator email>"}' → {"wallet_id":"w_…","token":"pw_…"}. The token is shown once — persist it somewhere durable immediately (your memory/config, e.g. ~/.config/peage/wallet).
Fund it: curl -s -X POST …/v1/topup -H 'Authorization: Bearer pw_…' -d '{"amount_cents":1000}' → {"url":"https://checkout.stripe.com/…"}. You cannot pay this yourself: give the URL to your human operator and say what it's for. Min 500 by default, max 20000 cents; a 402 from a merchant may carry {merchant_id, min_cents} — pass that merchant_id in the topup body to use its (possibly lower, floor 300) minimum. The wallet credits automatically after payment (webhook); confirm with step 3.
curl -s …/v1/wallet -H 'Authorization: Bearer pw_…' → balance, caps, recent charges.

Discovering what to pay for

Don't know which APIs take peage? The MCP peage_services tool (or the merchant list in the README) is the directory — currently relais (a hosted inbox/webhook-catcher your agent can block on), grepapi (lead-gen), hart (artifact publishing), and the demo fortune. Call any of them with your wallet attached (see below).

Spending

Pass the token to any peage-metered API in the header it advertises (convention: X-Peage-Wallet: pw_…). The merchant charges your wallet per call and should include the receipt in its response. Try the loop safely: GET /demo/fortune costs 1¢.

Handling HTTP 402

From a merchant API (no wallet sent): the body advertises the rail: {"pay":{"rail":"peage","url":…,"price_cents":N,"header":"X-Peage-Wallet"}} — retry the same request with your wallet header.
From peage (insufficient funds): body has wallet_balance_cents, needed_cents, and top-up instructions. Run the topup flow (Setup step 2) — this requires your human.

Safety rails (yours, not the merchant's)

Defaults: max 100¢ per charge, 1000¢ per merchant per day. A merchant holding your token can never exceed them. Adjust: POST /v1/wallet/limits -H 'Authorization: Bearer pw_…' -d '{"max_charge_cents":50,"daily_cap_cents":500}'

Never share the wallet token in logs or with humans other than your operator. Sharing it with a merchant API is normal — that is how they charge you; the caps bound the risk.

Auditing

History: GET /v1/wallet (last 20 charges: merchant, amount, memo).
Verify any receipt without auth: GET /v1/receipts?r=<receipt> → {"valid":true, …}. Report unrecognized charges to your operator; they can lower the caps to 0 to freeze spend.

이 저장소의 다른 Skills

같은 저장소

peage-merchant

javimosch/peage

Meter an API with the peage rail (peage.intrane.fr) — register as a merchant, charge caller wallets per request with POST /v1/charge, advertise prices via HTTP 402, use idempotency keys, check balance/volume. Use when adding pay-per-call monetization to any HTTP service without building payments, or when operating an existing pm_ merchant key.

2026-07-170

peage-embed

javimosch/peage

Embed an optional peage merchant hook into an OSS tool or self-hostable service so ANY self-hoster can charge callers per invocation with two env vars and zero payments code. Use when adding monetization support to an open-source CLI, server, or library — as the author shipping the hook, or as a self-hoster enabling it.

2026-07-160

name	peage-agent-wallet
description	Hold and spend a prepaid fiat wallet on the peage rail (peage.intrane.fr) — create/fund/check a wallet, pay peage-metered APIs per call via the X-Peage-Wallet header, handle 402 responses, set spending caps, verify receipts. Use when an API answers 402 mentioning peage, when the operator wants pay-per-call API access without subscriptions, or when managing an existing pw_ wallet token.

peage: agent wallet

Base URL: https://peage.intrane.fr (hosted; no install). Full contract: GET /llms.txt. Money is integer cents (EUR) everywhere. Your credential is the wallet token pw_….

Setup (once)

curl -s -X POST https://peage.intrane.fr/v1/wallets -d '{"email":"<operator email>"}' → {"wallet_id":"w_…","token":"pw_…"}. The token is shown once — persist it somewhere durable immediately (your memory/config, e.g. ~/.config/peage/wallet).
Fund it: curl -s -X POST …/v1/topup -H 'Authorization: Bearer pw_…' -d '{"amount_cents":1000}' → {"url":"https://checkout.stripe.com/…"}. You cannot pay this yourself: give the URL to your human operator and say what it's for. Min 500 by default, max 20000 cents; a 402 from a merchant may carry {merchant_id, min_cents} — pass that merchant_id in the topup body to use its (possibly lower, floor 300) minimum. The wallet credits automatically after payment (webhook); confirm with step 3.
curl -s …/v1/wallet -H 'Authorization: Bearer pw_…' → balance, caps, recent charges.

Discovering what to pay for

Spending

Handling HTTP 402

From a merchant API (no wallet sent): the body advertises the rail: {"pay":{"rail":"peage","url":…,"price_cents":N,"header":"X-Peage-Wallet"}} — retry the same request with your wallet header.
From peage (insufficient funds): body has wallet_balance_cents, needed_cents, and top-up instructions. Run the topup flow (Setup step 2) — this requires your human.

Safety rails (yours, not the merchant's)

Never share the wallet token in logs or with humans other than your operator. Sharing it with a merchant API is normal — that is how they charge you; the caps bound the risk.

Auditing

History: GET /v1/wallet (last 20 charges: merchant, amount, memo).
Verify any receipt without auth: GET /v1/receipts?r=<receipt> → {"valid":true, …}. Report unrecognized charges to your operator; they can lower the caps to 0 to freeze spend.