ToolVet
75trust / 100

Integration Device

by api.aventtech.com in Other

x402 APIPassing, checked 2 h ago

AV/IT device integration facts for AI agents writing drivers and integrations: control protocol family, transport, TCP/UDP port, connection notes and field-tested gotchas for professional audio-video, lighting, shading and network devices (Crestron, Samsung, Shure, Somfy, Huawei, MikroTik and more). Curated first-hand by working systems integrators.

GET
https://api.aventtech.com/integration/device
Price
$0.25
per call in USDC
Uptime
100%
last 30 days
Response time
364 ms
576 ms slowest 5%
Last check
Passed
2 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

GET https://api.aventtech.com/integration/device

Each call costs $0.25 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.aventtech.com/integration/device?make=samsung&model=commercial-display-mdc

Parameters

ParameterTypeRequiredDescription
makestringYesManufacturer, lowercase (e.g. samsung, shure, somfy)
modelstringNoDevice/family slug (e.g. commercial-display-mdc, p300-intellimix). Omit to list available entries for the make.

Example response

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

{
  "make": "samsung",
  "model": "commercial-display-mdc",
  "notes": [
    "Poll input state after power-on before sending input select",
    "Debounce command sends; displays reject rapid sequential writes"
  ],
  "port": 1515,
  "protocol": "Samsung MDC",
  "transport": "TCP"
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.aventtech.com/integration/device?make=samsung&model=commercial-display-mdc'

# 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.aventtech.com/integration/device?make=samsung&model=commercial-display-mdc' \
  | 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.25 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.25" });
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.25 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.aventtech.com%2Fintegration%2Fdevice
const res = await pay("https://api.aventtech.com/integration/device?make=samsung&model=commercial-display-mdc");
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.25 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.25"})
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.aventtech.com/integration/device?make=samsung&model=commercial-display-mdc")
    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
2 h agoPassed402267 ms$0.25
5 h agoPassed402322 ms$0.25
8 h agoPassed402274 ms$0.25
12 h agoPassed402509 ms$0.25
17 h agoPassed402415 ms$0.25
Show 10 older checks
23 h agoPassed402459 ms$0.25
28 h agoPassed402228 ms$0.25
33 h agoPassed402277 ms$0.25
38 h agoPassed402302 ms$0.25
43 h agoPassed402314 ms$0.25
2 days agoPassed402360 ms$0.25
2 days agoPassed402339 ms$0.25
2 days agoPassed402282 ms$0.25
3 days agoPassed402380 ms$0.25
3 days agoPassed402396 ms$0.25