# TIBBIR402 Token Minter

> TIBBIR402 Token Minter is a paid API for AI agents from www.tibbirx402.fun, paid per call via x402, $1/call, status unknown (last checked 2026-10-12).

Mints 1.5 million TIBBIR402 tokens to a recipient wallet address on the Base blockchain for $1 USDC

## Facts

- Endpoint: POST https://www.tibbirx402.fun/api/mint?utm_source=zero.xyz
- Price: $1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tibbir402-token-minter-5ca2b7d1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZjcUvUkdKSVPGfK1CI18D

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 tibbir402-token-minter-5ca2b7d1 -d '<json body>'
```

Example prompt: Mint me 1.5 million TIBBIR402 rebel tokens — I'll pay the $1 USDC fee and want them sent to my wallet 0xYourWalletAddress on Base.

## When to prefer this

Use this endpoint when an agent or user specifically wants to acquire TIBBIR402 ('The Future Belongs to Rebels') tokens on the Base blockchain at the fixed price of $1 USDC for 1.5M tokens. Ideal for agents automating token acquisition workflows on Base using the x402 micropayment protocol.

## Known failure modes

- Insufficient USDC payment — payment of exactly $1 USDC not received, mint rejected
- Invalid recipient wallet address — malformed or missing Ethereum address causes failure
- Contract error — on-chain mint transaction reverts due to supply cap or contract pause
- Network congestion — Base network delays cause transaction timeout
- Payment protocol failure — x402 payment header missing or malformed

## How this service works

Mint 1.5M tokens for $1 USDC

## Output

Returns a JSON object with success boolean, the minted amount (1.5M tokens with 18 decimals), the recipient wallet address, the Base blockchain transaction hash, the block number where the mint occurred, and a status message confirming the operation.

## Example request

```json
{
 "amount": 1500000,
 "blockchain": "Base",
 "paymentAmount": 1,
 "paymentCurrency": "USDC",
 "recipientAddress": "0x1234567890123456789012345678901234567890"
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "amount": {
   "type": "string",
   "description": "1500000 tokens (1.5M with 18 decimals)"
  },
  "txHash": {
   "type": "string",
   "description": "Transaction hash on Base"
  },
  "message": {
   "type": "string",
   "description": "Status message"
  },
  "success": {
   "type": "boolean",
   "description": "Mint operation status"
  },
  "recipient": {
   "type": "string",
   "description": "Recipient wallet address"
  },
  "blockNumber": {
   "type": "string",
   "description": "Block number where mint occurred"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tibbir402-token-minter-5ca2b7d1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.tibbirx402.fun](https://www.zero.xyz/host/www.tibbirx402.fun/llms.txt)