32trust / 100

Mac Parse

by Identifier Validators in Documents & files

x402 APIFailing, checked 25 h ago

Parse a MAC address in any common notation: canonical forms, OUI, unicast or multicast, universal or local.

GET
https://id-validators.x402tookit.com/mac-parse
Price
$0.02
per call in USDC
Uptime
50.0%
last 30 days
Response time
505 ms
569 ms slowest 5%
Last check
Failed
25 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 25 h ago: Expected HTTP 402, got 530

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

How to call it

GET https://id-validators.x402tookit.com/mac-parse

Each call costs $0.02 in USDC on Polygon, 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://id-validators.x402tookit.com/mac-parse?id=00-1A-2B-3C-4D-5E

Parameters

ParameterTypeRequiredDescription
idstringYesMAC address, any separator

Example response

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

{
  "administration": "universal",
  "asOf": "2026-10-11T04:20:52.362Z",
  "bare": "001a2b3c4d5e",
  "broadcast": false,
  "cast": "unicast",
  "cisco": "001a.2b3c.4d5e",
  "colon": "00:1A:2B:3C:4D:5E",
  "degraded": false,
  "disclaimer": "Screening signal computed from the named public source. Not financial, legal or investment advice; provided as is. Verify at the source before acting.",
  "hyphen": "00-1A-2B-3C-4D-5E",
  "notChecked": [
    "vendor name (the OUI is returned, not looked up)",
    "whether the address is in use"
  ],
  "oui": "00:1A:2B",
  "reasons": [],
  "source": "computed locally",
  "summary": "00:1A:2B:3C:4D:5E: unicast, globally unique (vendor assigned).",
  "verdict": "VALID"
}

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 'https://id-validators.x402tookit.com/mac-parse?id=00-1A-2B-3C-4D-5E'

# 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://id-validators.x402tookit.com/mac-parse?id=00-1A-2B-3C-4D-5E' \
  | 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.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%2Fid-validators.x402tookit.com%2Fmac-parse
const res = await pay("https://id-validators.x402tookit.com/mac-parse?id=00-1A-2B-3C-4D-5E");
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.get("https://id-validators.x402tookit.com/mac-parse?id=00-1A-2B-3C-4D-5E")
    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
25 h agoExpected HTTP 402, got 530530128 ms-
2 days agoExpected HTTP 402, got 530530139 ms-
3 days agoExpected HTTP 402, got 53053092 ms-
5 days agoExpected HTTP 402, got 53053088 ms-
5 days agoExpected HTTP 402, got 530530116 ms-
Show 9 older checks
5 days agoExpected HTTP 402, got 530530215 ms-
5 days agoExpected HTTP 402, got 530530169 ms-
5 days agoPassed402505 ms$0.02
6 days agoPassed402514 ms$0.02
6 days agoPassed402564 ms$0.02
6 days agoPassed402569 ms$0.02
6 days agoPassed402496 ms$0.02
6 days agoPassed402499 ms$0.02
7 days agoPassed402491 ms$0.02