Mazza Group AI APIs

mazzagrp-mcp

23 AI APIs from mazzagrp.com behind one MCP endpoint. Agents pay per call with x402 v2 / USDC on Base mainnet — no API keys, no signup, no subscription.

• Registry name: com.mazzagrp/mcp
• Remote endpoint: https://mazzagrp.com/mcp (streamable HTTP)
• Discovery: /.well-known/x402.json · /.well-known/mcp/server-card.json · agents.md

Use the remote server (recommended)

Nothing to install. Point your client at the URL:

{
  "mcpServers": {
    "mazzagrp": {
      "type": "http",
      "url": "https://mazzagrp.com/mcp"
    }
  }
}

Claude Code: claude mcp add --transport http mazzagrp https://mazzagrp.com/mcp Cursor / Grok / any client that takes a URL: paste https://mazzagrp.com/mcp.

Payments are signed by the client's own wallet (the x402 flow returns a 402 with the requirements; your client settles in USDC on Base). The remote server never holds your key.

Use the stdio package (legacy, local wallet)

pip install mazzagrp-mcp

{
  "mcpServers": {
    "mazzagrp": {
      "command": "mazzagrp-mcp",
      "env": { "MAZZAGRP_WALLET_KEY": "0xYOUR_PRIVATE_KEY" }
    }
  }
}

Or with a wallet file: MAZZAGRP_WALLET_PATH=/path/to/wallet.json ({"private_key": "0x...", "address": "0x..."}).

Nota: il pacchetto stdio espone 21 tool con i nomi storici (recall, rag, sql, …). Il server remoto — quello a cui punta il registry — ne espone 23 con nomi più espliciti (knowledge_recall, rag_query, text_to_sql, …). Le API sottostanti sono le stesse. Per i client nuovi usa il remoto.

Endpoints and prices

API path	Price (USDC)	What it does
/api/ping	0.01	AI ping — one-sentence answer, validates the payment flow end to end
/api/character	0.10	Character development
/api/recall	0.20	Memory recall / context retrieval
/api/storyforge	0.60	Creative storytelling
/api/design	0.80	Design recommendations
/api/temporal	0.80	Temporal.io workflow design
/api/puzzles	0.80	Puzzle and riddle generation
/api/chatbot	1.00	Conversational AI
/api/longqa	1.00	Long-form Q&A
/api/sheets	1.00	Spreadsheet formulas and analysis
/api/sql	1.20	SQL generation and optimisation
/api/arena	1.20	LLM benchmarking / comparison
/api/autoflow	1.50	Workflow orchestration
/api/rag	1.50	Retrieval-augmented generation
/api/negotiator	1.50	Negotiation strategy
/api/desktop	1.50	Desktop app development guidance
/api/webagent	1.80	Autonomous web agent
/api/simulation	2.00	Scenario simulation
/api/worldbuilder	2.00	Worldbuilding for fiction and games
/api/mcp-eval	2.00	MCP implementation assessment
/api/event-ops	2.50	Event operations (catering, corporate, hospitality)
/api/consultation	5.00	Senior AI strategy consultation
/api/automation	15.00	Full automation workflow design

Source of truth: /.well-known/x402.json (23 endpoints, generated from the API's own endpoint table).

How payment works

1. The agent calls a tool.
2. The API replies HTTP 402 with the x402 v2 requirements (accepts[0].amount, network eip155:8453).
3. The client signs an EIP-712 authorisation with its own wallet.
4. It retries with the PAYMENT-SIGNATURE header.
5. The response comes back — the USDC settlement happens on Base.

• Network: Base mainnet (eip155:8453)
• Asset: USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
• Treasury: 0xD98b6969fab0bA4D4BB086fF273ff7CCD284CEe8

⚠️ Le versioni precedenti di questo README dicevano "Base Sepolia (testnet)". Era sbagliato: il servizio è su Base mainnet. Un wallet finanziato su Sepolia non paga nulla.

Free demo

demo_free returns one real LLM answer without payment, so an agent can verify the whole flow before funding a wallet.

License

MIT