Buyer-controlled x402 recipe

Build a public website and domain evidence pack

Collect publisher-asserted page metadata, then combine public DNS, TLS, RDAP, and focused mail-authentication records for the same site. Results are time-specific configuration evidence, not an identity, ownership, delivery, or safety verdict.

3separately authorized steps
$0.027maximum listed total · USDC
eip155:8453Base network
1
$0.002 USDC · separate authorization

Metadata extraction

Extract canonical, social, heading, feed, and privacy-safe publisher-asserted Organization metadata.

POSThttps://apiacre.com/v1/web/metadata

Input template

{
  "url": "$publicWebsiteUrl"
}
Use this result

Review redirect and content-hash provenance. Treat Organization fields as publisher assertions rather than verified identity evidence.

2
$0.02 USDC · separate authorization

Domain intelligence

Collect bounded DNS, verified TLS, RDAP, DNSSEC, SPF, and DMARC evidence.

POSThttps://apiacre.com/v1/web/domain-intelligence

Input template

{
  "url": "$publicWebsiteUrl"
}
Use this result

Use result.data.domain for the mail-policy step and review signals as time-specific technical evidence, not proof of ownership or safety.

3
$0.005 USDC · separate authorization

Email authentication posture

Inspect MX, SPF, DMARC, MTA-STS, TLS-RPT, BIMI, and any buyer-known DKIM selectors.

POSThttps://apiacre.com/v1/web/email-auth

Input template

{
  "domain": "$step2.result.data.domain",
  "dkim_selectors": []
}
Use this result

Review findings and record hashes as DNS configuration evidence. An empty DKIM list means no selectors were tested; the result does not prove delivery, sender identity, or message authenticity.

You stay in control. Each step is an independent API call. Inspect its HTTP 402 challenge, authorize no more than the displayed price, verify the result, and continue only when the output is suitable. The listed total is not a bundle charge.