Understand the project
Practical overview
When it fits
Use MPP32 when an agent must call paid services and the builder wants a shared discovery and payment layer instead of separate provider accounts and custom 402 handling for each service.
Who it is for
- Developers building AI agents with paid API access
- Teams operating machine-payable or x402-enabled services
- Builders needing scoped payment delegation between agents
Documented uses
- Find paid and free machine-payable APIs through a federated catalog
- Pay x402 endpoints from an agent on Solana or Base
- Add payment-aware API access through an SDK or MCP server
- Control delegated sub-agent spending with scopes, caps and revocation
Before you choose
Requirements & limits
The repository describes 10 free Intelligence Oracle calls per day with an MPP32 agent key and no wallet or USDC setup for those calls. It also describes paid settlement in USDC on Solana and Base. The project is public and MIT-licensed.
- The repository is TypeScript-based and includes a client SDK, npm MCP server, backend and React/Vite webapp.
- x402 payment is documented as production on Solana mainnet and Base, with USDC settlement.
- The backend uses Hono on Bun, Prisma and SQLite; hosted deployment adds operational infrastructure that is not part of the source.
- Delegated Spend Keys provide service allowlists, budgets, hourly limits, per-call ceilings, rolled-up parent accounting and cascading revocation.
- Tempo is listed as production with pathUSD, while AGTP is described as a production identity layer and AP2 as wired but disabled in production.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Evidence and transparency
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 2 October 2026
- Original website title
- MPP32/MPP32 · Official homepage title · retained in its source language