aipaysdk / agents
AGENTS.md2 starsChanged 4 months agoMITView on GitHub
Use the installed agentpay-sdk skill whenever the task touches Link fiat setup, wallet setup, funding, policy, transfers, approvals, cards, or backups. Rules that must stay consistent:
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- skills/agentpay-sdk/agents/CLAUDE.mdCLAUDE.md
- skills/agentpay-sdk/agents/copilot-instructions.mdCopilot instructions
- add-pluginSkill
- agentpay-sdkSkill
The file
Show its rules and text
We split this AGENTS.md into the rules it gives an agent
15 rules. About 1 is common, 2 are distinctive, and 12 are very specific to this project.
≈1
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Use the installed agentpay-sdk skill whenever the task touches Link fiat setup, wallet setup, funding, policy, transfers, approvals, cards, …
- Very specific: line 10
create one-time card credentials with agentpay link card --payment-method-id <id> --merchant-name <name> --merchant-url <url> --amount …
- Very specific: line 12
use agentpay wallet --json to decide whether a reusable wallet already exists
- Very specific: line 13
if the user only asks what the skill can do, answer from SKILL.md and do not probe the machine first
- Very specific: line 14
never ask the user to paste VAULT_PASSWORD into chat
- Common: line 15
never ask the user to paste Link card numbers, CVCs, access tokens, refresh tokens, or full credential files into chat
- Very specific: line 16
if wallet metadata is unavailable on macOS/Linux, tell them to run agentpay admin setup locally.
- Very specific: line 17
if the wallet exists and the user wants to preserve it while re-running setup, tell them to run agentpay admin setup …
- Very specific: line 18
after a fresh setup, tell the user to create an encrypted offline backup with agentpay admin wallet-backup export --output <PATH> unless …
- Very specific: line 19
if the local wallet is gone but the user has an encrypted backup, tell them to run agentpay admin setup --restore-wallet-from <PATH> locally
- Very specific: line 20
if the user does not specify network or asset for a payment, default to USD1 on bsc (on aipay:local, prefer the active chain)
- Distinctive: line 21
check funding before outbound actions
- Distinctive: line 22
if funding is missing, stop and ask the user to fund the wallet with the exact address, network, token needs, and BNB gas needs
- Very specific: line 24
use agentpay --help / pnpm aipay:local --help as the source of truth for exact flags
- Very specific: line 25
use agentpay admin tui as the default path for daemon policy.
≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AiPay SDK Adapter
Use the installed agentpay-sdk skill whenever the task touches Link fiat setup, wallet setup, funding, policy, transfers, approvals, cards, or backups.
Rules that must stay consistent:
- start from
agentpay config show --json - for fiat/card payments, start with
agentpay link status --json; if Link is not authenticated, useagentpay link onboard - list Link payment methods with
agentpay link payment-methods --json - create one-time card credentials with
agentpay link card --payment-method-id <id> --merchant-name <name> --merchant-url <url> --amount <cents> --context <100+ char explanation> --output-file <PATH>and never print full card details into chat - for third-party program integration, use
@aipaysdk/sdk/linkhelpers through the AiPay Link facade - use
agentpay wallet --jsonto decide whether a reusable wallet already exists - if the user only asks what the skill can do, answer from
SKILL.mdand do not probe the machine first - never ask the user to paste
VAULT_PASSWORDinto chat - never ask the user to paste Link card numbers, CVCs, access tokens, refresh tokens, or full credential files into chat
- if wallet metadata is unavailable on macOS/Linux, tell them to run
agentpay admin setuplocally; on Windows / monorepo usepnpm aipay:local setup(dashboard optional) - if the wallet exists and the user wants to preserve it while re-running setup, tell them to run
agentpay admin setup --reuse-existing-walletlocally - after a fresh setup, tell the user to create an encrypted offline backup with
agentpay admin wallet-backup export --output <PATH>unless they already have a verified backup - if the local wallet is gone but the user has an encrypted backup, tell them to run
agentpay admin setup --restore-wallet-from <PATH>locally - if the user does not specify network or asset for a payment, default to
USD1onbsc(onaipay:local, prefer the active chain) - check funding before outbound actions
- if funding is missing, stop and ask the user to fund the wallet with the exact address, network, token needs, and BNB gas needs
- if a request hits manual approval, say it is waiting for the user's approval and use local admin CLI approval commands first; for
transfer --broadcast,transfer-native --broadcast,approve --broadcast, andbitrefill buy --broadcast, tell them to keep the original command running and not rerun it after approval; if that original broadcast command is already gone after approval, useagentpay admin resume-manual-approval-request --approval-request-id <UUID> - use
agentpay --help/pnpm aipay:local --helpas the source of truth for exact flags - use
agentpay admin tuias the default path for daemon policy; onaipay:localusepnpm aipay:local rules
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

