Domain Host Trust
by Domain Host Trust Record in Security & trust
Observe public DNS, TLS and baseline response headers through HTTPS HEAD / on port443; no full-path scan or global trust assessment.
https://foundry-api-production-95ae.up.railway.app/v1/domain-host-trust- Price
- $0.01
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 384 ms
- 475 ms slowest 5%
- Last check
- Passed
- 2 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://foundry-api-production-95ae.up.railway.app/v1/domain-host-trust
Each call costs $0.01 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://foundry-api-production-95ae.up.railway.app/v1/domain-host-trust
content-type: application/json
{
"hostname": "example.org",
"schema_version": "1.0"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
client_request_id | string | No | |
hostname | string | Yes | Public DNS hostname only; URLs, ports, paths and IP literals are rejected. |
schema_version | any | Yes |
Example response
The provider's example. We can't check it without paying.
Example response, 55 lines
{
"client_request_id": null,
"commercial": {
"pricing_version": "domain-host-trust-v1"
},
"decision": {
"reasons": [
"OBSERVATION_UNAVAILABLE"
],
"state": "UNKNOWN"
},
"dns_resolution": {
"addresses": [],
"dnssec_state": "UNKNOWN_NOT_OBSERVED"
},
"freshness": {
"max_age_seconds": 300,
"observed_at": "2026-09-27T12:00:00.000Z",
"state": "FRESH"
},
"hostname": "example.org",
"http_security_headers": {
"present": {},
"state": "UNKNOWN"
},
"metering": {
"billable": false,
"quantity": 0,
"unit": "domain_host_trust_record"
},
"observation_scope": {
"full_paths_checked": false,
"global_trust_assessed": false,
"method": "HEAD",
"path": "/",
"port": 443,
"protocol": "HTTPS",
"redirects_followed": false
},
"observed_at": "2026-09-27T12:00:00.000Z",
"product_id": "foundry.domain-host-trust-record.v1",
"provenance": [],
"request_id": "req_domain_synthetic_contract",
"result_state": "UNKNOWN",
"rights": {
"state": "GREEN_SELF_OBSERVED_PROTOCOL_FACTS",
"third_party_reputation_feed": false,
"whois_bulk_content": false
},
"run_id": "run_domain_synthetic_contract",
"schema_version": "1.0",
"tls_certificate_validity": {
"state": "UNKNOWN"
}
}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.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://foundry-api-production-95ae.up.railway.app/v1/domain-host-trust' \
-H 'content-type: application/json' \
--data-raw '{"hostname":"example.org","schema_version":"1.0"}'
# 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://foundry-api-production-95ae.up.railway.app/v1/domain-host-trust' \
-H 'content-type: application/json' \
--data-raw '{"hostname":"example.org","schema_version":"1.0"}' \
| 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Ffoundry-api-production-95ae.up.railway.app%2Fv1%2Fdomain-host-trust&method=POST
const res = await pay("https://foundry-api-production-95ae.up.railway.app/v1/domain-host-trust", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"hostname": "example.org",
"schema_version": "1.0"
}),
});
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://foundry-api-production-95ae.up.railway.app/v1/domain-host-trust",
json={
"hostname": "example.org",
"schema_version": "1.0",
},
)
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 |
|---|---|---|---|---|
| 2 h ago | Passed | 402 | 385 ms | $0.01 |
| 9 h ago | Passed | 402 | 377 ms | $0.01 |
| 15 h ago | Passed | 402 | 373 ms | $0.01 |
| 20 h ago | Passed | 402 | 471 ms | $0.01 |
| 25 h ago | Passed | 402 | 376 ms | $0.01 |
Show 10 older checks
| 31 h ago | Passed | 402 | 398 ms | $0.01 |
| 40 h ago | Passed | 402 | 236 ms | $0.01 |
| 2 days ago | Passed | 402 | 378 ms | $0.01 |
| 2 days ago | Passed | 402 | 397 ms | $0.01 |
| 3 days ago | Passed | 402 | 365 ms | $0.01 |
| 3 days ago | Passed | 402 | 368 ms | $0.01 |
| 4 days ago | Passed | 402 | 433 ms | $0.01 |
| 4 days ago | Passed | 402 | 359 ms | $0.01 |
| 4 days ago | Passed | 402 | 392 ms | $0.01 |
| 5 days ago | Passed | 402 | 361 ms | $0.01 |