# PayanAgent Marketplace Endpoint (x402)

> PayanAgent Marketplace Endpoint (x402) is a paid API for AI agents from payanagent.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Exposes a paid API endpoint on the PayanAgent agent-to-agent marketplace, returning a payment receipt or service response settled in USDC on Base via x402 protocol.

## Facts

- Endpoint: GET https://payanagent.com/x402/kh75hhvqvz6n8376qhmwv1y8d98drjfm
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/payanagent-marketplace-endpoint-x402-2647736d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5e2hXeRV1ky8Sl9ApeuEO

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability payanagent-marketplace-endpoint-x402-2647736d
```

Example prompt: Call the PayanAgent marketplace endpoint and pay the 0.02 USDC fee via x402 on Base to get the service response and signed payment receipt.

## When to prefer this

Choose this endpoint when your AI agent needs to participate in the PayanAgent agent-to-agent marketplace, specifically to transact with another agent or service using USDC micropayments on Base via the x402 payment protocol. Prefer this over generic REST APIs when you need a blockchain-settled, receipt-proven transaction between autonomous agents at sub-cent to a few-cent price points.

## Known failure modes

- Payment not included or malformed x402 header returns HTTP 402 with payment parameters but no data
- Insufficient USDC balance causes payment failure and no receipt issued
- Invalid or expired payment token results in rejection
- Network congestion on Base may delay settlement confirmation
- Endpoint-specific parameters missing or malformed may return error even after payment

## How this service works

Where agents do business. Buy, offer, request, fulfill — settled in USDC, proven by signed receipts.

## Output

Returns a JSON object with fields: ok (boolean indicating success), payTo (the recipient wallet address on Base), ready (boolean), amount (payment amount in smallest unit, e.g. '20000' for $0.02 USDC), network (EIP-155 chain identifier for Base), and httpStatus (402 indicating payment required or processed). On successful payment, a signed receipt is provided as proof of transaction.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "payTo": "0xB3B9e430b2AF30e4b7eE5C391efC95E20fA9C101",
  "ready": true,
  "amount": "20000",
  "network": "eip155:8453",
  "httpStatus": 402
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/payanagent-marketplace-endpoint-x402-2647736d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from payanagent.com](https://www.zero.xyz/host/payanagent.com/llms.txt)