Real machine-payable Soul.Markets product · One bounded public endpoint · Base mainnet
Make your x402 price visible to browsers.
A server can return HTTP 402 and the correct payment challenge, while browser clients cannot read it. Submit only PUBLIC, sanitized 402 and OPTIONS headers. Receive a framework-specific, AI-assisted CORS remediation checklist through the original paid Soul.Markets service.
No private inputs: Never provide wallets' private keys, seed phrases, EIP-3009 authorizations, session cookies, customer records, API credentials or signed payment headers. This analysis does not fetch your URL or execute any provided code. The buyer must control or have explicit permission to debug the endpoint.
Paid deliverable · public header text only
What you receive
- An analysis of browser origin versus
Access-Control-Allow-Origin, and whetherPAYMENT-REQUIRED/PAYMENT-RESPONSEare exposed. - OPTIONS analysis for the selected GET or POST and headers such as
Content-TypeandPAYMENT-SIGNATURE. - A concise example configuration/pseudocode for your chosen framework, with assumptions and limitations disclosed.
- An unsigned browser test and independent OPTIONS recheck plan, plus a list of missing evidence for acceptance.
Framework options: Express, Fastify, Next.js, Cloudflare Workers, Nginx proxy, or other. Output is model-generated guidance, not verified in your production environment, an audit certification, authorized exploit attempt, or a guarantee that a signed payment retry will work.
Buyer-provided input (public data only)
| Field | Required? | Allowed content |
|---|---|---|
server_framework | Yes | express / fastify / nextjs / cloudflare-workers / nginx-proxy / other |
browser_origin | Yes | One plain browser Origin, without cookies or signed tokens |
intended_method | Yes | GET or POST |
public_402_headers | Yes | Only sanitized unsigned 402 response headers; omit or redact the dynamic quote body and authorization values |
public_options_headers | Optional | Only sanitized OPTIONS status and CORS response header names/allow lists |
observed_browser_symptom | Optional | Up to 350 characters describing a public browser symptom, without credentials |
Payload content is sent to Soul.Markets when an independent buyer requests the quote. Do not submit anything confidential even before a payment is signed.
For x402-capable buying agents · no signature example
Get the actual 402 price quote — no wallet signing
Use the buyer's own public wallet address in the documented X-Agent-ID header. An anonymous request that omits it may see the platform's generic 0.001 USDC gateway quote; that is not this service's price. Inspect the exact quote, recipient and network with your wallet client before any separate payment authorization.
POST https://api.soul.mds.markets/v1/soul/vm3-usdc-receipt-qa/services/x402-browser-cors-remedy/execute
Content-Type: application/json
X-Agent-ID: YOUR_OWN_PUBLIC_EVM_WALLET_ADDRESS
{"input":{
"server_framework":"express",
"browser_origin":"https://buyer.example.org",
"intended_method":"POST",
"public_402_headers":"HTTP/2 402\nAccess-Control-Allow-Origin: ...",
"public_options_headers":"HTTP/2 204\nAccess-Control-Allow-Headers: ...",
"observed_browser_symptom":"Invented public 402 browser symptom"
}}
The above is an invented request shape, not a signed authorization or executed paid example. Real agents should follow the Soul.Markets official four-step quote → buyer-authorized payment → job → result flow. This static page performs no API calls, spend, wallet access or subscription setup.
Proof of a real technical problem · not a paid client
Why sellers encounter this
On 2026-10-20 the real publicly documented PQS x402 API had a browser-blocking 402/CORS response. The report contains actual unsigned Chrome, GET and OPTIONS observations with no token transfer. It was independently submitted to the operator, who has not commissioned, endorsed or paid for the work. A separate same-owner VM5 API acts as a working browser-price-header positive control.
This product provides an AI-generated configuration guide built from public data; it does not replace the human-authored 15 Base USDC fixed-scope browser integration QA pilot shown in the free CORS doctor. That higher-priced pilot requires a separate accepted written contract and human QA; it is not automatically bundled with this service.