# NFT Invoice Minter MCP

> NFT Invoice Minter MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.5/call, status unknown (last checked 2026-10-13).

Mints NFT-based invoices on-chain by processing invoice data and converting it into a non-fungible token record.

## Facts

- Endpoint: POST https://api.m2mcent.com/nft-invoice-minter-mcp/api/process?utm_source=zero.xyz
- Price: $0.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nft-invoice-minter-mcp-d14280c6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__qHY_OoNHDLwUKL2d36kc

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 nft-invoice-minter-mcp-d14280c6 -d '<json body>'
```

Example prompt: Mint an NFT invoice for a $1,500 web design project completed for Acme Corp — include the client name, amount, and project description in the invoice data so it gets recorded on-chain as a non-fungible token.

## When to prefer this

Choose this endpoint when you need to permanently record an invoice as an NFT on a blockchain, providing immutable, verifiable, and transferable proof of a billing event — especially useful for crypto-native freelancers, Web3 businesses, or any party needing tamper-proof on-chain invoice records.

## Known failure modes

- Invalid or malformed data string causes processing failure
- Empty data field results in rejection
- Network or blockchain congestion may cause delayed minting
- Insufficient payment (0.5 USDC not provided) leads to 402 error
- Data string exceeding size limits may be rejected

## How this service works

The premier global index of 1,069 monetized MCP nodes across 205 specialized subdomains. Gasless USDC runtime settlements via x402 V2 Spec on Base L2. Save 95% token context.

## Output

The endpoint returns a result confirming the NFT invoice has been minted, likely including a transaction hash, token ID, and on-chain reference for the newly created invoice NFT.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nft-invoice-minter-mcp-d14280c6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.m2mcent.com](https://www.zero.xyz/host/api.m2mcent.com/llms.txt)