Lattice Check
by quantum.halowerk.com in Onchain & crypto
Uses lattice dimension, log2 determinant and an assumed root-Hermite factor to estimate Gaussian-heuristic and reduced-basis vector lengths in log2 units. It does not execute lattice reduction, validate an LWE instance or provide a cryptographic security level.
https://quantum.halowerk.com/v1/lattice-check- Price
- $0.003
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 126 ms
- 177 ms slowest 5%
- Last check
- Passed
- 3 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://quantum.halowerk.com/v1/lattice-check
Each call costs $0.003 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://quantum.halowerk.com/v1/lattice-check
content-type: application/json
{
"dimension": 512,
"log2_determinant": 4096,
"root_hermite_factor": 1.005,
"target_norm_log2": 8.2
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
dimension | integer | Yes | |
log2_determinant | number | Yes | |
root_hermite_factor | number | Yes | |
target_norm_log2 | number | Yes |
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.003.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://quantum.halowerk.com/v1/lattice-check' \
-H 'content-type: application/json' \
--data-raw '{"dimension":512,"log2_determinant":4096,"root_hermite_factor":1.005,"target_norm_log2":8.2}'
# 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://quantum.halowerk.com/v1/lattice-check' \
-H 'content-type: application/json' \
--data-raw '{"dimension":512,"log2_determinant":4096,"root_hermite_factor":1.005,"target_norm_log2":8.2}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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.003 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.003" });
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.003 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fquantum.halowerk.com%2Fv1%2Flattice-check&method=POST
const res = await pay("https://quantum.halowerk.com/v1/lattice-check", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"dimension": 512,
"log2_determinant": 4096,
"root_hermite_factor": 1.005,
"target_norm_log2": 8.2
}),
});
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.003 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.003"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://quantum.halowerk.com/v1/lattice-check",
json={
"dimension": 512,
"log2_determinant": 4096,
"root_hermite_factor": 1.005,
"target_norm_log2": 8.2,
},
)
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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 h ago | Passed | 402 | 150 ms | $0.003 |
| 13 h ago | Passed | 402 | 106 ms | $0.003 |
| 17 h ago | Passed | 402 | 104 ms | $0.003 |
| 22 h ago | Passed | 402 | 94 ms | $0.003 |
| 26 h ago | Passed | 402 | 103 ms | $0.003 |
Show 10 older checks
| 30 h ago | Passed | 402 | 69 ms | $0.003 |
| 34 h ago | Passed | 402 | 29 ms | $0.003 |
| 39 h ago | Passed | 402 | 33 ms | $0.003 |
| 43 h ago | Passed | 402 | 99 ms | $0.003 |
| 47 h ago | Passed | 402 | 126 ms | $0.003 |
| 2 days ago | Passed | 402 | 135 ms | $0.003 |
| 2 days ago | Passed | 402 | 128 ms | $0.003 |
| 2 days ago | Passed | 402 | 127 ms | $0.003 |
| 3 days ago | Passed | 402 | 177 ms | $0.003 |
| 3 days ago | Passed | 402 | 127 ms | $0.003 |