77trust / 100

Trackrecord Timing

by ManyLives Track Records in Onchain & crypto

x402 APIPassing, checked 17 min ago

Proof that a book's calls for a period were locked before the period started: the Base network transaction, its block time read live from the chain, the period start, and the margin in seconds. Use it to confirm no result was recorded after the fact.

GET
https://api.manylives.me/paid/trackrecord/timing
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
398 ms
544 ms slowest 5%
Last check
Passed
17 min ago, next in 12 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

How to call it

GET https://api.manylives.me/paid/trackrecord/timing

Each call costs $0.01 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.

GET https://api.manylives.me/paid/trackrecord/timing?book=CRY-5m

Parameters

ParameterTypeRequiredDescription
bookstringYesbook id (required), e.g. CRY-5m
periodstringNooptional period label, or 'latest' (default)

Example response

The provider's example. We can't check it without paying.

{
  "block_time_onchain": "2026-10-09T05:03:41Z",
  "book": "CRY-5m",
  "period": "2026-10-09T05:05:00",
  "period_start": "2026-10-09T05:05:00Z",
  "root_in_calldata": true,
  "seconds_before_start": 79,
  "tx": "0x…"
}

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.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.manylives.me/paid/trackrecord/timing?book=CRY-5m'

# 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 - 'https://api.manylives.me/paid/trackrecord/timing?book=CRY-5m' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.manylives.me%2Fpaid%2Ftrackrecord%2Ftiming
const res = await pay("https://api.manylives.me/paid/trackrecord/timing?book=CRY-5m");
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://api.manylives.me/paid/trackrecord/timing?book=CRY-5m")
    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

WhenResultHTTPTimePrice
17 min agoPassed402492 ms$0.01
5 h agoPassed402441 ms$0.01
9 h agoPassed402570 ms$0.01
13 h agoPassed402398 ms$0.01
17 h agoPassed402544 ms$0.01
Show 10 older checks
22 h agoPassed402396 ms$0.01
26 h agoPassed402389 ms$0.01
30 h agoPassed402531 ms$0.01
33 h agoPassed402339 ms$0.01
37 h agoPassed402403 ms$0.01
41 h agoPassed402379 ms$0.01
45 h agoPassed402388 ms$0.01
2 days agoPassed402390 ms$0.01
2 days agoPassed402397 ms$0.01
2 days agoPassed402395 ms$0.01