> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aifinpay.io/llms.txt
> Use this file to discover all available pages before exploring further.

# AiFinPay — Payment Infrastructure for AI Agents

> Public skills, agent tooling and merchant payment gates for paid access over HTTP.

**AiFinPay is payment infrastructure for AI agents.** A merchant can publish
paid resources through an HTTP 402 gate. An agent discovers the terms and,
when its client supports the offered settlement route, buys access and reuses
a scoped payment receipt.

<CardGroup cols={2}>
  <Card title="I own an agent" icon="wallet" href="/skills">
    Install the payer skill, connect your tools and inspect a site's paid routes.
  </Card>

  <Card title="I own a site or API" icon="store" href="/skills">
    Use the merchant skill to integrate the gate and publish your API catalog.
  </Card>
</CardGroup>

## Start with the skill

```bash theme={null}
npx skills add AiFinPay/skill
```

Choose `aifinpay` for the paying side or `aifinpay-merchant` for the merchant
side. Skills provide instructions; MCP and SDK packages provide tools.
Read [the skill setup guide](/skills) and [quickstart](/quickstart).

<Note>
  MCP `@aifinpay/mcp` 2.2.x pays with `payable_fetch` once the owner enables it,
  and Node `@aifinpay/agent` 2.1.x pays with `fetchPaid`. Both settle AIFP-1 on
  Polygon (splitter v1.4) in native POL; the smallest batch is \$0.10 plus gas. The
  Python SDK does not pay yet. A quote or invoice alone does not move funds.
  See [current payment support](/pay/paywalled-sites).
</Note>

## How the gate works

The agent discovers paid routes on the merchant's own origin, requests a
resource, and receives HTTP 402 with payment terms. A supported executor
settles an approved batch from the agent's wallet. After verification, the
agent receives a receipt and retries with `AIFP-Receipt` to get the data.
Further covered calls spend quota from that receipt. See [the flow](/pay/manual-flow).

## The dashboard

Everything above can be driven from code alone, but the running product has a
control panel: **[dash.aifinpay.io](https://dash.aifinpay.io)**.

It is where you register a site, price its endpoints, watch which agents paid
for what, set a payout wallet, and configure webhooks. Resource registration through `ensureResources()` and the dashboard uses
the same registry. A self-hosted discovery array is separate: publish and
update it in the partner app, as described in [discovery](/ai-discovery).

<CardGroup cols={2}>
  <Card title="Set up your site" icon="gauge" href="/charge/dashboard">
    Endpoints, pricing tiers, payout wallet, and the paywall builder.
  </Card>

  <Card title="Connect your gateway" icon="server" href="/charge/gateway">
    Point your domain at AiFinPay, or verify receipts in your own backend.
  </Card>
</CardGroup>

## The dashboard

Everything above can be driven from code alone, but the running product has a
control panel: **[dash.aifinpay.io](https://dash.aifinpay.io)**.

It is where you register a site, price its endpoints, watch which agents paid
for what, set a payout wallet, and configure webhooks. Whatever you declare in
code with `ensureResources()` shows up there, and whatever you draw there is
picked up by the gate within about a minute — the two surfaces edit the same
registry, so you can start in either one.

<CardGroup cols={2}>
  <Card title="Set up your site" icon="gauge" href="/charge/dashboard">
    Endpoints, pricing tiers, payout wallet, and the paywall builder.
  </Card>

  <Card title="Connect your gateway" icon="server" href="/charge/gateway">
    Point your domain at AiFinPay, or verify receipts in your own backend.
  </Card>
</CardGroup>

## SDKs and tooling

| Package | Purpose |
| - | - |
| `@aifinpay/skill` | Payer and merchant instructions for assistants |
| `@aifinpay/mcp` | Wallet, history, quota and non-signing preparation tools |
| `@aifinpay/agent` | Node/TypeScript SDK; settlement depends on supported deployment |
| `aifinpay-agent` | Python SDK; consult the installed version's supported routes |
| `@aifinpay/gate` | Merchant-side receipt verification and quota metering |

[Publish discovery](/ai-discovery) so agents can learn your site's routes,
prices and parameters without guessing.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.