77trust / 100

Parse

by Parse timecode in Documents & files

x402 APIPassing, checked 3 h ago

Parse an SMPTE timecode (HH:MM:SS:FF, or HH:MM:SS;FF for drop-frame) at a given frame rate into its components, total frame count and real-time seconds. Drop-frame is auto-detected from a ';' separator unless dropFrame is set. Out-of-range or non-existent drop-frame values are a clean 400.

POST https://timecode.openverbs.com/v1/parse

Last 30 days

All checks passedSome failedAll failedNot checked
Uptime
100%
Response time
566 ms typical, 597 ms slowest 5%
Last check
3 h ago
Next check
any minute now

How to call it

POST https://timecode.openverbs.com/v1/parse

Each call costs $0.002 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://timecode.openverbs.com/v1/parse
content-type: application/json

{
  "dropFrame": false,
  "frameRate": 24,
  "timecode": "01:00:00:00"
}

Parameters

ParameterTypeRequiredDescription
dropFramebooleanNoForce drop-frame counting (29.97/59.94 only). Default: auto-detect from separator.
frameRatenumberYesFrame rate, e.g. 24, 25, 29.97, 30, 59.94, 60. One of: 24, 25, 30, 48, 50, 60, 23.976, 29.97, 47.952, 59.94.
timecodestringYesTimecode, e.g. 01:00:00:00 or 00:01:00;02.

Example response

The listing has no example response.

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://timecode.openverbs.com/v1/parse' \
  -H 'content-type: application/json' \
  --data-raw '{"dropFrame":false,"frameRate":24,"timecode":"01:00:00:00"}'

# 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://timecode.openverbs.com/v1/parse' \
  -H 'content-type: application/json' \
  --data-raw '{"dropFrame":false,"frameRate":24,"timecode":"01:00:00:00"}' \
  | 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.002 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.002" });
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.002 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Ftimecode.openverbs.com%2Fv1%2Fparse&method=POST
const res = await pay("https://timecode.openverbs.com/v1/parse", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "dropFrame": false,
    "frameRate": 24,
    "timecode": "01:00:00:00"
  }),
});
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.002 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.002"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://timecode.openverbs.com/v1/parse",
        json={
            "dropFrame": False,
            "frameRate": 24,
            "timecode": "01:00:00:00",
        },
    )
    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
3 h agoPassed402577 ms$0.002
7 h agoPassed402521 ms$0.002
11 h agoPassed402616 ms$0.002
15 h agoPassed402549 ms$0.002
19 h agoPassed402577 ms$0.002
23 h agoPassed402557 ms$0.002
26 h agoPassed402561 ms$0.002
30 h agoPassed402567 ms$0.002
33 h agoPassed402597 ms$0.002
37 h agoPassed402558 ms$0.002
40 h agoPassed402575 ms$0.002
44 h agoPassed402582 ms$0.002
2 days agoPassed402576 ms$0.002
2 days agoPassed402563 ms$0.002
2 days agoPassed402575 ms$0.002