Equip an autonomous agent fleet with prepaid API credits.

Match your workload to the right package before paying

Choose the real API tool, planned calls and approved buyer budget. This no-charge quote picks only a pack that can cover your workload. No invoice is created.

Compare production-sized examples: 1,000 funding batch calls · 2,000 calls · 5,000 calls. Estimates depend on current tool credit costs, not a guaranteed number of future calls.

Test payment delivery first: the $0.49 Agent Micro Pack offers 50 ordinary API credits to validate the one-time wallet invoice, confirmation and API-key flow. It does not cover premium $149.90 or $999.90 analyses and is not a mandatory deposit.

Which enterprise problem is this designed to solve?

These are tested analysis capabilities, not customer testimonials. The paid analysis works on the buyer's submitted data; no real-world funds are transferred or independently verified by the report.

Autonomous buyer, no wallet authorization yet? Validate a $250 one-workspace budget for free or Validate a $1,100 cross-workspace budget for free. These are sample permitted budget ceilings, not a claim that any customer has approved them. For agent-native discovery use MCP qualify_premium_buyer. No money is moved.

Not the right fit? For one payment, use inexpensive x402 payment preflight; for a few ordinary API calls, use pay-per-call. A premium package is useful only when its exact, supported workload warrants the upfront cost. Check the free quote before authorizing a wallet.

Price your complete workflow

Combine the tools your agents actually need. The quote compares every available one-time package with paying per call, using one API key and your total spending cap.

Published example workload, not customer orders. Unused credits have no assumed value; gas and payment fees are excluded.

Check your premium analysis input before paying

Validate your own seller, ledger and mission snapshot. Receive its input hash, supported volume, exact price and included deliverables. This free check does not return the paid findings. The initial input below is a published sample.

For Control Tower, use {"workspaces":[...]} as documented in OpenAPI. Submit snapshots without credentials or personal information. Valid input does not confirm receipts on chain or guarantee a ready decision.

Create your one-time Base USDC invoice

Select a package and the public Base address that will pay. The invoice shows the exact USDC amount and recipient; your own wallet authorizes the transfer separately. Credits activate after two confirmations.

Connect the activated API key · Download the prepaid client · Verify the complete wallet catalog

Exactly when each package earns its price

These figures use the current paid API prices and exact credit costs. The break-even column is the minimum completed calls needed to match the package price. A pack saves money only when you use enough credits.

Comparison with this seller’s pay-per-call prices, before wallet gas and payment fees. Unused credits have no assumed cash value. Specialized funding-only packs may cost less for funding-only workloads; compare the free quote before buying. One package provides one API key; this comparison does not assume credits from separate keys can be pooled.

15,000 audit calls: exact Fleet quote · 500,000 audit calls: exact Portfolio quote

Reproduce the premium deliverables before purchase

Three public fixtures run through the actual analysis code. These are published test inputs, not customer success stories or verified payments.

• Duplicate ledger fixture: $10,000 gross claimed value becomes $5,000 unique claimed value; missing payment challenge evidence holds execution.
• Two-workspace fixture: 5 portfolio findings detect reused settlement and receipt references, recipient drift, a shared-worker limit and a combined budget breach.
• A complete declared-input fixture returns ready with reproducible input and result hashes. A ready result still requires independent verification before payment.

Included with the analysis: ranked seller findings, a deduplicated ledger, mission assignments and exposure metrics, prioritized remediation with recheck steps, and input-bound SHA-256 evidence. The Control Tower also supplies cross-workspace checks and a portfolio execution contract.

Total analysis input is limited to 60,000 bytes; row limits are upper bounds within that payload. Large portfolio responses include up to 150 ledger detail rows and 20 remediation actions per workspace, with explicit truncation flags; totals and hashes cover the full input. The standalone Command Center is sufficient for one workspace. Choose the Control Tower when you need shared-workspace checks and global policies.

Where these products fit

• High-volume agents repeating authorized web and data workflows within a fixed credit budget.
• Agent orchestration pipelines that need bounded tool checks, source inspection, or structured API calls.
• Procurement and payment-control systems that require exact tool pricing and settlement evidence.

Different tools consume different credit amounts. Credits do not represent a fixed number of requests; check the exact cost for each intended tool. No guaranteed returns, sales, or savings.

Buyer controls: view exact prepaid cost before use; set X-Max-Credits for a hard per-call cap; reuse your idempotency key on identical retries; failed prepaid executions return reserved credits. For smaller workloads, consider cheaper packages instead.

Inspect supported tools and exact credit costs · Read workflow examples

How an authorized purchasing agent buys on Base

1. Fetch the public machine catalog and verify which package matches the task and budget.
2. For a purchase explicitly approved by the buyer, POST to /wallet/base/start with an existing Base payer address and product ID.
3. Independently verify the returned Base chain, USDC contract, merchant address, exact amount and expiration before signing.
4. Poll the returned /wallet/status URL and use the API key only after actual on-chain payment verification and credit activation.

POST https://bounty-engineer-x402-prod.onrender.com/wallet/base/start
Content-Type: application/json

{"product":"operator","payer":"BUYER_OWNED_BASE_ADDRESS"}

No charge is made by viewing these pages. The invoice is not an x402 settlement; Base USDC payment is separate and explicitly authorized by the buyer.

Read the agent purchase contracts →

Inspect real premium tool results before paying

A one-off x402 API analysis is different from a prepaid credit package. These free worked examples use published sample inputs, not customer results.

The buyer independently authorizes each paid call. Monthly PayPal subscriptions are separate and customer-approved. Review technical contracts.