{ "schema": "varexis-index-free-publication-preview/1", "catalogue_version": "pub-1-tranche-51-v1", "route_id": "agentic_reviewed_x402_flow_selection_before_resource_execution", "record_id": "VXI-EXT-PROCUREMENT-X402-FLOW-SELECTION-BEFORE-RESOURCE-EXECUTION-01-v1", "question": "Must every x402 v2 payment settle after the protected resource executes?", "answer": "The reviewed v2 specification defines authorization, upfront and escrow flows with different ordering around resource execution. A non-authorization flow must be declared in the offered requirements. Clients must not construct payments for an unrecognised flow, and servers must reject unsupported method-and-flow combinations.", "records": [ { "record_id": "VXI-EXT-PROCUREMENT-X402-FLOW-SELECTION-BEFORE-RESOURCE-EXECUTION-01-v1", "url": "/varexis-index/records/x402-flow-selection-before-resource-execution.json", "content_sha256": "483621d9ecf1e1fba3a3ac728438192231db44566ec3b58270a92d034a5bceae", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-24T21:35:02.243Z", "record_id": "VXI-EXT-PROCUREMENT-X402-FLOW-SELECTION-BEFORE-RESOURCE-EXECUTION-01-v1", "record_kind": "external_reference", "title": "x402 payment flow and execution order", "system": "x402 Foundation", "evidence_family": "vendor_evidence_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Must every x402 v2 payment settle after the protected resource executes?", "near_questions": [ "Does x402 always charge after a successful API call?", "How does x402 escrow differ from authorization flow?", "Can an agent accept an unknown x402 paymentFlow?", "When does an x402 upfront flow commit payment?" ], "supported_claims": [ { "claim": "The reviewed v2 specification defines authorization, upfront and escrow flows with different ordering around resource execution. A non-authorization flow must be declared in the offered requirements. Clients must not construct payments for an unrecognised flow, and servers must reject unsupported method-and-flow combinations.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "Independent verification of payment, delivery or deployed controls", "Implementation conformance and the effect of a failed buyer request remain unverified.", "Buyer deployment testing, live runtime enforcement, certification or permission to act", "Expanded capabilities or licences for existing INDEX executables" ], "public_summary": "The reviewed v2 specification defines authorization, upfront and escrow flows with different ordering around resource execution. A non-authorization flow must be declared in the offered requirements. Clients must not construct payments for an unrecognised flow, and servers must reject unsupported method-and-flow combinations.", "related_record_ids": [], "source_review": { "source_type": "official_external_documentation", "source_title": "X402 Protocol Specification", "source_url": "https://raw.githubusercontent.com/x402-foundation/x402/4241d56cae2fb7ed06cd18e3a9ff2a3457b1ce54/specs/x402-specification-v2.md", "checked_on": "2026-10-24", "candidate_record_id": "VXI-EXT-PROCUREMENT-X402-FLOW-SELECTION-BEFORE-RESOURCE-EXECUTION-01-v1", "candidate_record_sha256": "5cbdb4fac4a5ae4f199fbb0d0301beef949728bbacb69e14edf725beca02f430", "method": "Primary documentation reviewed for the published bounded statement.", "deployment_tested_by_varexis": false, "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research." }, "answer_policy": { "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY", "bounded_answer": "The reviewed v2 specification defines authorization, upfront and escrow flows with different ordering around resource execution. A non-authorization flow must be declared in the offered requirements. Clients must not construct payments for an unrecognised flow, and servers must reject unsupported method-and-flow combinations.", "required_buyer_context": "Offered transfer method and paymentFlow; Client and facilitator supported combinations; Execution, deposit and final-charge evidence. Buyer deployment not inspected.", "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state." }, "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.", "decision_profile": { "schema": "varexis-vendor-evidence-review/1", "review_status": "documentation_review_only", "checked_on": "2026-10-24", "claim_to_check": "Must every x402 v2 payment settle after the protected resource executes?", "documented_statement": { "status": "documented", "statement": "The reviewed v2 specification defines authorization, upfront and escrow flows with different ordering around resource execution. A non-authorization flow must be declared in the offered requirements. Clients must not construct payments for an unrecognised flow, and servers must reject unsupported method-and-flow combinations.", "source_ids": [ "x402-v2" ] }, "review_inference": { "status": "review_inference", "statement": "Understand whether funds are committed before an operation can fail. This is a review decision, not an observed buyer result.", "source_ids": [ "x402-v2" ] }, "buyer_evidence_required": [ "Offered transfer method and paymentFlow", "Client and facilitator supported combinations", "Execution, deposit and final-charge evidence" ], "review_condition": { "status": "varexis_review_policy", "statement": "Do not assume one settlement order across all x402 schemes." }, "unknowns": "Implementation conformance and the effect of a failed buyer request remain unverified.", "unknown_finding": { "status": "unknown", "statement": "Implementation conformance and the effect of a failed buyer request remain unverified." }, "evidence_sources": [ { "source_id": "x402-v2", "url": "https://raw.githubusercontent.com/x402-foundation/x402/4241d56cae2fb7ed06cd18e3a9ff2a3457b1ce54/specs/x402-specification-v2.md", "final_url": "https://raw.githubusercontent.com/x402-foundation/x402/4241d56cae2fb7ed06cd18e3a9ff2a3457b1ce54/specs/x402-specification-v2.md", "status": 200, "captured_at_utc": "2026-10-24T21:23:33.811Z", "sha256": "55a86e49a2fc14fd1c94240cd7f74c2950b9ab61d3d577173defd39ae2eaaa44", "bytes": 38468, "title": "X402 Protocol Specification", "hash_basis": "Decoded HTTP response body bytes", "rights_review": "Original factual paraphrase and source metadata only; Apache-2.0 repository captures retained privately and not redistributed.", "checked_on": "2026-10-24", "capture_status": 200, "claim_review_completed": true, "reviewed_sections": [ "7.1 POST /verify", "7.2 POST /settle", "6.1 Asset Transfer Methods and Payment Flow Models" ], "version_context": "Pinned x402-foundation/x402 revision 4241d56cae2fb7ed06cd18e3a9ff2a3457b1ce54 captured 2026-10-24. Documentation revision, not evidence that any buyer deployment conforms." } ], "observed_deployment": false, "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.", "paid_value": { "decision_context": "Understand whether funds are committed before an operation can fail.", "free": "Complete review, sources, practical questions and limitations; may be saved locally.", "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.", "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.", "excluded": [ "Fresh vendor research", "Continuous monitoring or change alerts", "Testing the buyer configuration", "Private evidence or vendor certification" ], "integrity": "Hashes identify content versions; they do not prove truth or provide a signature." }, "revalidation": { "trigger": "A saved purchase does not recheck the source or buyer configuration.", "specific_watch": "Recheck the pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome." }, "buyer_relevance": "Understand whether funds are committed before an operation can fail.", "refusal_conditions": [ "Do not assume one settlement order across all x402 schemes." ] }, "niche": { "niche_id": "agent-authority-action-evidence", "label": "Agent Authority & Action Evidence", "classification_id": "payments", "classification_label": "Agent Payments, Authority & Transaction Evidence", "topic_id": "payments", "buyer_intent": "Understand whether funds are committed before an operation can fail.", "comparison_role": "supplementary_discovery" }, "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.", "service_route": { "request_guide": "/varexis-index/request.html", "request_workflow": "/varexis-index/request-workflow.json", "service_id": "single_request", "service_routes_url": "/varexis-index/service-routes.json", "payment_required": true, "availability_endpoint": "/api/index/capabilities", "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED", "checkout_url": "/index-access" }, "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.", "human_page": "/varexis-index/catalog.html#x402-flow-selection-before-resource-execution", "machine_readable_record": "/varexis-index/records/x402-flow-selection-before-resource-execution.json" } } ], "access": { "mode": "exact_http_only", "payment_required": false, "purchase_url": null, "mcp_preview_available": false, "paid_saved_retrieval_available": false, "natural_language_search_qualified": false }, "boundary": "Catalogue additions are available free through the exact HTTP JSON links below. Enhanced natural-language discovery is not yet qualified for these records. They are outside MCP search, MCP preview and paid saved retrieval. No search qualification, executable capability or entitlement is added.", "content_sha256": "f4ccd791f3f4fdcc21e806b152a500c3d562070fe7c3ef8bdb47fda57a225977" }