x402-market-api

Identical to test-echo-cdp-fresh except priced at 0.10 USDC (= 100000 atomic units) instead of 0.01. Used to test the hypothesis that Coinbase Bazaar has an undocumented price floor above $0.01. Use this tool when validating x402-market end-to-end via the Coinbase Facilitator path with a higher per-call price. Echoes the JSON body. Returns { request_id, timestamp, method, echoed }. When to use: - Confirming the listing surfaces in Coinbase Bazaar /discovery/resources at the higher 0.10 USDC price point. - A/B testing Bazaar indexing behaviour vs the existing 0.01 USDC listings (test-echo-cdp, test-echo-cdp-2, test-echo-cdp-fresh). - Smoke-testing CDP-mediated settle on Base mainnet at the 10x price step. Output: request_id: server-generated UUID for tracing. timestamp: ISO-8601 UTC of when the upstream handled the request. method: the HTTP method observed at the upstream. echoed: byte-identical copy of the JSON body you sent. Use cases: - test integration - echo for debugging Price: 0.1 USDC per call (x402 settlement on Base).

Third cdp-mode echo listing, created after the v2-spec PaymentPayload.extensions fix. Used to test whether a brand-new resource indexed only with the corrected wire format gets picked up by Bazaar discovery. Use this tool to verify x402-market end-to-end via the Coinbase Facilitator settlement path. Echoes whatever JSON you POST. Returns { request_id, timestamp, method, echoed }. When to use: - Verifying a buyer SDK that signs EIP-3009 transferWithAuthorization rather than broadcasting txs directly. - Confirming the listing appears in Coinbase Bazaar discovery (https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources). - Smoke-testing the CDP-mediated settle path end-to-end on Base mainnet for under one cent. Output: request_id: server-generated UUID for tracing. timestamp: ISO-8601 UTC of when the upstream handled the request. method: the HTTP method observed at the upstream. echoed: byte-identical copy of the JSON body you sent (or {} for GET/HEAD). Use cases: - test integration - echo for debugging Price: 0.01 USDC per call (x402 settlement on Base).

Second cdp-mode listing identical to test-echo-cdp, used to A/B test whether the Bazaar indexer picks up newly-created resources differently from one that has been live for several days. Use this tool to verify x402-market end-to-end via the Coinbase Facilitator settlement path. Echoes whatever JSON you POST. Returns { request_id, timestamp, method, echoed }. When to use: - Verifying a buyer SDK that signs EIP-3009 transferWithAuthorization rather than broadcasting txs directly. - Confirming the listing appears in Coinbase Bazaar discovery (https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources). - Smoke-testing the CDP-mediated settle path end-to-end on Base mainnet for under one cent. Output: request_id: server-generated UUID for tracing. timestamp: ISO-8601 UTC of when the upstream handled the request. method: the HTTP method observed at the upstream. echoed: byte-identical copy of the JSON body you sent (or {} for GET/HEAD). Use cases: - test integration - echo for debugging Price: 0.01 USDC per call (x402 settlement on Base).

Same echo endpoint as test-echo-prod, but settlement is routed through the Coinbase Facilitator instead of self-verified on-chain. Used to validate Coinbase Bazaar discoverability for x402-market listings. Use this tool to verify x402-market end-to-end via the Coinbase Facilitator settlement path. Echoes whatever JSON you POST. Returns { request_id, timestamp, method, echoed }. When to use: - Verifying a buyer SDK that signs EIP-3009 transferWithAuthorization rather than broadcasting txs directly. - Confirming the listing appears in Coinbase Bazaar discovery (https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources). - Smoke-testing the CDP-mediated settle path end-to-end on Base mainnet for under one cent. Output: request_id: server-generated UUID for tracing. timestamp: ISO-8601 UTC of when the upstream handled the request. method: the HTTP method observed at the upstream. echoed: byte-identical copy of the JSON body you sent (or {} for GET/HEAD). Use cases: - test integration - echo for debugging Price: 0.01 USDC per call (x402 settlement on Base).

Test endpoint that echoes back input. Used for SDK integration testing and end-to-end verification. Use this tool when the user wants to verify x402-market end-to-end (payment, proxy, response) without spending real money on a meaningful API. Echoes whatever JSON you POST. Returns { request_id, timestamp, method, echoed }. When to use: - Smoke-testing your buyer wallet against Base mainnet x402 settlement. - Confirming your MCP host (Claude Desktop, Cursor) actually invokes pay_and_call rather than hallucinating. - Demoing the marketplace to someone for under one cent. Output: request_id: server-generated UUID for tracing. timestamp: ISO-8601 UTC of when the upstream handled the request. method: the HTTP method observed at the upstream. echoed: byte-identical copy of the JSON body you sent (or {} for GET/HEAD). Use cases: - test integration - echo for debugging Price: 0.01 USDC per call (x402 settlement on Base).

Test endpoint that echoes back input. Used for SDK integration testing and end-to-end verification. Use this tool when the user wants to verify x402-market end-to-end (payment, proxy, response) without spending real money on a meaningful API. Echoes whatever JSON you POST. Returns { request_id, timestamp, method, echoed }. When to use: - Smoke-testing your buyer wallet against Base mainnet x402 settlement. - Confirming your MCP host (Claude Desktop, Cursor) actually invokes pay_and_call rather than hallucinating. - Demoing the marketplace to someone for under one cent. Output: request_id: server-generated UUID for tracing. timestamp: ISO-8601 UTC of when the upstream handled the request. method: the HTTP method observed at the upstream. echoed: byte-identical copy of the JSON body you sent (or {} for GET/HEAD). Use cases: - test integration - echo for debugging Price: 0.01 USDC per call (x402 settlement on Base).

Predicts the winner and run distribution of upcoming Nippon Professional Baseball (NPB) games using a model trained on team-level offense/defense, starting pitcher splits, recent form, and ballpark factors. Returns calibrated win probabilities (sum to 1.0) and an expected run differential. Suitable for betting analysis, fantasy lineup decisions, content generation, and quantitative research. Updated daily before first pitch. Use this tool when the user wants a model-backed prediction for an upcoming Nippon Professional Baseball game. Returns calibrated win probabilities and an expected run differential. When to use: - User asks "who will win tonight's NPB game between G and T?" - Building a fantasy lineup or DFS slate that needs win-probability inputs. - Backtesting a betting strategy against historical NPB outcomes. - Deciding which side of a sportsbook line carries positive expected value. Output: home_win_prob / away_win_prob: calibrated probabilities, sum to 1.0. expected_run_diff: home runs minus away runs (positive = home favored). confidence: model's self-assessed reliability ("low" when teams have insufficient recent data). model_version: pin for reproducibility. Use cases: - Decide which side to bet given a sportsbook line for an NPB game. - Generate pre-game preview articles or social posts with a defensible model-backed angle. - Filter a slate of NPB games down to the highest-edge picks for fantasy or DFS. - Backtest a betting strategy by querying historical predictions vs. closing lines. - Surface upset alerts when model probability disagrees sharply with implied market probability. Price: 0.05 USDC per call (x402 settlement on Base).