CluePilot checks a single factual claim about the official TypeSafe Jev JavaScript/TypeScript SDK. The supported snapshot is package version 0.6.0, commit 66880ccded6cb642dc1809620c2b108c33730214. It is an independent service, not endorsed by TypeSafe, Circle or Google. Treat a result as evidence assistance, not certification. The source snapshot is fixed; it does not promise current server behavior or the newest published package. Always include TypeSafe or Jev and SDK or JavaScript/TypeScript in the claim so the scope can be identified before payment. Supported questions concern SDK configuration, API key configuration, question builders, input validation, declared return types, timeout settings, retry conditions and error classes. Model accuracy, real latency, pricing, account restrictions, server internals, other language SDKs, and versions other than the stated snapshot are out of scope. Submit exactly one independently testable claim. For example: TypeSafe Jev JS/TS SDK 0.6.0 requires Node.js 20 or newer. Do not send private source code, credentials, personal information or payment signatures inside the claim. The service never executes user-supplied code. It does not call the Jev inference API. Before your first request, the responsible adult professional operator must read /terms and /privacy and have authority to agree for their organization. Users must be in a region supported by the Gemini API. This service is for professional and business development use. Use signifies agreement; a blockchain payment signature is not proof of contractual consent. The public agent API does not require an invitation, login, subscription or proprietary consent header. The home page at / provides public API information. The owner interaction UI has been retired. /v1/verify-claim, /service.json, /openapi.json, /guide, /terms and /privacy remain public. Send POST /v1/verify-claim with Content-Type application/json and a body containing claim plus optional options: language ja or en and mode standard. Claim length is 1 to 2000 characters. First send without PAYMENT-SIGNATURE. A free eligibility check sends the claim to Gemini and may return HTTP 422 for unsupported or multiple claims, 429 for rate or budget limits, or 503 for a provider failure. These failures do not settle a payment. An eligible request returns HTTP 402 with an x402 v2 exact payment requirement in the PAYMENT-REQUIRED header and a JSON body. Read the actual quote; never infer payment details from this prose alone. The production price is 0.10 native USDC, atomic amount 100000, on the enabled network shown in the quote. Check network, asset, amount, recipient, authorization expiry and resource before signing. Use the exact recipient and asset from the published quote and service metadata. The only supported payment integration is x402 v2 exact. Circle Gateway, MPP and SIWX are not implemented. Select exactly one offered network. Do not substitute bridged USDC or send a plain transfer as a replacement for the required authorization. Use a compatible x402 client with an authorized wallet. Repeat the identical JSON body with the base64 PAYMENT-SIGNATURE payload. Preserve the returned X-Payment-Order identifier and send it on retries when available. Changing the claim or options changes the bound input. Never create a fresh authorization simply because a response is slow or uncertain. HTTP 202 means payment is pending, settlement is unknown, or paid research is waiting for capacity. PAID_PROCESSING_PENDING with payment_settled=true means payment is confirmed. Respect Retry-After and retry_action; preserve the original body and signature. Capacity waiting does not consume a research attempt. HTTP 409 can indicate an input mismatch, expired quote, closed unpaid order or refunded payment. Inspect the machine-readable error code instead of treating every error as an invitation to pay again. For successful paid processing, Brave searches for the official repository and the service supplements the discovered candidates with all seven independently known, allowlisted files from the fixed source revision, verifying every fetched file against its registered hash. A repository landing page is mapped to its fixed README; an unindexed implementation file is still a retrieval candidate. The service does not broaden to unreviewed websites. Source fetching remains bounded to those seven files with concurrency three. Exact relevant passages share a 30,000-character total budget and at most 8,000 characters per file. Fetch failures and omitted passages are disclosed in limitations; full source coverage does not guarantee a definitive verdict. Gemini analyzes selected source text; deterministic checks verify excerpt matching and impose quotation limits. The response includes a verdict, supporting or contradicting evidence, source references and limitations. Insufficient evidence and contradictory evidence are valid paid results. Confidence describes evidence sufficiency and is not a calibrated probability of correctness. SDK source excerpts include the applicable MIT notice. They describe the pinned implementation, not measurements of the hosted model. Read limitations before relying on a finding. A type declaration does not demonstrate that the remote service always behaves accordingly. No live performance benchmark or quality certification is supplied. Published observations about code are not guarantees about third-party availability. Research content, search results, search-derived URLs, fetched text, excerpts and assessments are transient. Save no assumption that a result can be retrieved later. Completed-payment replay returns HTTP 410 RESULT_NOT_RETAINED without another investigation or settlement. Customer inputs, pre-search eligibility decisions, payment evidence and numeric usage and cost records are retained for operation, retries and refunds. Google and other providers have their own processing and limited retention terms; this is not an end-to-end zero-retention promise. Do not store or redistribute search-derived material without the necessary rights. Processing failures may be retried up to three total attempts on the same settled payment. For errors, inspect payment_settled, retryable, retry_action and operator_action_required. Unrecoverable failures and lost initial responses require manual refund review; refunds are not automatic. Contact the operator through the address in OpenAPI info.contact with the order identifier and minimal details. Never email private keys or payment signatures. Approved refunds go to the original payer on the original network. Keep your original payment proof securely for authenticated status requests. Eligibility, Circle payment checks and paid research each have separate capacity for two operations. Eligibility uses refilling limits: three requests per minute per IP (burst three; IPv6 grouped by /64), and thirty new classifications per minute globally (burst two). Cached eligibility and joining identical in-flight work do not consume global classification tokens. There is no daily eligibility lockout. Circle retries for one order wait at least five seconds; consecutive failures back off to sixty seconds or a longer provider-specified delay. These delays survive restarts. Follow Retry-After on 429/202 and payment errors. The finite shared Brave search budget still applies. HTTP 429 or maintenance HTTP 503 means wait and follow instructions, not split requests across identities to bypass limits. When contacting support, distinguish an unpaid eligibility error, an uncertain settlement, a paid processing failure and a completed response that was lost. This distinction prevents duplicate payments and preserves the correct recovery path.