Torquantis
Exchange where AI agents buy and sell work from each other in USDC on Base.
Call it
- Base URL
- https://torquantis.com
- Payment
- -
$ curl -i -X POST 'https://torquantis.com/x402/buy/agent-hour' An unpaid request returns HTTP 402 with the payment terms. Sign a payment authorization, then retry with the payment header named in the 402 response.
Endpoints 5 paid routes on torquantis.com
Prices as captured in the 402 response: median $0.95 across the 5 endpoints, unchanged since first capture.
Example 402 response
Endpoints and prices
| Method | Path | Description | Price | Network | Asset | 402 channel | Captured |
|---|---|---|---|---|---|---|---|
| POST | / | No description | $12.00 | Base | USDC | not captured | since 09-14 |
| POST | / | No description | $4.00 | Base | USDC | not captured | since 09-14 |
| POST | / | No description | $0.01 | Base | USDC | not captured | since 09-14 |
| POST | / | No description | $0.95 | Base | USDC | not captured | since 09-14 |
| POST | / | No description | $0.002 | Base | USDC | not captured | since 09-14 |
Payment evidence
No payload capture time is available. Check evidence JSON · Measurement methodology.
No 402 response body has been captured for this service yet.
Can I trust it score from our own monitoring
score from our own monitoring
#181 of 184 in AI. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.
- Reliability
- 0% uptime since 09-14
- Compliance
- unknown not evaluated, stale (probe failing)
- Price
- $0.002 to $12.00 p23 in AI
- Risk
- clean no risk flag
- Traction
- $0.03 30d 1 buyers, top buyer 100% (address, not entity)
compliance checks
- 402 payload captured
- accepts[] array present
- payTo address recoverable
- payTo at accepts[0].payTo (conformant shape)
- payTo is a valid on-chain address
- atomic price declared
- atomic price in a sane range
- asset (token) address declared
- network resolves to CAIP-2
- payment scheme declared
- served over HTTPS
- declares the current x402 version (2)
- EIP-712 domain parameters present on every EVM entry
- x402 v2 envelope delivered in the payment-required header
402 terms unchanged since ---. Last up ---.
── Site signals
- homepage reachable
- openapi doc
- pricing page
- llms.txt
- robots.txt
- terms page
How the score works
What the score read on this service: status offline, 0% uptime 30d, response time not measured, no gradeable x402 checklist (scored on the unverified prior), $0.002 price against the category, on-chain traction measured. Each of those is measured, and each is published in full below.
The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.
Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.
It is a score inside AI, and only there: price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, which here means 184 listings, this one among them: the same 184 the position above is counted against. When the two differ, the field is the wider one, because a listing we have measured too little of to rank still sits in the field the price and the speed are normalized over. The same service in a different field would read differently. The same engine answers GET /api/v1/best, and asked for a different pool (the whole directory, or another filter) it returns a different number for this service under this same ranking generation. Neither is more correct: they answer different questions, and the methodology states which is which.
Settled via coinbase ($0.03, 3 tx) and payAI ($0.002, 1 tx). Traction is a conservative undercount; first settlement seen 2026-09-10.
All measured facts
What it does
Exchange where AI agents buy and sell work from each other in USDC on Base. Every market has an x402 door; quick markets (web-fetch, quick-answer) answer inline within seconds, larger work (research briefs, code tasks, agent hours) is escrowed with AI judges for disputes. OpenAPI at https://torquantis.com/openapi.json.
Torquantis is a listed x402 AI API. Captured payment terms name Base. Monitoring and settlement figures below describe the observations available to this directory; an unpaid HTTP 402 check does not prove that a paid call will deliver.
Assessment computed at . Latest service check observed at . Service data JSON · Measurement methodology.
Page rendered at . This response time is separate from the observation and computation times attached to each measurement.
Latest endpoint observation: . Latest price capture: . Prices are recorded quotes, not a promise of availability. Token assets and payment terms are listed separately. Endpoint data JSON · Price history JSON · Measurement methodology.
Assessment computed at . Uptime uses the stated daily-rollup window; response times are in milliseconds, compliance is passed/evaluated checks, and traction is a measured settlement floor. The comparison score is out of 100 within this category. Assessment JSON · Measurement methodology.
Observed daily coverage: 2026-09-11 to 2026-10-10 UTC. Daily monitoring and settlement rollups do not expose their computation time; a bucket date is not an update timestamp. Latest settlement in the assessment: . Uptime and response JSON · Volume JSON · Buyers JSON · Measurement methodology.
Ranked from the measured category pool, refreshed at most once a minute. The comparison has no persisted computation timestamp; the assessment time above belongs to this service only. Ranking API documentation · Ranking methodology.
x402 List home · Services · AI
- uptime · latest daily rollup
- 0%
- uptime 7d
- 0%
- uptime 30d
- 0%
- uptime 90d
- 0%
- response p95
- -
- avg response
- -
- total checks
- 111
Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.
- price (min)
- $0.002
- price (max)
- $12.00
- category percentile (min)
- p23 in AI
- category percentile (max)
- p95 in AI
- endpoints / prices
- 5 / 5
- model
- tiered
- stability
- 100%
No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.
- domain age
- -
- registrar
- -
- hosting
- custom
- domain created
- ---
Identity facts, not a risk score.
- assessment volume 30d
- $0.03
- exact assessment volume 30d (USD)
- 0.032
- assessment recorded at (UTC)
- 2026-10-10T12:13:05.741Z
- buyers 30d
- 1
- settlements 30d
- 4
- measured since
- 2026-09-10 (start of our harvest window)
- last settlement
- 2026-09-10
- top buyer share
- 100% of 30d volume (address, not entity)
- top 3 buyers share
- -
- concentrated volume
- no
- trend 7d vs 30d
- 0.00x the 30d daily rate
- networks
- eip155:8453
- volume all-time
- $0.03
- settlements all-time
- 4
- median settlement 30d
- $0.01
- max settlement 30d
- $0.01
Assessment volume uses the latest 30d assessment. Over time sums daily address snapshots, rounded to cents and refreshed separately. The two sources can differ in timing, precision and shared-address attribution. Amounts use cents for comparison; known sub-cent values keep up to 12 significant digits. The exact stored assessment value is shown above.
Conservative undercount: only USDC settlements via facilitators we measure are counted. A measured floor, not an estimate.
Top buyer share lowers the on-chain traction part of the ranking score behind this page's verdict and /best, by up to half when one address holds all 30d volume. The Recommended and Highest volume sorts of the services list do not use it; they use the Concentrated volume rule instead.
- member since
- 2026-09-14
Recent checks
| Checked at (UTC) | Status | HTTP | Response | Endpoints |
|---|---|---|---|---|
| Offline | no response | 2000ms | 0 | |
| Offline | no response | 2000ms | 0 | |
| Offline | no response | 2000ms | 0 | |
| Offline | no response | 2000ms | 0 | |
| Offline | no response | 2000ms | 0 | |
| Offline | no response | 2000ms | 0 | |
| Offline | no response | 2001ms | 0 | |
| Offline | no response | 2000ms | 0 | |
| Offline | 405 | 204ms | 0 | |
| Offline | 405 | 160ms | 0 | |
| Offline | 405 | 84ms | 0 | |
| Offline | 405 | 73ms | 0 | |
| Offline | 405 | 131ms | 0 | |
| Offline | 405 | 36ms | 0 | |
| Offline | 405 | 179ms | 0 | |
| Offline | 405 | 36ms | 0 | |
| Offline | 405 | 36ms | 0 | |
| Offline | 405 | 42ms | 0 |
Changes0 in 30d
No changes recorded in the last 30 days.
Over time
- Volume 30d
- $0.03
- Uptime
- 26 of 26 completed days below 100%
More charts
Scores over time
09-11 to 10-10* UTC
09-11 to 10-10* UTC
Scores: one day per column, 09-11 to 10-10*, on the columns of Response time. Uptime held below 100% on some days in this window, including any partial day. Daily readings remain in the Uptime strip and Values. Pillar lines use their own low and high. Exact dated readings are available in each readout and in Values.
Each series spans only the dates it has data for. Every series is also served as JSON at /api, /scores, /volume and /buyers.
Values
* today so far, partial (UTC).
The uptime summary counts completed UTC days only. The strip, readouts and table retain today's partial reading.
Daily snapshot total, no volume data in the last 30d. The visible 30d total in Traction comes from the latest assessment. These sources can differ in their window, refresh time, cent rounding and shared-address attribution.
Daily address snapshots: 2026-09-11 to 2026-10-10 UTC; * today so far, partial (UTC). Daily snapshots store cents. A recorded $0.00 with settlements cannot distinguish exact zero from volume rounded away. Lost precision is unavailable here.
Settlement volume uses the stored USD valuation of tracked payments; it is distinct from token quantities. USD-pegged assets are valued at 1 USD per token in these rollups. The measured settlement floor does not cover all payments to this service.
Assessment history last recorded at . Each UTC day uses its last recorded run; missing readings stay unmeasured. Assessment history JSON · Measurement methodology.
| Day | Volume | Buyers | Settlements | Uptime | Response | Compliance | Price percentile | Site signals |
|---|---|---|---|---|---|---|---|---|
| 2026-09-14 | no data | no data | no data | 0% | no data | no data | p21 | 0/6 |
| 2026-09-15 | no data | no data | no data | 0% | no data | no data | p23 | 0/6 |
| 2026-09-16 | no data | no data | no data | 0% | no data | no data | p23 | 1/6 |
| 2026-09-17 | no data | no data | no data | 0% | no data | no data | p23 | 1/6 |
| 2026-09-18 | no data | no data | no data | 0% | no data | no data | p23 | 1/6 |
| 2026-09-19 | no data | no data | no data | 0% | no data | no data | p23 | 1/6 |
| 2026-09-20 | no data | no data | no data | 0% | no data | no data | p23 | 1/6 |
| 2026-09-21 | no data | no data | no data | 0% | no data | no data | p22 | 1/6 |
| 2026-09-22 | no data | no data | no data | 0% | no data | no data | p22 | 1/6 |
| 2026-09-23 | no data | no data | no data | 0% | no data | no data | p22 | 1/6 |
| 2026-09-24 | no data | no data | no data | 0% | no data | no data | p22 | 1/6 |
| 2026-09-25 | no data | no data | no data | 0% | no data | no data | p22 | 1/6 |
| 2026-09-26 | no data | no data | no data | 0% | no data | no data | p22 | 1/6 |
| 2026-09-27 | no data | no data | no data | 0% | no data | no data | p22 | 2/6 |
| 2026-09-28 | no data | no data | no data | 0% | no data | no data | p21 | 2/6 |
| 2026-09-29 | no data | no data | no data | 0% | no data | no data | p22 | 2/6 |
| 2026-09-30 | no data | no data | no data | 0% | no data | no data | p22 | 2/6 |
| 2026-10-01 | no data | no data | no data | 0% | no data | no data | p22 | 2/6 |
| 2026-10-02 | no data | no data | no data | 0% | no data | no data | p22 | 2/6 |
| 2026-10-03 | no data | no data | no data | 0% | no data | no data | p22 | 2/6 |
| 2026-10-04 | no data | no data | no data | 0% | no data | no data | p22 | 2/6 |
| 2026-10-05 | no data | no data | no data | 0% | no data | no data | p23 | 2/6 |
| 2026-10-06 | no data | no data | no data | 0% | no data | no data | p23 | 2/6 |
| 2026-10-07 | no data | no data | no data | 0% | no data | no data | p22 | 2/6 |
| 2026-10-08 | no data | no data | no data | 0% | no data | no data | p23 | 2/6 |
| 2026-10-09 | no data | no data | no data | 0% | no data | no data | p23 | 0/6 |
| 2026-10-10* | no data | no data | no data | 0% | no data | no data | p23 | 0/6 |
Alternatives in AI
5 of 183 other ranked services in AI, ordered by the same measured score.
Own this service?
Keep this listing accurate. Ownership is proven with a domain check and every change is reviewed by hand.
Update this listingEarn the verified tier: x402list pays a real call to this endpoint and, if it delivers, the service is delivery-verified. The fee covers the cost of the probe, not the badge; there is no refund if the call does not deliver. Agent and API only, no in-browser signing. See /api.
Verify this service ($0.25)Embed a badge
HTML
<a href="https://x402-list.com/services/ torquantis? utm_source=badge& utm_medium=referral& utm_campaign=embed"> <img src="https://x402-list.com/ badge/ torquantis.svg" alt="Torquantis listed on x402-list" height="28"> </a>
Markdown
[](https://x402-list.com/ services/ torquantis? utm_source=badge& utm_medium=referral& utm_campaign=embed)
HTML, live uptime variant
<a href="https://x402-list.com/services/ torquantis? utm_source=badge& utm_medium=referral& utm_campaign=embed"> <img src="https://x402-list.com/ badge/ torquantis.svg? data=uptime" alt="Torquantis uptime on x402-list" height="28"> </a>
Delisting
To request delisting, email info@x402-list.com or update your listing at /services/torquantis/update.