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

# Introduction

> Payzor is the payments layer for the agent economy. Let any AI agent pay you with budgets, policies, and receipts in minutes.

# Introduction

**Payzor is a payments network for AI agents.**

Today, software agents book flights, buy API credits, and hire other agents, but they pay like tourists: ad-hoc card flows built for humans, or nothing at all.

Payzor gives every agent something it has never had: **a wallet with rules**.

* Agents hold balances and spend them through APIs.
* Businesses accept payments *from agents* as naturally as from humans.
* Humans stay in control: every agent operates under spending policies, and anything unusual requires human approval.

```mermaid theme={null}
flowchart LR
    A[Your customer's agent] -->|1. pays| C[Charge / PayLink]
    C --> B[Your business]
    P[Policy Engine] -.->|guards every move| A
    W[Webhooks] -->|real-time events| B
```

## Who is this for?

<CardGroup cols={2}>
  <Card title="Businesses & SaaS" icon="store" href="/guides/accept-a-payment">
    Accept payments from autonomous agents. One API key, one endpoint, webhooks for everything.
  </Card>

  <Card title="Agent developers" icon="robot" href="/concepts/agents-and-wallets">
    Give your agent a wallet with hard limits and audit trails, so it can spend without supervision.
  </Card>
</CardGroup>

## The three primitives

Everything in Payzor is built on three ideas:

1. **Charges**: "I owe you \$2.00." A business creates a charge; an agent (or anyone) settles it.
2. **PayLinks**: "You may spend up to \$5.00 with me this month." A pre-authorized budget that a merchant can draw against, approved once by a human.
3. **Policy Engine**: "This agent may spend at most $50 per transaction, only on `data_apis` and `shop`, and above $100 a human must approve." Evaluated before *every* movement of money.

## What makes it different

<AccordionGroup>
  <Accordion title="Agents are first-class citizens, not browser sessions">
    Every payment is authenticated with an agent API key (`pz_sk_...`) and evaluated against that agent's policy. No cards, no redirects, no humans typing OTP codes.
  </Accordion>

  <Accordion title="Humans approve, machines execute">
    Hard limits block bad transactions outright. Suspicious ones pause and notify a human via webhook and notification channels; the money does not move until someone says yes.
  </Accordion>

  <Accordion title="Every fact is auditable">
    Each event is written to an append-only chain with a sequence number and hash. Export it as CSV with `GET /export/transactions.csv`.
  </Accordion>

  <Accordion title="Native HTTP 402 payments (x402)">
    Resources can cost money on-chain in USDC. Request without paying → `402 Payment Required` with exact terms; retry with an `X-PAYMENT` header → verified and settled. See [x402 Payments](/concepts/x402).
  </Accordion>
</AccordionGroup>

## Next steps

<Steps>
  <Step title="Run the quickstart">
    Create your first charge and get paid by an agent in \~10 minutes → [Quickstart](/quickstart).
  </Step>

  <Step title="Learn the auth model">
    Three credentials, three levels of power → [Authentication](/authentication).
  </Step>

  <Step title="Go deeper">
    Understand [charges](/concepts/charges), [PayLinks](/concepts/paylinks), and [webhooks](/guides/webhooks) before going to production.
  </Step>
</Steps>