Agent Council
payment-ready 2026-11-04, probe currently failing
A judgement call instead of a lookup.
Call it x402 v2
x402 v2
- Base URL
- https://council.cyberwarex.com
- Payment
- x402 v2, header channel
$ curl -i 'https://council.cyberwarex.com/council' An unpaid request returns HTTP 402 with the payment terms. Sign a payment authorization, then retry with the PAYMENT-SIGNATURE header.
Endpoints 2 paid routes on council.cyberwarex.com
Prices as captured in the 402 response: median $0.02 across the 2 endpoints.
Example 402 response
Endpoints and prices
| Method | Path | Description | Price | Network | Asset | 402 channel | Captured |
|---|---|---|---|---|---|---|---|
| GET | / | Put one question to a panel of 3 different AI models and get a single verdict back. Each model answers independently, then a chair synthesizes: verdict, confidence, the points they all agreed on, the dissent, and what would flip the answer. Use it for judgement calls where one model's opinion is not enough: is this safe, is this worth it, which option. No account, no API key, one USDC micropayment per call. | $0.01 | Base | USDC | header | since 10-04 |
| GET | / | The deep council: 4 different AI models, two rounds. Each seat answers, then sees the other seats' positions and revises - so you get a verdict that survived cross-examination, with changed_after_debate on each seat and the dissent that held. For decisions where being wrong is expensive. | $0.03 | Base | USDC | header | since 10-04 |
Payment evidence
402 payload captured at . Check evidence JSON · Measurement methodology.
First of 2 payloads captured by the monitor.
199 lines, scroll inside
{
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x058D0Cc5CC97e61e8A9f38D6d6365bce525921B2",
"amount": "10000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
],
"resource": {
"url": "https://council.cyberwarex.com/council",
"tags": [
"council",
"reasoning",
"decision",
"multi-model",
"verdict"
],
"iconUrl": "https://cyberwarex.com/assets/icon.png",
"mimeType": "application/json",
"description": "Put one question to a panel of 3 different AI models and get a single verdict back. Each model answers independently, then a chair synthesizes: verdict, confidence, the points they all agreed on, the dissent, and what would flip the answer. Use it for judgement calls where one model's opinion is not enough: is this safe, is this worth it, which option. No account, no API key, one USDC micropayment per call.",
"serviceName": "Agent Council"
},
"extensions": {
"bazaar": {
"info": {
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"q": "Is a 3-day-old Base lending pool paying 42% APY with an unverified proxy admin safe to deposit into?"
}
},
"output": {
"type": "json",
"example": {
"mode": "quick",
"panel": [
{
"seat": "analyst",
"model": "deepseek-v4.1-flash",
"risks": [
"Slower ceiling"
],
"reasons": [
"No demand signal yet"
],
"position": "Single product first.",
"confidence": 85
}
],
"seats": 3,
"rounds": 1,
"dissent": [
{
"seat": "builder",
"point": "A thin marketplace is cheaper to test than it looks"
}
],
"verdict": "Ship the single product first. A marketplace needs both sides and the team has neither supply nor demand locked in.",
"question": "Should we ship the marketplace or the single product first?",
"consensus": [
"A marketplace needs liquidity on two sides before it is useful"
],
"watch_for": [
"An anchor supplier committing first",
"Distribution that already exists"
],
"confidence": 84,
"elapsed_sec": 6.9,
"seats_invited": 4
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method"
],
"properties": {
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"GET",
"HEAD",
"DELETE"
],
"type": "string"
},
"queryParams": {
"type": "object",
"required": [
"q"
],
"properties": {
"q": {
"type": "string",
"maxLength": 2000,
"description": "The question to put to the council (required, max 2000 chars). A decision question works best: include the options and the constraints."
}
},
"additionalProperties": false
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object",
"properties": {
"mode": {
"enum": [
"quick",
"deep"
],
"type": "string"
},
"panel": {
"type": "array",
"items": {
"type": "object"
},
"description": "each seat's position, confidence and the model that argued it."
},
"seats": {
"type": "integer"
},
"rounds": {
"type": "integer"
},
"dissent": {
"type": "array",
"items": {
"type": "object"
},
"description": "real disagreements, as {seat, point} - empty when the panel agreed."
},
"verdict": {
"type": "string",
"description": "the council's answer, synthesized by the chair."
},
"question": {
"type": "string"
},
"consensus": {
"type": "array",
"items": {
"type": "string"
}
},
"watch_for": {
"type": "array",
"items": {
"type": "string"
},
"description": "what would flip the verdict."
},
"confidence": {
"type": "integer",
"description": "0-100, lower when the seats disagreed."
},
"elapsed_sec": {
"type": "number"
}
}
}
}
}
}
}
}
},
"x402Version": 2
} Other captured 402 responses (1)
Captured payload 2 of 2
{
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x058D0Cc5CC97e61e8A9f38D6d6365bce525921B2",
"amount": "30000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
],
"resource": {
"url": "https://council.cyberwarex.com/council-deep",
"tags": [
"council",
"debate",
"decision",
"multi-model",
"verdict"
],
"iconUrl": "https://cyberwarex.com/assets/icon.png",
"mimeType": "application/json",
"description": "The deep council: 4 different AI models, two rounds. Each seat answers, then sees the other seats' positions and revises - so you get a verdict that survived cross-examination, with changed_after_debate on each seat and the dissent that held. For decisions where being wrong is expensive.",
"serviceName": "Agent Council"
},
"extensions": {
"bazaar": {
"info": {
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"q": "We have 16 paid API endpoints and almost no revenue. Build a 17th or spend the week on distribution?"
}
},
"output": {
"type": "json",
"example": {
"mode": "deep",
"panel": [
{
"seat": "analyst",
"model": "deepseek-v4.1-flash",
"risks": [
"Slower ceiling"
],
"reasons": [
"No demand signal yet"
],
"position": "Single product first.",
"confidence": 85
}
],
"seats": 4,
"rounds": 2,
"dissent": [
{
"seat": "builder",
"point": "A thin marketplace is cheaper to test than it looks"
}
],
"verdict": "Ship the single product first. A marketplace needs both sides and the team has neither supply nor demand locked in.",
"question": "Should we ship the marketplace or the single product first?",
"consensus": [
"A marketplace needs liquidity on two sides before it is useful"
],
"watch_for": [
"An anchor supplier committing first",
"Distribution that already exists"
],
"confidence": 84,
"elapsed_sec": 6.9,
"seats_invited": 4
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method"
],
"properties": {
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"GET",
"HEAD",
"DELETE"
],
"type": "string"
},
"queryParams": {
"type": "object",
"required": [
"q"
],
"properties": {
"q": {
"type": "string",
"maxLength": 2000,
"description": "The question to put to the council (required, max 2000 chars). A decision question works best: include the options and the constraints."
}
},
"additionalProperties": false
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object",
"properties": {
"mode": {
"enum": [
"quick",
"deep"
],
"type": "string"
},
"panel": {
"type": "array",
"items": {
"type": "object"
},
"description": "each seat's position, confidence and the model that argued it."
},
"seats": {
"type": "integer"
},
"rounds": {
"type": "integer"
},
"dissent": {
"type": "array",
"items": {
"type": "object"
},
"description": "real disagreements, as {seat, point} - empty when the panel agreed."
},
"verdict": {
"type": "string",
"description": "the council's answer, synthesized by the chair."
},
"question": {
"type": "string"
},
"consensus": {
"type": "array",
"items": {
"type": "string"
}
},
"watch_for": {
"type": "array",
"items": {
"type": "string"
},
"description": "what would flip the verdict."
},
"confidence": {
"type": "integer",
"description": "0-100, lower when the seats disagreed."
},
"elapsed_sec": {
"type": "number"
}
}
}
}
}
}
}
}
},
"x402Version": 2
}Can I trust it score from our own monitoring
score from our own monitoring
#211 of 228 in AI. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.
- Reliability
- 94.7% uptime 30d
- Compliance
- A 14/14 checks pass, stale (probe failing)
- Price
- $0.01 to $0.03 p53 in AI
- Risk
- clean no risk flag
- Traction
- $0.00 30d 0 buyers
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-10-04. Last up 2026-11-04.
── 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, 94.7% uptime 30d, 843ms response p95, x402 compliance 14 of 14, $0.01 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 228 listings, this one among them: the same 228 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.
Traction is a conservative undercount.
All measured facts
What it does
A judgement call instead of a lookup. Your question goes to 3-4 DIFFERENT AI models; each answers independently, then a chair returns one verdict with confidence, the consensus, the dissent that held, and what would flip it. Quick $0.01, deep $0.03 (2 rounds of cross-examination). Pay-per-call via x402 (USDC on Base). Free first call.
Agent Council 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-10-21 to 2026-11-19 UTC. Daily monitoring and settlement rollups do not expose their computation time; a bucket date is not an update timestamp. 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
- -
- uptime 7d
- 0%
- uptime 30d
- 94.7%
- uptime 90d
- 97.1%
- response p95
- 843ms
- avg response
- 372ms
- total checks
- 2,750
Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.
- price (min)
- $0.01
- price (max)
- $0.03
- category percentile (min)
- p53 in AI
- category percentile (max)
- p42 in AI
- endpoints / prices
- 2 / 2
- 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
- 90d
- registrar
- HOSTINGER operations, UAB
- hosting
- custom
- domain created
- 2026-08-17
Identity facts, not a risk score.
- assessment volume 30d
- $0.00
- exact assessment volume 30d (USD)
- 0
- assessment recorded at (UTC)
- 2026-11-19T00:04:27.091Z
- buyers 30d
- 0
- settlements 30d
- 0
- measured since
- --- (start of our harvest window)
- last settlement
- ---
- top buyer share
- -
- top 3 buyers share
- -
- concentrated volume
- no
- trend 7d vs 30d
- -
- networks
- eip155:8453
- volume all-time
- $0
- settlements all-time
- 0
- median settlement 30d
- -
- max settlement 30d
- -
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-10-04
Recent checks
| Checked at (UTC) | Status | HTTP | Response | Endpoints |
|---|---|---|---|---|
| Offline | 410 | 1498ms | 0 | |
| Offline | 410 | 272ms | 0 | |
| Offline | 410 | 222ms | 0 | |
| Offline | 410 | 857ms | 0 | |
| Offline | 410 | 328ms | 0 | |
| Offline | 410 | 298ms | 0 | |
| Offline | 410 | 272ms | 0 | |
| Offline | 410 | 370ms | 0 | |
| Offline | 410 | 232ms | 0 | |
| Offline | 410 | 260ms | 0 | |
| Offline | 410 | 228ms | 0 | |
| Offline | 410 | 1107ms | 0 | |
| Offline | 410 | 247ms | 0 | |
| Offline | 410 | 587ms | 0 | |
| Offline | 410 | 244ms | 0 | |
| Offline | 410 | 194ms | 0 | |
| Offline | 410 | 240ms | 0 | |
| Offline | 410 | 284ms | 0 |
Changes0 in 30d
No changes recorded in the last 30 days.
Over time
- Volume 30d
- $0.00
- Uptime
- 16 of 29 completed days below 100%
More charts
10-21 to 11-19* UTC
Scores over time
10-21 to 11-19* UTC
10-21 to 11-19* UTC
10-21 to 11-19* UTC
Scores: one day per column, 10-21 to 11-19*, 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, /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-10-21 to 2026-11-19 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-10-21 | no data | no data | no data | 100% | 347.88ms | 14/14 | p52 | 4/6 |
| 2026-10-22 | no data | no data | no data | 100% | 240.76ms | 14/14 | p52 | 4/6 |
| 2026-10-23 | no data | no data | no data | 100% | 253.97ms | 14/14 | p52 | 4/6 |
| 2026-10-24 | no data | no data | no data | 100% | 230.31ms | 14/14 | p52 | 4/6 |
| 2026-10-25 | no data | no data | no data | 100% | 197.70ms | 14/14 | p52 | 4/6 |
| 2026-10-26 | no data | no data | no data | 100% | 215.29ms | 14/14 | p52 | 4/6 |
| 2026-10-27 | no data | no data | no data | 100% | 217.83ms | 14/14 | p52 | 0/6 |
| 2026-10-28 | no data | no data | no data | 100% | 249.11ms | 14/14 | p53 | 0/6 |
| 2026-10-29 | no data | no data | no data | 100% | 387.59ms | 14/14 | p53 | 6/6 |
| 2026-10-30 | no data | no data | no data | 100% | 445.44ms | 14/14 | p53 | 6/6 |
| 2026-10-31 | no data | no data | no data | 100% | 383.93ms | 14/14 | p53 | 6/6 |
| 2026-11-01 | no data | no data | no data | 100% | 417.28ms | 14/14 | p53 | 6/6 |
| 2026-11-02 | no data | no data | no data | 98.86% | 416.21ms | 14/14 | p53 | 6/6 |
| 2026-11-03 | no data | no data | no data | 100% | 440.60ms | 14/14 | p53 | 6/6 |
| 2026-11-04 | no data | no data | no data | 61.29% | 403.79ms | 14/14 | p53 | 3/6 |
| 2026-11-05 | no data | no data | no data | 0% | no data | 14/14 | p53 | 3/6 |
| 2026-11-06 | no data | no data | no data | 0% | no data | 14/14 | p53 | 3/6 |
| 2026-11-07 | no data | no data | no data | 0% | no data | 14/14 | p53 | 3/6 |
| 2026-11-08 | no data | no data | no data | 0% | no data | 14/14 | p53 | 3/6 |
| 2026-11-09 | no data | no data | no data | 0% | no data | 14/14 | p53 | 3/6 |
| 2026-11-10 | no data | no data | no data | 0% | no data | 14/14 | p53 | 3/6 |
| 2026-11-11 | no data | no data | no data | 0% | no data | 14/14 | p53 | 3/6 |
| 2026-11-12 | no data | no data | no data | 0% | no data | 14/14 | p53 | 3/6 |
| 2026-11-13 | no data | no data | no data | 0% | no data | 14/14 | p53 | 3/6 |
| 2026-11-14 | no data | no data | no data | 0% | no data | 14/14 | p53 | 3/6 |
| 2026-11-15 | no data | no data | no data | 0% | no data | 14/14 | p53 | 3/6 |
| 2026-11-16 | no data | no data | no data | 0% | no data | 14/14 | p54 | 3/6 |
| 2026-11-17 | no data | no data | no data | 0% | no data | 14/14 | p53 | 3/6 |
| 2026-11-18 | no data | no data | no data | 0% | no data | 14/14 | p53 | 3/6 |
| 2026-11-19* | no data | no data | no data | no data | no data | 14/14 | p53 | 3/6 |
Alternatives in AI
5 of 227 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/ agent-council? utm_source=badge& utm_medium=referral& utm_campaign=embed"> <img src="https://x402-list.com/ badge/ agent-council.svg" alt="Agent Council listed on x402-list" height="28"> </a>
Markdown
[](https://x402-list.com/ services/ agent-council? utm_source=badge& utm_medium=referral& utm_campaign=embed)
HTML, live uptime variant
<a href="https://x402-list.com/services/ agent-council? utm_source=badge& utm_medium=referral& utm_campaign=embed"> <img src="https://x402-list.com/ badge/ agent-council.svg? data=uptime" alt="Agent Council uptime on x402-list" height="28"> </a>
Delisting
To request delisting, email info@x402-list.com with the service name, slug, or URL. Removal is free and does not require proof of ownership. See all free email requests.