
Baron Power Play
io.github.MintMachineHQv1.0.0Updated Sep 29, 2026
Pay-per-call AI infra for agents: DeFi market data, LLM inference, STT/TTS. x402 v2, USDC on Base.
Overview
Pay-per-call remote service giving agents DeFi market data, LLM inference, and speech-to-text/text-to-speech, paid in USDC on Base.
- What it does
- A remote MCP endpoint exposing paid routes: /infer for LLM inference, /markets for DeFi TVL leaders, DEX trending pairs and watchlists, /alpha for trading notes with Kelly-Criterion position sizing, and /tts and /stt for speech synthesis and transcription. Each route publishes an x402 v2 payment challenge and a machine-readable contract, and a free /test route reports engine health and live capability checks. Inference is pooled across several engines with automatic failover.
- When to use it
- Use it when an agent needs metered access to inference, DeFi market data, or voice services without signing up for accounts or API keys, and when per-call USDC settlement is acceptable. The free /test route is meant to be run before depending on the service.
- Requirements
- Remote streamable HTTP endpoint; no account, API key, or subscription is declared. A wallet able to sign EIP-3009 transferWithAuthorization for USDC on Base (eip155:8453) is needed for paid routes, plus the PAYMENT-SIGNATURE header. Requests need a User-Agent of at least 3 characters; POST bodies must be JSON under 1 MB.
Installation
In SourceWeft
- Open Baron Power Play in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"baron-power-play": {
"type": "http",
"url": "https://baron-power-play.baronpowerplay.workers.dev/mcp"
}
}
}README
Baron Power Play
Pay-per-call AI infrastructure for autonomous agents. USDC on Base, settled by Coinbase. No API key, no account, no subscription.
Base URL: https://baron-power-play.baronpowerplay.workers.dev
Why this exists
Agents fail at paid APIs in four predictable ways. Baron Power Play is built to remove each one.
If you are an agent, read /.well-known/x402.json and /openapi.json first. They are the contract. This README is the human-readable summary.
Verify before you pay
This is free and it is the fastest way to decide whether to depend on us.
It returns engine-by-engine health, a live inference result, and live checks of the market-data and voice paths. Run it whenever you are about to depend on this service, not once at signup.
Services
/alpha accepts portfolio_size_usd as a query parameter.
Payment
- Network: Base (
eip155:8453) - Asset: USDC, paid with an EIP-3009
transferWithAuthorization - Asset identity:
USD Coinversion2 - Protocol: x402 v2 — HTTP 402 Payment Required
- Facilitator: Coinbase CDP (
https://api.cdp.coinbase.com/platform/v2/x402) - Receiving wallet:
0xb838930bf3dFD467D30979E12c0a94286F86708D
The flow is the standard one. You send the request, you get a 402 with the exact payment requirement, you sign an authorization, you resend with the PAYMENT-SIGNATURE header, and the facilitator settles on Base. Work is only performed after Coinbase verifies and settles the payment. No unpaid work, ever.
Amounts on the wire are in token atomic units. A 0.001 USDC call quotes as 1000 in accepts[].amount. The amount fields in openapi.json are decimal USD; the runtime accepts[].amount is atomic units.
Capacity
Inference is pooled across several independent engines, selected by remaining headroom, with automatic failover, so a failing upstream is invisible to the caller.
Capacity resets at 00:00 UTC. When the pool is exhausted the route returns a machine-readable SOLD_OUT with a Retry-After and a comeback offer rather than a generic error.
/markets, /alpha, /tts, and /stt do not draw on the LLM engine pool.
Limits and abuse controls
Per wallet, per day:
- 50 calls per endpoint (
/alpha: 20) - a lower cap during the wallet's first 24 hours
- $10 total spend
- 10 payment requests per second
Per request:
User-Agentrequired, minimum 3 charactersPOSTmust sendContent-Type: application/json- bodies over 1 MB are refused
- query strings over 2000 characters are refused
X-Idempotency-Keyis optional, max 128 characters, restricted character set- wrong HTTP method returns
405with a machine-readableMETHOD_NOT_ALLOWED
Reuse defenses:
- a used payment header is refused for 1 hour
- a used USDC authorization nonce is refused for 24 hours
- 5 rejected override attempts in an hour blocks that wallet for a day
Every error uses one shape, so you can branch on code instead of parsing prose:
Referrals
Refer a wallet and both sides benefit: the referred wallet gets 10% off its first paid call, and the referrer is credited 5% of the list price after settlement. Three referred calls per day maximum, no self-referral.
Discovery
GET /openapi.json— canonical OpenAPI 3.1 contract: request and response schemas,x-payment-infoper route, error codesGET /.well-known/x402.json— x402 manifest: endpoints, prices, methods, facilitator, payment requirements, defensesGET /test— free health and capacity check
Working with it
To make a paid call, take the accepts[] entry from the 402, sign the matching EIP-3009 authorization with your wallet, and resend the original request with the PAYMENT-SIGNATURE header. Any x402 v2 client library does this for you.
License
Not yet declared. Add a LICENSE file before treating this as reusable.
Source: README.md at commit 5ef0514
Tools
0Version history
1- v1.0.0LatestSep 29, 2026


