Space Ticket
by Flow in Onchain & crypto
Gigabyte Space — ask-the-cast ticket. Pay $0.50 USDC on Base and put one written question into the live Space speaker queue: when the cast calls your ticket, you come up as a speaker and your question is answered on air, by name. One ticket buys one question. House rules: no shilling without a graded record, claims carry numbers — never product, always results. Listening is free; the ticket buys the question, not a verdict.
https://flow-kg4x.vercel.app/api/space/ticket- Price
- $0.5
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 453 ms
- 453 ms slowest 5%
- Last check
- Passed
- 2 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://flow-kg4x.vercel.app/api/space/ticket
Each call costs $0.5 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://flow-kg4x.vercel.app/api/space/ticket
content-type: application/json
{
"handle": "yourhandle",
"name": "Your Name",
"question": "What does the verdict score actually measure?"
}Example response
The provider's example. We can't check it without paying.
{
"ticket": {
"id": "SP-0001",
"position": 1,
"state": "queued"
}
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.5.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://flow-kg4x.vercel.app/api/space/ticket' \
-H 'content-type: application/json' \
--data-raw '{"handle":"yourhandle","name":"Your Name","question":"What does the verdict score actually measure?"}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://flow-kg4x.vercel.app/api/space/ticket' \
-H 'content-type: application/json' \
--data-raw '{"handle":"yourhandle","name":"Your Name","question":"What does the verdict score actually measure?"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.5 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.5" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.5 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fflow-kg4x.vercel.app%2Fapi%2Fspace%2Fticket&method=POST
const res = await pay("https://flow-kg4x.vercel.app/api/space/ticket", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"handle": "yourhandle",
"name": "Your Name",
"question": "What does the verdict score actually measure?"
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.5 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.5"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://flow-kg4x.vercel.app/api/space/ticket",
json={
"handle": "yourhandle",
"name": "Your Name",
"question": "What does the verdict score actually measure?",
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Passed | 402 | 453 ms | $0.5 |