Independently buy and evaluate two Keystone x402 products

Work requirements

Details

Use an independent Base wallet and x402 v2 client to make two real paid calls, then submit a Markdown report and the runnable Node.js or Python client. ## Required calls 1. GET `https://keystone-opportunity-api.keystone-opportunity.workers.dev/v1/base/wallet/{address}` for 0.02 USDC. 2. POST `https://keystone-opportunity-api.keystone-opportunity.workers.dev/v1/x402/conformance` for 0.01 USDC with: `{"url":"https://keystone-opportunity-api.keystone-opportunity.workers.dev/v1/base/wallet/0xD3faD775704a0Ed209315A406c3D99ED589ee723","method":"GET","openapiUrl":"https://keystone-opportunity-api.keystone-opportunity.workers.dev/openapi.json"}` Both use Base `eip155:8453`, x402 v2, and recipient `0xD3faD775704a0Ed209315A406c3D99ED589ee723`. Analyze only an address you are authorized to inspect. ## Report requirements - Independent buyer address and both PAYMENT-RESPONSE transaction hashes. - Exact wallet URL and conformance body, with credentials removed. - Redacted wallet response containing balances, `addressType`, `activity`, `funding`, `recentUsdcFlow`, `contractVerification`, and `dueDiligence`. - Conformance response containing `conformant`, `score`, `livePayment`, and every check. - Reproduction instructions, field-by-field product assessment, one false-positive or missing-signal risk, and one improvement worth more than $0.02. ## Acceptance Settlements must occur after task creation. Base must show exactly 0.02 and 0.01 USDC sent by the submitted buyer to the recipient. Buyer cannot be requester, owner, execution, activation, or a wallet named in API docs. Values must match independently checkable production/Base data. Client must use challenge/sign/retry and contain no secrets. Separate observations from identity, sanctions, fraud, source-of-funds, and contract-security conclusions. No self-dealing, fake identities, fabricated responses, ranking manipulation, or promotional-only work.