xQuant - xQuant Community AI Trading Algorithm

Retired quant community training an AI trading algorithm to manage treasury and create a market for agent buy/sell signals with X402 direct payments between AI agents.

Paid verification

How it works

No sponsored paid call yet.

Pay this endpoint once from your own wallet (Base USDC, up to $1.00) and we call it and record what came back. Your wallet pays the listed recipient directly; Agent Tools never holds funds. Sponsored checks prove delivery; they do not count as demand.

Quality grade

How grading works

D 29.8 / 100 capped at D while down

Availability 0.0 / 40

Endpoint did not respond

Payability 20.0 / 20

✓ Answers a real HTTP 402 challenge
✓ Publishes a /.well-known/x402 descriptor
✓ Payment address on record
✓ Settlement network declared
✓ Price declared

Demand 9.8 / 40

4 distinct payers, 11 USDC transfers in the last 30 days

Owner verified 0.0 / 3

Nobody has claimed this listing yet

Endpoint last checked 6 h ago. On-chain activity last read 2 d ago. Availability and on-chain demand are both re-probed daily; the grade updates automatically on the next pass. This grade sets search order and leaderboards; the readiness score below is shown for reference only.

x402 readiness

D · 47/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here D, 29.8/100), which weighs availability, payability and on-chain demand. How the two differ

Valid payment requirements	10/10	Payment requirements carry a payee, a mainnet network and a price.
Live 402 challenge	0/25	Endpoint did not answer.
x402 version	5/10	Speaks x402 v1; v2 is current.
Signed descriptor	n/a	No x402 standard defines a signed descriptor.
Uptime (30 days)	9.84/15	21/32 probes succeeded over 30 days (66%).
Resource declaration	5/10	Declares 1 paid resource(s).
Verified identity	5/10	Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Freshness + modern flags	5/5	seen in a source within 7 days; declares x402.
Security declaration	n/a	Payment is the access control for an x402 resource.

Applicable criteria total 85 points, scaled to 100.

Payment evidence: x402_challenge — We sent a request and got a live HTTP 402 challenge. Also: x402_manifest, catalog_listing. Qualifies the payment claim; adds no points.

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily probe of the paid endpoint, its payment requirements and 30-day probe history. Signed descriptor and security declaration are n/a for x402 (payment is the access control), as is an x402 version we have not observed; the remaining points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 10,060 reachable x402 APIs in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness: Higher than 5% of peers; This listing 47 · peer median 78
Latency: Faster than 31% of peers; This listing 349 ms · peer median 205 ms

Where it loses the most points, and how to win them back

Live 402 challenge −25 — Answer the paid path with a valid 402 challenge.
Now: Endpoint did not answer.
Uptime (30 days) −5.2 — Stay reachable in our daily probes.
Now: 21/32 probes succeeded over 30 days (66%).
x402 version −5 — Support the current protocol revision.
Now: Speaks x402 v1; v2 is current.

How many agent tools actually work · All statistics

How to call

cURL · x402-fetch / x402-axios will auto-handle 402

curl -sS -i -X GET http://www.xquant-api.xyz/api/xQuant-stonk  # expect HTTP 402 Payment Required (about $1.0/call)

/.well-known/x402.json

http://www.xquant-api.xyz/.well-known/x402

Listed in

Directories this entry was found in.

x402scan since 2026-05-22