Back to Browse
u-kiyo GPU Block Purchase
x402
u-kiyo GPU Block Purchase is a paid API for AI agents from pay.u-kiyo.ai, paid per call via x402, $5/call, status unknown (last checked 2026-10-29).
Purchase a prepaid GPU compute block without prior signup using x402 or MPP payment, returning an access token for bounded interactive GPU execution.
Price / call$5
Success—
StatusUnknown
How this service works
Purchase a prepaid GPU block without prior signup. Use for bounded interactive compute; standard x402 or MPP payment and a recovery public key are required.
Output
A JSON object containing the provisioning state (e.g. 'PROVISIONING'), a purchase ID (SHA-256 based), and a purchase-scoped access token for interacting with the allocated GPU block.
Example use cases
One-off ML inference without an account
“Buy me a 5-minute GPU block on u-kiyo right now using my Base wallet — I want to run a quick PyTorch inference script, keep output under 256KB, and don't spend more than 800 minor units. Here's my P-256 recovery public key coordinates.”
Agent-orchestrated GPU job in a pipeline
“As part of this automation, provision a gpu-block on u-kiyo via the Solana payment method for up to 120 seconds, execute the ffmpeg transcoding command I'm passing, cap output at 1MB, and hand me back the access token so I can poll results.”
Campaign compute burst with cost cap
“Spin up a u-kiyo GPU block tagged as a campaign job, run this image batch-processing command for at most 600 seconds, use Base payment, set max price to 5000 minor units, and give me the purchase ID when it's provisioning.”
Technical details
Endpoint
POSThttps://pay.u-kiyo.ai/api/machine/gpu-blocks?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need a single bounded GPU compute session on-demand without any account registration, and you can pay via x402 or MPP (Base, Solana, or Tempo). It is especially suited for agentic pipelines that need verifiable GPU execution with a crypto-native payment flow and a recovery key for key management, where the compute duration and output size must be strictly bounded.
Side effects
- Payment rejected or insufficient funds — x402 or MPP payment fails, returning a payment-required error
- Invalid recovery key format — EC P-256 key coordinates malformed or wrong length
- Terms or privacy acceptance not provided or hash mismatch — request rejected with validation error
- Duration or output byte limits out of allowed range — 400 validation error
- Offer ID not found or expired — UUID references unavailable offer
- Max price too low to cover actual cost — provisioning refused
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| kind | string | |
| method | string | |
| source | string | |
| command | string | |
| offerId | string | |
| requestId | string | |
| storageGb | number | |
| recoveryKey | object | |
| maxPriceMinor | integer | |
| maxOutputBytes | integer | |
| durationSeconds | integer | |
| termsAcceptance | object | |
| privacyAcceptance | object |
Output
Schema · Response
{
"type": "json",
"example": {
"state": "PROVISIONING",
"purchaseId": "sha256",
"accessToken": "purchase-scoped"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"