Paid services matching “test data”

Generate realistic-looking test data: users, companies, Luhn-valid test cards and addresses. Deterministic by seed — the same seed always produces identical records, so your tests and fixtures are reproducible. All data is synthetic; card numbers pass Luhn but are not real accounts. Use this when an agent needs to seeded test users, companies and cards — reproducible.

Honest crypto prediction test: pick a Binance coin, timeframe (1h/4h/1d), range and horizon. Trains a scikit-learn random forest walk-forward (past data only, tested on unseen later candles) and reports accuracy vs baselines (always up, majority, last move repeats), p-values, feature importance, a fee-aware strategy vs buy-and-hold, and the latest prediction with a clear no-edge verdict. Body: {"s

Test endpoint for verifying x402 payment integration end to end. Returns a static greeting in the Agent Tollbooth standard response envelope. Not a data product — use it to smoke-test your x402 client for $0.001 before calling our compliance endpoints: OFAC sanctions screening ($0.01) and FDIC bank verification ($0.01), listed under this same payTo address.

Send an HTTP request to any URL from our servers and receive the full response — including the status code, all response headers, and the body content. Supports GET, POST, PUT, PATCH, DELETE, and HEAD. Automatically follows up to 3 redirects. Useful for testing endpoints, verifying servers are responding correctly, debugging redirect chains, or fetching raw data without needing a local setup.

What a seller's payTo address earned from x402 payments on Base in the last days, read from the chain: total, distinct and repeat payers, per day, per price, top payers and recent payments, with plain USDC transfers counted apart and your own test wallets left out on request. Includes the seller's Bazaar listings with their payers, calls and measured uptime.

Arbitrary-precision integer arithmetic (add, subtract, multiply, power) beyond IEEE-754 float precision, using native BigInt. Operands are passed as digit strings so precision is never lost in transit. For power, the combined magnitude (base digit count x exponent) is capped at 50000 to bound response size, in addition to the per-operand digit cap and exponent cap.