feat(skills): fix stale economics, add secure-wallet, add the merchant skill - #59
Open
enot3615 wants to merge 1 commit into
Open
feat(skills): fix stale economics, add secure-wallet, add the merchant skill#59enot3615 wants to merge 1 commit into
enot3615 wants to merge 1 commit into
Conversation
…t skill Three things, all so an agent — on any platform — can act on the skill without a human explaining it. 1. STALE ECONOMICS, in a public file. The payer skill said "98.99 / 1 / 0.01". That is the v1.2 fee-on-top model. The canon is AIFP-1: the agent pays the quoted price, AiFinPay takes 100 bps from it, the merchant receives 99%, the creator 0 — enforced on-chain by the v1.3/v1.4 splitter and verified on Polygon and Solana on 2026-09-04. A skill that misstates the fee is a skill that quotes an agent the wrong number. 2. SECURE WALLET, which the skill did not mention at all: recovery is printed once in the terminal and never in chat; an ephemeral agent never prints its key; AIFINPAY_WALLET_PASSPHRASE encrypts the keystore; one seed derives every chain. Plus describeQuote, so the agent sees what a payment buys rather than a bare "1.06 POL", and the orderIdHash/nonce that stop a double-pay. 3. THE MERCHANT SKILL — the other side of a two-sided platform, and the missing entry point. Today an agent scrapes a site for free; this skill turns any site into one that charges agents per request, with one middleware, keeping 99%. It is written for the case the user asked about: an agent noticing its owner has a website and walking them through registering it — explicitly NOT guessing a merchant_id or inventing a payout address, because the owner sets where the money lands. The payer skill now points at the merchant skill up front, because the platform is two-sided and a user with their own site should always be told they can earn, not only pay. Every gate/discovery API the merchant skill shows is verified present in the published @aifinpay/gate@0.3.0. Both skills are plain markdown with a name/description/when_to_use header, so they work as a Claude skill file, as context for any other agent, and as the text an llms.txt can carry — one document, three channels, any agent.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three things, so an agent on any platform can act on the skill without a human explaining it.
1. Stale economics — in a public file
The payer skill said "98.99 / 1 / 0.01". That is the v1.2 fee-on-top model. The canon is AIFP-1: the agent pays the quoted price, AiFinPay takes 100 bps from it, the merchant receives 99%, creator 0 — enforced on-chain by the v1.3/v1.4 splitter, verified on Polygon and Solana this session. A skill that misstates the fee quotes an agent the wrong number.
2. Secure wallet — not mentioned before
Recovery printed once in the terminal, never in chat; ephemeral agents never print their key;
AIFINPAY_WALLET_PASSPHRASEencrypts the keystore; one seed derives every chain. PlusdescribeQuote(what a payment buys, not a bare "1.06 POL") and the orderIdHash/nonce that stop a double-pay.3. The merchant skill — the missing entry point
The other side of a two-sided platform. Today an agent scrapes a site for free; this turns any site into one that charges agents per request, one middleware, owner keeps 99%.
Written for the exact case asked about: an agent noticing its owner has a website and walking them through registering it — explicitly not guessing a
merchant_idor inventing a payout address, because the owner sets where the money lands.The payer skill now points at the merchant skill up front — the platform is two-sided, and a user with their own site should always be told they can earn, not only pay.
Every gate/discovery API the merchant skill shows is **verified present in the published **. Both skills are plain markdown with a header, so they work as a Claude skill file, as context for any other agent, and as
llms.txttext — one document, three channels.