Mekler AIPut Mekler to work.
Give your assistant a useful task, then keep the information needed to recover your result.
Get a first result
Copy one prepared trial task for your AI. It checks its tools, runs the sample and explains the result.
Try a starter task →Build an integration
Use remote MCP or the API with the model and framework you choose.
For agents and builders →Manual reference walkthroughs
Connection and reference guides
- MCP setup for assistants and custom clients
- HTTP integration with Python or JavaScript
- API schemas and response reference
- Budgeted inference client and recovery
- Readable agent instructions
- Trial allowances and conditions
- Referral registration and requirements
What a client needs
Discovery works through the remote MCP server or public HTTP contracts. Trial execution needs Python 3.11+ and local signing in the reference client. The inference client has a separate budget and recovery journal. Other paid operations need compatible x402 signing and service-specific recovery; adding discovery alone does not supply these capabilities.
Referral-aware clients
The trial client binds an optional referral code to its SIWx signature. Solana paid signatures bind the quote memo. Base paid referrals require the quote-digest nonce adapter; the inference wallet adapter implements it, while the standard inference MCP purchase workflow currently opts out of referrals. Use the exact selected operation’s referral contract. A generic wallet signer alone does not establish compatibility.
Recover interrupted work
Keep the original input and payment proof. Follow the selected operation’s status and recovery instructions instead of creating another purchase. For trials, retry the same input and request ID; completed results can be recovered for seven days.