# x402-api [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/gigsoul/x402  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/x402-api-2

## Description
AI API for marketing, content and outreach. 22 endpoints. Pay with USDC on Base via x402.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "x402-api": {
    "command": "uvx",
    "args": ["x402"]
  }
}
```

## Documentation

## What x402-api does

The x402-api MCP server is associated with x402, an open standard for internet-native payments over HTTP. The protocol connects three roles: a client requesting a resource, a resource server providing an API or other HTTP resource, and a facilitator that can verify and settle payments for supported networks and schemes.

Rather than defining one currency or blockchain, x402 describes payment requirements and payloads that can be implemented across networks. Its stated scope includes crypto and fiat networks, stablecoins, tokens, and other forms of value, subject to the available scheme and network implementations. The material specifically describes an `exact` scheme for transferring a specified amount.

## How it works

A client first requests a protected resource. The resource server can respond with HTTP status `402 Payment Required` and provide a base64-encoded `PaymentRequired` object in the `PAYMENT-REQUIRED` header. The client selects an accepted payment requirement and creates a `PaymentPayload` for its scheme and network.

The client then repeats the request with the payload in the `PAYMENT-SIGNATURE` header. The resource server verifies the payload locally or sends it to a facilitator's `/verify` endpoint. If verification succeeds, the server fulfills the request. Settlement can occur directly on a blockchain or through a facilitator's `/settle` endpoint. After successful execution, the resource server returns the requested content and may include a base64-encoded settlement response in the `PAYMENT-RESPONSE` header.

The x402-api MCP server therefore fits workflows where payment is part of the normal request and response exchange. The protocol also allows servers flexibility around when verification and settlement occur, trading response speed against payment guarantees.

## Setup and configuration

The repository provides reference packages rather than MCP-client setup instructions. TypeScript users can install the core, EVM, SVM, and fetch packages for a minimal client, or use the Express package for a minimal server. Additional TypeScript packages cover Axios, Hono, Next.js, a paywall, and extensions. Python installation uses the `x402` package, while Go projects can import the repository's Go module.

Those details should be confirmed from the repository's implementation and examples before deployment.

## Tools and capabilities

The documented capabilities are protocol-level:

- Declare accepted payment requirements for HTTP routes.
- Return payment-required responses using HTTP semantics.
- Create client payment payloads for supported scheme and network pairs.
- Verify payloads locally or through a facilitator.
- Settle payments locally or through a facilitator.
- Extend implementations to additional schemes and networks.

## Limitations and notes

Support is not automatic for every network and scheme. Clients and facilitators must explicitly support the selected pair, and scheme behavior can vary by blockchain. The documentation describes `exact` as the first shipping scheme and mentions `upto` as a theoretical example, so the availability of other schemes should not be assumed.

It also does not establish that the marketing, content, and outreach endpoints mentioned in the listing are implemented. Use the repository's specifications and examples to validate those capabilities before relying on them.

_Full upstream README: https://allmcps.com/mcp/x402-api-2/readme_