Skip to main content
An AiFinPay skill teaches your assistant how to use the product. Choose the paying side if you own an agent, or the merchant side if you own a site or API. The skills are published in @aifinpay/skill and the AiFinPay/skill repository.

​
Install in your assistant

Select aifinpay for an agent buying access, or aifinpay-merchant for a merchant integrating payments. The installer lets you choose the agent client. Installing @aifinpay/skill with npm downloads the files; it does not by itself register the skill with your assistant. If your client accepts a Markdown instruction URL, use:
A skill is instructions, not a payment executor. Payments are executed by MCP payable_fetch (2.2.x, once the owner enables it) or Node fetchPaid (2.1.x). A skill copy older than 2.1.0 that calls MCP “read-only” or payments “release pending” is out of date — update it. See the MCP tool reference.

​
I own an agent

  1. Install the aifinpay skill.
  2. Connect the MCP server, or use the SDK from your own agent code.
  3. Create or select a persistent wallet with npx @aifinpay/mcp init.
  4. Ask the agent to inspect the target site’s discovery document and API catalog.
  5. Agree on the resource, scope, batch price and separate gas budget. Confirm that the installed executor supports the quoted deployment before funding or requesting a payment.
A useful first prompt:
Use the AiFinPay skill to inspect this website’s paid API. Read discovery on the same origin, list suitable routes and their parameters, and explain the batch price and receipt scope. Check whether your installed tools can execute the offered route before proposing a payment.
For example, on dev.ratersapp.com, read /.well-known/x402.json and /api/agent. The first lists paid routes; the second describes their request parameters. Use the dev origin throughout. A published catalog alone does not mean the installed client can settle it.

​
I own a website or API

Use aifinpay-merchant, register the site in the dashboard, and integrate @aifinpay/gate following the self-hosted integration guide. Publish the paid route catalog and link it from the site. See agent discovery for ownership, storage and deployment details.

​
Where the instructions live

The public skills live in AiFinPay/skill, under agent/skills/aifinpay/SKILL.md and agent/skills/aifinpay-merchant/SKILL.md. The skill installer saves a copy for the selected client. Update that copy when upgrading; it is not a live subscription to the source file. The MCP server also exposes a bundled skill as the resource aifinpay://skill. That copy belongs to the installed MCP version. A website’s paid routes live in its own discovery document, separately from these general AiFinPay instructions.