Does the domain carry a twilio domain-verification TXT record? Reads the apex TXT records (Cloudflare DoH) and reports whether the twilio ownership token is present and the token value (truncated). A present token usually means the company uses twilio's product; absence means not verified there. $0.01 per lookup.
Security x402 offerings
Browse indexable security x402 offerings, including provider, method, and service details.
4139 indexable offerings in this category.
Offerings
Page 72 of 173Does the domain carry a workplace domain-verification TXT record? Reads the apex TXT records (Cloudflare DoH) and reports whether the workplace ownership token is present and the token value (truncated). A present token usually means the company uses workplace's product; absence means not verified there. $0.01 per lookup.
Change watch for has workplace domain verification: runs the check, compares it with the result from your previous call for the same domain (kept 90 days) and returns the current answer, changed true/false, the fields that changed with before/after values, and when it was last seen. Schedule it to be alerted when this changes. $0.02 per check.
Does the domain carry a zoom domain-verification TXT record? Reads the apex TXT records (Cloudflare DoH) and reports whether the zoom ownership token is present and the token value (truncated). A present token usually means the company uses zoom's product; absence means not verified there. $0.01 per lookup.
Cryptographic hash of a text string - sha256 (default), sha512, sha1 or md5 - returned as hex and base64. Use it for content fingerprints, integrity checks and deterministic ids; pure computation, instant.
One endpoint for hashing and encoding: sha256, sha512, sha3, keccak256, md5, sha1, blake2, ripemd160, crc32, all-hashes-at-once, HMAC, base64/base64url, hex, URL and base58 encode/decode, JWT decode (with expiry check) and UUID v4/v5. Input as text, hex or base64.
Compute cryptographic digests and HMACs deterministically: MD5, SHA-1, SHA-256, SHA-384, SHA-512, output as hex, base64, or base64url. Add a "key" for HMAC. Built for checksums, content addressing, and signature verification. Inputs are hashed and discarded. POST a JSON body like: {"text":"hello world","algorithm":"sha256","encoding":"hex"}
Hash generator: compute a cryptographic digest of supplied data: SHA-256, SHA-384, SHA-512, SHA-1, SHA3-256, SHA3-512, Keccak-256, BLAKE2b-256 and BLAKE2b-512, plus HMAC with any of them. Input is UTF-8 text, base64 or hex bytes; output is hex, base64, base64url or base32. Returns the digest, the byte length of the input, and the exact algorithm identifier used.
Compute an MD5, SHA-1, SHA-256 or SHA-512 hex digest of text.
Compute an HMAC (MD5, SHA-1, SHA-256 or SHA-512) of text with a given key.
Give this API any text or binary data and it returns its fingerprint under whichever hash algorithms you choose - SHA-256, SHA-512, MD5, BLAKE2, CRC32 and more. It also signs data with a secret key (…
SHA-1 digest of the given text as base64: computed with WebCrypto, nothing stored. Also returns the byte length and the digest size. Integrity checks, cache keys, content addressing. $0.01 per call.
SHA-1 digest of the given text as base64url: computed with WebCrypto, nothing stored. Also returns the byte length and the digest size. Integrity checks, cache keys, content addressing. $0.01 per call.
SHA-1 digest of the given text as hex: computed with WebCrypto, nothing stored. Also returns the byte length and the digest size. Integrity checks, cache keys, content addressing. $0.01 per call.
SHA-256 digest of the given text as base64: computed with WebCrypto, nothing stored. Also returns the byte length and the digest size. Integrity checks, cache keys, content addressing. $0.01 per call.
SHA-256 digest of the given text as base64url: computed with WebCrypto, nothing stored. Also returns the byte length and the digest size. Integrity checks, cache keys, content addressing. $0.01 per call.
SHA-256 digest of the given text as hex: computed with WebCrypto, nothing stored. Also returns the byte length and the digest size. Integrity checks, cache keys, content addressing. $0.01 per call.
SHA-384 digest of the given text as base64: computed with WebCrypto, nothing stored. Also returns the byte length and the digest size. Integrity checks, cache keys, content addressing. $0.01 per call.
SHA-384 digest of the given text as base64url: computed with WebCrypto, nothing stored. Also returns the byte length and the digest size. Integrity checks, cache keys, content addressing. $0.01 per call.
SHA-384 digest of the given text as hex: computed with WebCrypto, nothing stored. Also returns the byte length and the digest size. Integrity checks, cache keys, content addressing. $0.01 per call.
SHA-512 digest of the given text as base64: computed with WebCrypto, nothing stored. Also returns the byte length and the digest size. Integrity checks, cache keys, content addressing. $0.01 per call.
SHA-512 digest of the given text as base64url: computed with WebCrypto, nothing stored. Also returns the byte length and the digest size. Integrity checks, cache keys, content addressing. $0.01 per call.
SHA-512 digest of the given text as hex: computed with WebCrypto, nothing stored. Also returns the byte length and the digest size. Integrity checks, cache keys, content addressing. $0.01 per call.
Compute a cryptographic digest (SHA-2, SHA-3, BLAKE2, and legacy SHA-1/MD5/RIPEMD-160) of some data. The input may be utf8/hex/base64/base64url and the digest is returned as hex/base64/base64url.
