x402 List Submit a serviceSubmit
Menu

RedRobotRouges IA Inference

payment-readyonline

payment-ready until 2026-10-17

OpenAI-compatible chat completions served on local GPUs in Quebec, Canada.

redrobotrouges.ca ↗

Call it x402 v2

x402 v2

Base URL
https://redrobotrouges.ca
Payment
x402 v2, header channel
$ curl -i -X POST 'https://redrobotrouges.ca/x402/v1/chat/completions'

An unpaid request returns HTTP 402 with the payment terms. Sign a payment authorization, then retry with the PAYMENT-SIGNATURE header.

Endpoints 1 paid route on redrobotrouges.ca

POST/x402/v1/chat/completionsBase$0.001since 09-28

Prices as captured in the 402 response: $0.001, unchanged since first capture.

Example 402 response

Endpoints and prices

Current paid endpoints; minimum quoted prices in USD where available; first capture dates in UTC
MethodPathDescriptionPriceNetworkAsset402 channelCaptured
POST/x402/v1/chat/completionsNo description$0.001BaseUSDCheadersince 09-28

Payment evidence

402 payload captured at . Check evidence JSON · Measurement methodology.

1 payload captured by the monitor.

129 lines, scroll inside

{
  "error": "PAYMENT-SIGNATURE header is required",
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "extra": {
        "name": "USD Coin",
        "version": "2"
      },
      "payTo": "0xeC45fc2379075361990B8AE344f6e22C2466ae5A",
      "amount": "1000",
      "scheme": "exact",
      "network": "eip155:8453",
      "maxTimeoutSeconds": 60
    }
  ],
  "resource": {
    "url": "https://redrobotrouges.ca/x402/v1/chat/completions",
    "tags": [
      "llm",
      "ai",
      "chat",
      "openai-compatible",
      "quebec"
    ],
    "iconUrl": "https://redrobotrouges.ca/x402/icon.png",
    "mimeType": "application/json",
    "description": "OpenAI-compatible chat completions (local GPU, Quebec/CA)",
    "serviceName": "RedRobotRouges IA"
  },
  "extensions": {
    "bazaar": {
      "info": {
        "input": {
          "body": {
            "model": "qwen3.6:35b",
            "stream": false,
            "messages": [
              {
                "role": "user",
                "content": "Bonjour"
              }
            ]
          },
          "type": "http",
          "method": "POST",
          "bodyType": "json"
        },
        "output": {
          "type": "json",
          "example": {
            "id": "chatcmpl-…",
            "model": "qwen3.6:35b",
            "object": "chat.completion",
            "choices": [
              {
                "index": 0,
                "message": {
                  "role": "assistant",
                  "content": "Bonjour !"
                },
                "finish_reason": "stop"
              }
            ]
          }
        }
      },
      "schema": {
        "type": "object",
        "$schema": "https://json-schema.org/draft/2020-12/schema",
        "required": [
          "input"
        ],
        "properties": {
          "input": {
            "type": "object",
            "required": [
              "type",
              "method",
              "bodyType",
              "body"
            ],
            "properties": {
              "body": {
                "type": "object"
              },
              "type": {
                "type": "string",
                "const": "http"
              },
              "method": {
                "enum": [
                  "POST",
                  "PUT",
                  "PATCH"
                ],
                "type": "string"
              },
              "bodyType": {
                "enum": [
                  "json",
                  "form-data",
                  "text"
                ],
                "type": "string"
              }
            },
            "additionalProperties": false
          },
          "output": {
            "type": "object",
            "required": [
              "type"
            ],
            "properties": {
              "type": {
                "type": "string"
              },
              "example": {
                "type": "object"
              }
            }
          }
        }
      }
    }
  },
  "x402Version": 2
}

Can I trust it score from our own monitoring

score from our own monitoring

85/100 Solid

#60 of 184 in AI. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.

Reliability
99.2% uptime since 09-25
Compliance
A 14/14 checks pass
Price
$0.001 p12 in AI
Risk
clean no risk flag
Traction
$0.002 30d 2 buyers, top buyer 50% (address, not entity)
Last change
schema changed 12d ago 1 in 30d
14/14 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 2026-09-28. Last up 2026-10-10.

── 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 online, 99.2% uptime 30d, 1779ms response p95, x402 compliance 14 of 14, $0.001 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 payAI ($0.002, 2 tx). Traction is a conservative undercount; first settlement seen 2026-09-23.

All measured facts

What it does

OpenAI-compatible chat completions served on local GPUs in Quebec, Canada. Pay $0.001 USDC on Base per call via x402; no API key or signup. Canadian data residency (Loi 25), French and English. Contact: [email protected]

RedRobotRouges IA Inference 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
100%
uptime 7d
99.8%
uptime 30d
99.2%
uptime 90d
99.2%
response p95
1779ms
avg response
1321ms
total checks
1,307

Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.

price (min)
$0.001
category percentile (min)
p12 in AI
endpoints / prices
1 / 1
model
flat
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.002
exact assessment volume 30d (USD)
0.002
assessment recorded at (UTC)
2026-10-10T13:53:02.190Z
buyers 30d
2
settlements 30d
2
measured since
2026-09-23 (start of our harvest window)
last settlement
2026-10-05
top buyer share
50% of 30d volume (address, not entity)
top 3 buyers share
-
concentrated volume
no
trend 7d vs 30d
2.14x the 30d daily rate
networks
eip155:8453
volume all-time
$0
settlements all-time
2
median settlement 30d
$0.001
max settlement 30d
$0.001

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-25
Recent checks
Latest 18 unpaid HTTP checks, newest first; response times in milliseconds, observation times in UTC
Checked at (UTC)StatusHTTPResponseEndpoints
Online402838ms1
Online4021091ms1
Online402867ms1
Online402516ms1
Online402414ms1
Online4021886ms1
Online402455ms1
Online402785ms1
Online402465ms1
Online402754ms1
Online402591ms1
Online402924ms1
Online402690ms1
Online402521ms1
Online402702ms1
Online402488ms1
Online402493ms1
Online402786ms1

Changes1 in 30d

Latest 1 recorded changes, up to 10 in the last 30 days; newest first; observation times in UTC
Observed at (UTC)ChangeEvidence
schema changed

endpoint removed GET /x402/v1/chat/completions

endpoint added POST /x402/v1/chat/completions

schema removed GET /x402/v1/chat/completions exact eip155:8453 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 USDC 2 60 {"name":"USD Coin","version":"2"}

schema added POST /x402/v1/chat/completions exact eip155:8453 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 USDC 2 60 {"name":"USD Coin","version":"2"}

all changes

Over time

On-chain volume daily snapshots, USD 30d: $0.002
volume no data in the payload
Distinct buyers per dayDistinct buyers per day
Uptime 2 of 17 completed days below 100%
uptime below 100%, to scale
Volume 30d
$0.002
Uptime
2 of 17 completed days below 100%
Daily on-chain settlement volume in US dollars, 2026-09-11 to 2026-10-10; 16 days have no data in the payload; distinct buyers per day
More charts
Response time daily average, ms min 890ms, avg 1295ms, max 1929ms

09-11 to 10-10* UTC

Scores over time

x402 compliance low 14/14, high 14/14

09-11 to 10-10* UTC

Price percentile in AI own low to high; exact values below

09-11 to 10-10* UTC

Site signals present (of 6) own low to high; exact values below

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. The checklist grew from 11 to 14 checks on 2026-07-28, before this window. 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/v1/services/redrobotrouges-ia-inference/price, /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, 30d: $0.00 recorded in daily snapshots. 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. † marks a recorded $0.00 with settlements.

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.

Daily values, 2026-09-23 to 2026-10-10: address settlement volume in USD, distinct buyer and settlement counts, uptime percent, average response milliseconds, compliance passed/total, price percentile 0-100, site signals out of 6; UTC dates
DayVolumeBuyersSettlementsUptimeResponseCompliancePrice percentileSite signals
2026-09-23$0.00 recorded†11no datano datano datano datano data
2026-09-24no datano datano datano datano datano datano datano data
2026-09-25no datano datano data100%986.71ms14/14p115/6
2026-09-26no datano datano data100%1705.98ms14/14p115/6
2026-09-27no datano datano data100%1659.66ms14/14p115/6
2026-09-28no datano datano data100%1929.09ms14/14p115/6
2026-09-29no datano datano data100%1593.80ms14/14p115/6
2026-09-30no datano datano data88.61%1623.39ms14/14p115/6
2026-10-01no datano datano data100%1235.34ms14/14p115/6
2026-10-02no datano datano data100%1361.43ms14/14p115/6
2026-10-03no datano datano data100%1278.68ms14/14p115/6
2026-10-04no datano datano data100%1260.96ms14/14p115/6
2026-10-05$0.00 recorded†11100%1151.58ms14/14p125/6
2026-10-06no datano datano data100%890.08ms14/14p125/6
2026-10-07no datano datano data100%928.28ms14/14p125/6
2026-10-08no datano datano data98.89%904.82ms14/14p125/6
2026-10-09no datano datano data100%1206.79ms14/14p125/6
2026-10-10*no datano datano data100%1006.61ms14/14p125/6

Alternatives in AI

Cluster Protocol strong 99/100 100% up 30d $55.7k 30d
x402engine strong 94/100 100% up 30d $46.02 30d
NetIntel strong 94/100 100% up 30d $20.88 30d
Agent402.tools strong 93/100 99.7% up 30d $202.84 30d
GlianaAI strong 93/100 100% up 30d $36.57 30d

5 of 183 other ranked services in AI, ordered by the same measured score.

see the whole category

Own this service?

Keep this listing accurate. Ownership is proven with a domain check and every change is reviewed by hand.

Update this listing

Earn 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/redrobotrouges-ia-inference?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/redrobotrouges-ia-inference.svg" alt="RedRobotRouges IA Inference listed on x402-list" height="28">
</a>

Markdown

[![RedRobotRouges IA Inference on x402-list](https://x402-list.com/badge/redrobotrouges-ia-inference.svg)](https://x402-list.com/services/redrobotrouges-ia-inference?utm_source=badge&utm_medium=referral&utm_campaign=embed)

HTML, live uptime variant

<a href="https://x402-list.com/services/redrobotrouges-ia-inference?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/redrobotrouges-ia-inference.svg?data=uptime" alt="RedRobotRouges IA Inference uptime on x402-list" height="28">
</a>
Delisting

To request delisting, email info@x402-list.com or update your listing at /services/redrobotrouges-ia-inference/update.