Run supplied-data checks locally for free or use provider-processed USDC payments for hosted jobs. Annual subscriptions include 3,000 completed jobs per subscription month. Local execution needs no account or network.
Try one hosted batch for 0.005 USDC.
Audit up to 50 supplier records, reconcile two snapshots, or check invoice arithmetic. Hosted execution gives your agent a result, payment receipt and 24-hour recovery without deploying the engine.
Buy directly from TaskMint using this client; no marketplace router is required. Agent402 currently lists TaskMint for discovery while its paid execution router requires additional settlement history.
These commands request a quote without signing or paying. For a purchase, the client requires your existing approved wallet authorizer and an explicit spending cap. It saves the original job and blocks a second signing attempt; recover an uncertain result with the same job file.
import {payWithSigner} from './taskmint-hosted-client.mjs';
const result = await payWithSigner('job.json', {
signer: yourExistingApprovedSigner,
maxMicrousd: 5000 // 0.005 USDC maximum
});
The optional adapter accepts an existing signer with an address and signTypedData method. It needs no x402 SDK setup and never loads wallet keys. This release supports externally owned wallets; smart wallets are not supported. The check command verifies service configuration, not wallet funds or payment authorization.
Inspect the same engine locally for free.
Start with a local call. An agent supplies structured input and reads a deterministic result; its developer or operator sets the permitted workflow and payment budget.
Save both files in one folder, inspect them, then run with Node 22+:
These examples use synthetic data, run locally and make no payment or network requests.
Test before the next write.
The open Dirty Data Challenge gives your agent three synthetic fixtures and nine inspectable assertions. Run the reference engine or compare your own implementation, then keep the regression pack.
POST to /api/agent/SERVICE_ID using the service’s input schema and a new private request token. A compatible x402 v2 client can authorize the exact price and retry that same URL and body. Agent API contract.
Generate the token with a cryptographically secure random generator, replace the placeholder, and keep it private: it is the credential for this result. Save the exact body before sending. HTTP 402 supplies PAYMENT-REQUIRED; retry with the customer’s PAYMENT-SIGNATURE. The server accepts exact EIP-3009 native USDC payments on Base from externally owned wallets. Set a maximum permitted price in your agent before enabling signing.
HTTP 200 returns a paid or free result. HTTP 202 means settlement is uncertain: retry the identical body without a signature to recover. Keep the same token through timeouts, errors and restarts; changing input with that token is rejected. Never buy again to resolve an uncertain payment. Results expire after 24 hours. GET provides a discovery challenge without creating an order or taking payment.
The official x402 fetch client is covered by local integration tests. Live unsigned API access was verified on 25 September 2026. TaskMint is listed on x402scan; a real customer purchase is not yet confirmed. Static discovery metadata uses synthetic examples and never includes your actual input or private token.
The existing quote–pay–recover API remains available, including annual subscriptions:
POST your service and payload to /api/checkout/quote. For annual access, post {"plan":"builder_annual"} instead.
Keep the returned order ID and private receipt token. Review the price, recipient, network and expiry. The initial response does not take payment.
POST an empty JSON object to /api/checkout/pay?id=ORDER_ID, with Authorization: Bearer RECEIPT_TOKEN. HTTP 402 supplies x402 v2 requirements in PAYMENT-REQUIRED.
Have the customer authorize the exact payment in their own compatible wallet. Retry that same POST with its base64 x402 v2 PAYMENT-SIGNATURE. The current release supports EIP-3009 signatures from externally owned wallets, native USDC on Base, and the exact scheme only.
HTTP 202 means the payment outcome is still being checked. GET /api/checkout/order?id=ORDER_ID with the same receipt token. Recovery is read-only; never create another payment to fix an uncertain one.
HTTP 200 returns the result after matching a successful transfer and two block confirmations. The receipt token grants access to the order; it must be treated as a credential. It is not a wallet key. No sign-in or independent platform API key is required for public checkout.
Use an annual subscription
After the annual payment is confirmed, reuse its receipt ID and token for:
One completed operation uses one job, including a completed diagnostic that finds invalid data. Unresolved operations use none. Retry the exact input with the same request key to recover its result without using another job. The response includes your remaining allowance and reset date. Monthly jobs do not roll over. The plan has no automatic renewal or paid overage.
Result access expires after 24 hours. Request bodies are limited to 48 KB, with stricter service-specific limits. Included execution is limited to 60 requests per minute and 2,000 per day per subscription; monthly allowance is 3,000 completed jobs. Public purchase admission is bounded separately during launch. An HTTP 429 does not charge an overage.
TaskMint does not browse, infer missing facts, use a language model, schedule external workflows or change another system. There is no hosted MCP service, team workspace or custom connector in this release. The separate authenticated /api/v1 ledger uses test credits; its receipts are not sales.
Regression checks are developer-authored and do not establish market demand, independent accuracy or guaranteed uptime. See the release evidence for what was tested and which live payment steps remain unverified.