75trust / 100

Hotp

by HOTP (counter-based) in Developer tools

x402 APIPassing, checked 1 h ago

Generate an RFC 4226 counter-based HMAC one-time password from a base32 secret and counter. Configurable digits (6–10, default 6) and algorithm (SHA1/SHA256/SHA512, default SHA1). An invalid base32 secret is a clean 400.

POST
https://otp.openverbs.com/v1/hotp
Price
$0.004
per call in USDC
Uptime
100%
last 30 days
Response time
570 ms
628 ms slowest 5%
Last check
Passed
1 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://otp.openverbs.com/v1/hotp

Each call costs $0.004 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://otp.openverbs.com/v1/hotp
content-type: application/json

{
  "algorithm": "SHA1",
  "counter": 1,
  "digits": 6,
  "secret": "example"
}

Parameters

ParameterTypeRequiredDescription
algorithmstringNoHMAC algorithm. Default SHA1. One of: SHA1, SHA256, SHA512.
counterintegerYesThe HOTP counter value.
digitsintegerNoNumber of code digits. Default 6.
secretstringYesBase32-encoded shared secret.

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://otp.openverbs.com/v1/hotp' \
  -H 'content-type: application/json' \
  --data-raw '{"algorithm":"SHA1","counter":1,"digits":6,"secret":"example"}'

# 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://otp.openverbs.com/v1/hotp' \
  -H 'content-type: application/json' \
  --data-raw '{"algorithm":"SHA1","counter":1,"digits":6,"secret":"example"}' \
  | 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.004 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.004" });
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.004 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fotp.openverbs.com%2Fv1%2Fhotp&method=POST
const res = await pay("https://otp.openverbs.com/v1/hotp", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "algorithm": "SHA1",
    "counter": 1,
    "digits": 6,
    "secret": "example"
  }),
});
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.004 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.004"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://otp.openverbs.com/v1/hotp",
        json={
            "algorithm": "SHA1",
            "counter": 1,
            "digits": 6,
            "secret": "example",
        },
    )
    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
1 h agoPassed402624 ms$0.004
6 h agoPassed402558 ms$0.004
11 h agoPassed402565 ms$0.004
16 h agoPassed402614 ms$0.004
20 h agoPassed402632 ms$0.004
Show 10 older checks
25 h agoPassed402587 ms$0.004
29 h agoPassed402628 ms$0.004
34 h agoPassed402593 ms$0.004
38 h agoPassed402599 ms$0.004
42 h agoPassed402589 ms$0.004
46 h agoPassed402559 ms$0.004
2 days agoPassed402589 ms$0.004
2 days agoPassed402609 ms$0.004
2 days agoPassed402584 ms$0.004
3 days agoPassed402566 ms$0.004