Market Ticker
by HubVibe in Markets & finance
Crypto ticker / bid and ask: live best bid, best ask, last price and volume for one Coinbase product from Coinbase's Exchange data host, an independent second source to market.quote. Input: product_id such as BTC-USD.
POST https://hubvibe-io.com/work/market/ticker
Last 30 days
Status and outage history · Atom feed
- Uptime
- 100%
- Response time
- 373 ms typical, 454 ms slowest 5%
- Last check
- 2 h ago
- Next check
- any minute now
How to call it
POST https://hubvibe-io.com/work/market/ticker
Each call costs $0.02 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://hubvibe-io.com/work/market/ticker
content-type: application/json
{
"product_id": "BTC-USD"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
language | string | No | |
product_id | string | Yes |
Example response
The provider's example. We can't check it without paying.
Example response, 31 lines
{
"price_usd": 0.02,
"provenance": {
"attempts": 1,
"elapsed_ms": 660,
"providers_used": [
"coinbase-exchange"
],
"steps": [
{
"ms": 640,
"ok": true,
"provider": "coinbase-exchange",
"step": "ticker"
}
]
},
"receipt_id": "rcpt_9f1c2b3a4d5e6f70",
"receipt_url": "/work/receipts/rcpt_9f1c2b3a4d5e6f70",
"result": {
"ask": "97232.80",
"bid": "97230.10",
"price": "97231.45",
"product_id": "BTC-USD",
"source": "coinbase-exchange",
"time": "2026-09-22T04:10:12.345Z",
"volume": "14231.9"
},
"status": "ok",
"worker": "market.ticker"
}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.02.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://hubvibe-io.com/work/market/ticker' \
-H 'content-type: application/json' \
--data-raw '{"product_id":"BTC-USD"}'
# 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://hubvibe-io.com/work/market/ticker' \
-H 'content-type: application/json' \
--data-raw '{"product_id":"BTC-USD"}' \
| 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.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fhubvibe-io.com%2Fwork%2Fmarket%2Fticker&method=POST
const res = await pay("https://hubvibe-io.com/work/market/ticker", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"product_id": "BTC-USD"
}),
});
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.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://hubvibe-io.com/work/market/ticker",
json={
"product_id": "BTC-USD",
},
)
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 | 433 ms | $0.02 |
| 6 h ago | Passed | 402 | 358 ms | $0.02 |
| 10 h ago | Passed | 402 | 116 ms | $0.02 |
| 13 h ago | Passed | 402 | 441 ms | $0.02 |
| 17 h ago | Passed | 402 | 407 ms | $0.02 |
| 21 h ago | Passed | 402 | 151 ms | $0.02 |
| 25 h ago | Passed | 402 | 429 ms | $0.02 |
| 28 h ago | Passed | 402 | 454 ms | $0.02 |
| 32 h ago | Passed | 402 | 355 ms | $0.02 |
| 35 h ago | Passed | 402 | 472 ms | $0.02 |
| 39 h ago | Passed | 402 | 144 ms | $0.02 |
| 43 h ago | Passed | 402 | 373 ms | $0.02 |
| 46 h ago | Passed | 402 | 125 ms | $0.02 |
| 2 days ago | Passed | 402 | 394 ms | $0.02 |
| 2 days ago | Passed | 402 | 356 ms | $0.02 |