Kilawatt Cloud
payment-ready until 2026-10-17
Multi-provider GPU orchestration platform.
Call it x402 v2
x402 v2
- Base URL
- https://www.kilawattcloud.dev
- Payment
- x402 v2, header channel
$ curl -i -X POST 'https://www.kilawattcloud.dev/api/public/x402/exec' 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 www.kilawattcloud.dev
Prices as captured in the 402 response: $0.54.
Example 402 response
Endpoints and prices
| Method | Path | Description | Price | Network | Asset | 402 channel | Captured |
|---|---|---|---|---|---|---|---|
| POST | / | No description | $0.54 | Base | USDC | header | since 09-14 |
Payment evidence
402 payload captured at . Check evidence JSON · Measurement methodology.
1 payload captured by the monitor.
192 lines, scroll inside
{
"error": "PAYMENT-SIGNATURE header is required",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xf441ad71d29502c33ef911de45aaec0060b34c66",
"amount": "540000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 600
}
],
"resource": {
"url": "https://www.kilawattcloud.dev/api/public/x402/exec",
"mimeType": "application/json",
"description": "Kilawatt GPU compute: 1x nvidia-h100 for 600s"
},
"extensions": {
"x402.discovery": {
"name": "Kilawatt Cloud GPU compute",
"method": "POST",
"openapi": "https://www.kilawattcloud.dev/api/public/x402/openapi.json",
"resource": "https://www.kilawattcloud.dev/api/public/x402/exec",
"description": "Pay-per-job GPU capacity with multi-provider failover, settled in USDC on Base. The request provisions capacity and does not accept code or commands.",
"inputSchema": {
"type": "object",
"properties": {
"gpu_type": {
"enum": [
"nvidia-b300",
"nvidia-b200",
"nvidia-h200",
"nvidia-h100",
"nvidia-a100",
"nvidia-l40s",
"nvidia-l40",
"nvidia-a40",
"nvidia-a10",
"nvidia-rtx-a6000",
"nvidia-rtx-a5000",
"nvidia-rtx-a4500",
"nvidia-rtx-a4000",
"nvidia-rtx-5090",
"nvidia-rtx-4090",
"nvidia-rtx-3090"
],
"type": "string",
"default": "nvidia-h100",
"maxLength": 64,
"minLength": 1,
"description": "GPU model to provision. Any other value returns HTTP 400 unknown_gpu_type with the list of valid values."
},
"card_count": {
"type": "integer",
"default": 1,
"maximum": 16,
"minimum": 1,
"description": "Number of GPUs in the job. Minimum 1. Maximum: 8 for H100, H200, A100, and L40S; 4 for B200; 16 for workstation-class cards. Other GPU classes use the server-enforced class limit."
},
"workload_type": {
"enum": [
"agent_exec",
"fine_tune",
"batch_inference"
],
"type": "string",
"default": "agent_exec",
"description": "Workload class dispatched through the Kilawatt gateway."
},
"routing_policy": {
"enum": [
"lowest_cost",
"lowest_latency",
"zero_quota"
],
"type": "string",
"default": "lowest_cost",
"description": "Provider selection policy across the failover chain."
},
"duration_seconds": {
"type": "number",
"default": 600,
"maximum": 86400,
"minimum": 60,
"description": "Requested runtime in seconds. Billing and pre-authorization use this value."
}
},
"description": "Only the listed fields affect the request. Other fields are ignored. There is no field for source code, commands, container images, or workload payloads.",
"additionalProperties": true
},
"outputSchema": {
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Kilawatt job identifier, normally the same value as job_id."
},
"ready": {
"type": "boolean"
},
"job_id": {
"type": [
"string",
"null"
],
"description": "Execution record identifier used by GET /api/public/v1/jobs/{job_id}."
},
"status": {
"type": "string",
"description": "provisioning when the node accepts the job."
},
"api_key": {
"type": "string",
"description": "The machine account's long-lived API key. Returned only in the wallet's first successful paid response because only its hash is stored; it cannot be recovered later."
},
"payment": {
"type": "object",
"properties": {
"payer": {
"type": "string"
},
"network": {
"type": "string"
},
"amount_usd": {
"type": "number",
"description": "Full signed amount settled on-chain and credited, expressed in whole cents."
},
"transaction_hash": {
"type": "string"
}
}
},
"gpu_type": {
"type": "string"
},
"provider": {
"type": "string"
},
"billed_usd": {
"type": "number",
"description": "Exact job charge from the credited balance. The current x402 pricing path rounds this charge up to whole cents."
},
"card_count": {
"type": "integer"
},
"instance_id": {
"type": "string"
},
"failover_hops": {
"type": "integer"
},
"health_status": {
"type": "string"
},
"pricing_basis": {
"type": "string"
},
"real_cost_usd": {
"type": "number"
},
"workload_type": {
"type": "string"
},
"routing_policy": {
"type": "string"
},
"sla_credit_usd": {
"type": "number"
},
"provisioned_gpu": {
"type": [
"string",
"null"
]
},
"health_monitoring": {
"type": "object"
},
"real_cost_precision": {
"type": "string"
}
}
}
}
},
"x402Version": 2
} Can I trust it score from our own monitoring
score from our own monitoring
#12 of 16 in Compute. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.
- Reliability
- 96.6% uptime since 09-14
- Compliance
- A 14/14 checks pass
- Price
- $0.38 p97 in Compute
- Risk
- clean no risk flag
- Traction
- $34.26 30d 4 buyers, top buyer 91% (address, not entity)
- Last change
- price changed 58m ago latest 10 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-10-10. 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, 96.6% uptime 30d, 7677ms response p95, x402 compliance 14 of 14, $0.38 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 Compute, 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 16 listings, this one among them: the same 16 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 ($34.26, 406 tx). Traction is a conservative undercount; first settlement seen 2026-09-12.
All measured facts
What it does
Multi-provider GPU orchestration platform. Routes AI/ML workloads across RunPod, Vast.ai, Lambda, and Hyperstack with automatic failover, per-second billing, and zero egress fees. Agents provision and pay for GPU compute via x402 in a single request.
Kilawatt Cloud is a listed x402 Compute 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 · Compute
- uptime · latest daily rollup
- 100%
- uptime 7d
- 95.4%
- uptime 30d
- 96.6%
- uptime 90d
- 96.6%
- response p95
- 7677ms
- avg response
- 5615ms
- total checks
- 2,312
Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.
- price (min)
- $0.38
- category percentile (min)
- p97 in Compute
- endpoints / prices
- 1 / 1
- model
- flat
- stability
- 0%
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
- $34.26
- exact assessment volume 30d (USD)
- 34.26
- assessment recorded at (UTC)
- 2026-10-10T12:13:01.897Z
- buyers 30d
- 4
- settlements 30d
- 406
- measured since
- 2026-09-12 (start of our harvest window)
- last settlement
- 2026-10-10
- top buyer share
- 91% of 30d volume (address, not entity)
- top 3 buyers share
- -
- concentrated volume
- -
- trend 7d vs 30d
- 2.22x the 30d daily rate
- networks
- eip155:8453
- volume all-time
- $34.26
- settlements all-time
- 406
- median settlement 30d
- $0.02
- max settlement 30d
- $3.40
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 |
|---|---|---|---|---|
| Online | 402 | 5898ms | 1 | |
| Online | 402 | 7344ms | 1 | |
| Online | 402 | 7204ms | 1 | |
| Online | 402 | 9326ms | 1 | |
| Online | 402 | 8776ms | 1 | |
| Online | 402 | 7846ms | 1 | |
| Online | 402 | 5955ms | 1 | |
| Online | 402 | 6823ms | 1 | |
| Online | 402 | 6365ms | 1 | |
| Online | 402 | 6325ms | 1 | |
| Online | 402 | 7543ms | 1 | |
| Online | 402 | 7100ms | 1 | |
| Online | 402 | 7004ms | 1 | |
| Online | 402 | 6282ms | 1 | |
| Online | 402 | 6703ms | 1 | |
| Online | 402 | 6125ms | 1 | |
| Online | 402 | 6419ms | 1 | |
| Online | 402 | 6706ms | 1 |
Changeslatest 10 in 30d
| Observed at (UTC) | Change | Evidence |
|---|---|---|
| price changed |
| |
| price changed |
| |
| price changed |
| |
| price changed |
| |
| price changed |
| |
| price changed |
| |
| price changed |
| |
| price changed |
| |
| price changed |
| |
| price changed |
|
Amounts are on-wire atomic units in the named asset.
Over time
- Volume 30d
- $34.26
- Uptime
- 13 of 28 completed days below 100%
More charts
09-11 to 10-10* UTC
Scores over time
09-11 to 10-10* UTC
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. 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, 30d: $34.26, peak $17.73 on 10-08. 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-12 | $0.08 | 1 | 2 | no data | no data | no data | no data | no data |
| 2026-09-13 | no data | no data | no data | no data | no data | no data | no data | no data |
| 2026-09-14 | $0.08 | 1 | 2 | 100% | 2634.67ms | 14/14 | p97 | 3/6 |
| 2026-09-15 | $0.72 | 1 | 18 | 100% | 2884.38ms | 14/14 | p97 | 3/6 |
| 2026-09-16 | $0.39 | 1 | 8 | 89.89% | 4529.06ms | 14/14 | p97 | 3/6 |
| 2026-09-17 | no data | no data | no data | 90% | 5587.62ms | 14/14 | p97 | 3/6 |
| 2026-09-18 | no data | no data | no data | 92.22% | 5085.90ms | 14/14 | p97 | 3/6 |
| 2026-09-19 | no data | no data | no data | 90% | 4694.94ms | 14/14 | p97 | 3/6 |
| 2026-09-20 | no data | no data | no data | 95.56% | 4657.15ms | 14/14 | p97 | 3/6 |
| 2026-09-21 | $0.19 | 1 | 10 | 95.56% | 4896.29ms | 14/14 | p97 | 3/6 |
| 2026-09-22 | no data | no data | no data | 95.56% | 4992.86ms | 14/14 | p97 | 3/6 |
| 2026-09-23 | no data | no data | no data | 98.89% | 5413.93ms | 14/14 | p97 | 3/6 |
| 2026-09-24 | no data | no data | no data | 100% | 4797.77ms | 14/14 | p97 | 3/6 |
| 2026-09-25 | $0.80 | 1 | 12 | 100% | 4939.87ms | 14/14 | p97 | 3/6 |
| 2026-09-26 | $0.10 | 1 | 10 | 100% | 5321.30ms | 14/14 | p97 | 3/6 |
| 2026-09-27 | $0.02 | 1 | 2 | 100% | 5350.06ms | 14/14 | p97 | 3/6 |
| 2026-09-28 | no data | no data | no data | 100% | 6308.82ms | 14/14 | p97 | 3/6 |
| 2026-09-29 | no data | no data | no data | 100% | 6371.42ms | 14/14 | p97 | 4/6 |
| 2026-09-30 | $1.64 | 1 | 4 | 100% | 6471.13ms | 14/14 | p97 | 4/6 |
| 2026-10-01 | no data | no data | no data | 100% | 6458.98ms | 14/14 | p97 | 4/6 |
| 2026-10-02 | $12.50 | 1 | 8 | 100% | 6612.38ms | 14/14 | p97 | 4/6 |
| 2026-10-03 | no data | no data | no data | 95.56% | 6778.08ms | 14/14 | p97 | 4/6 |
| 2026-10-04 | no data | no data | no data | 93.33% | 7261.05ms | 14/14 | p97 | 4/6 |
| 2026-10-05 | no data | no data | no data | 93.33% | 6685.86ms | 14/14 | p97 | 4/6 |
| 2026-10-06 | no data | no data | no data | 100% | 6356.14ms | 14/14 | p97 | 4/6 |
| 2026-10-07 | no data | no data | no data | 91.11% | 6234.72ms | 14/14 | p97 | 4/6 |
| 2026-10-08 | $17.73 | 1 | 329 | 92.22% | 5988.72ms | 14/14 | p97 | 4/6 |
| 2026-10-09 | no data | no data | no data | 100% | 6181.01ms | 14/14 | p97 | 4/6 |
| 2026-10-10* | $0.01 | 1 | 1 | 100% | 6128.61ms | 14/14 | p97 | 4/6 |
Alternatives in Compute
5 of 15 other ranked services in Compute, 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/ kilawatt-cloud? utm_source=badge& utm_medium=referral& utm_campaign=embed"> <img src="https://x402-list.com/ badge/ kilawatt-cloud.svg" alt="Kilawatt Cloud listed on x402-list" height="28"> </a>
Markdown
[](https://x402-list.com/ services/ kilawatt-cloud? utm_source=badge& utm_medium=referral& utm_campaign=embed)
HTML, live uptime variant
<a href="https://x402-list.com/services/ kilawatt-cloud? utm_source=badge& utm_medium=referral& utm_campaign=embed"> <img src="https://x402-list.com/ badge/ kilawatt-cloud.svg? data=uptime" alt="Kilawatt Cloud uptime on x402-list" height="28"> </a>
Delisting
To request delisting, email info@x402-list.com or update your listing at /services/kilawatt-cloud/update.