Skip to main content

agent-checkout

Stripe payment links for merchants with AI agents - generate a link for your own product, a customer clicks and pays, you never touch card data. Free tier 100 links/day.

ソース情報

リポジトリ
oidsdev/honeypot
ソースの最終更新活動
2026年10月12日 21:36
検出された SKILL.md の言語
英語
スター
0
フォーク
1

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

ファイルエクスプローラー
2 ファイル

SKILL.md を表示中

SKILL.md
ソースの指示 · 読み取り専用プレビュー
name
agent-checkout
description
Stripe payment links for merchants with AI agents - generate a link for your own product, a customer clicks and pays, you never touch card data. Free tier 100 links/day.
# Agent Checkout - Stripe payment links for AI agents One API call turns "want to buy this?" into "here's the checkout link." Built for merchants whose AI agents sell their own goods and services. You are the merchant. Your customer completes the payment. You never see card data. Stripe handles checkout directly. You are the merchant of record - funds settle to YOUR connected Stripe account; the platform never holds them. Site: https://checkout.ignitionfoundry.com · Docs: https://checkout.ignitionfoundry.com/docs MCP server (dependency-free Python, stdlib only): https://github.com/oidsdev/agent-checkout-mcp ## When to use You sell something and need to collect payment. Generate a link, hand the `payment_url` to your customer, then poll the link status until `paid` is true. Use when your agent must trigger a real sale without ever handling payment credentials. 18+ only. ## Commands Get a key first (no card required): ```bash curl -s -X POST https://checkout.ignitionfoundry.com/v1/keys \ -H 'Content-Type: application/json' \ -d '{"email": "you@example.com", "agent_name": "my-agent"}' # -> {"api_key": "ack_live_...", "connect_url": "https://connect.stripe.com/..."} # Save the key - shown only once. Open connect_url in a browser (~3 min) to finish # Stripe Connect onboarding. Until that's done, link creation returns 403. ``` Create a checkout link: ```bash curl -s -X POST https://checkout.ignitionfoundry.com/v1/checkout-links \ -H "Authorization: Bearer ack_live_..." \ -H 'Content-Type: application/json' \ -d '{"amount_cents": 900, "currency": "usd", "product_name": "Widget"}' # -> {"payment_url": "https://checkout.stripe.com/...", "link_id": "cs_..."} # Give payment_url to your customer. They click, they pay. Done. ``` Check status: ```bash curl -s https://checkout.ignitionfoundry.com/v1/links/cs_... \ -H "Authorization: Bearer ack_live_..." # -> {"paid": true, "paid_at": "..."} ``` Usage stats: `GET /v1/stats` (tier, daily limit, used today). No-key demo: `POST /v1/demo-link` returns a mock of the real response. Nothing is created or charged. BYOK alternative: `POST /v1/byok` with your own Stripe key - zero platform fee. ## Gotchas - Complete Stripe Connect onboarding (the `connect_url`) before creating links - otherwise every call returns 403. This is the step everyone skips. - The customer pays, not you. Never send `payment_url` anywhere your customer won't see it. - `amount_cents` is an integer from 50 to 500000 ($0.50–$5,000). - Free tier: 100 links/day, then 429. Check `/v1/stats` before bulk runs. - In connect/byok modes links are Stripe Checkout Sessions (`cs_...`); both work the same from your side. - 401 means bad or revoked key - get a new one. 429 means daily limit hit.
GitHubで見る