Checking payment availability…

X LAYER / AGENT TOOLS

Verify the evidence.
Call it from your agent.

Inspect a transaction, match an exact token transfer, and check public delivery bytes. Receive code-verified facts and an AI explanation grounded in those facts. 0.01 USDT per call through official OKX x402 payment.

Chain 196Official OKX x4020.01 USDT per call

Connect through MCP

Add this URL as a remote Streamable HTTP MCP server:

https://holonagentservice.lingoai.io/mcp

Tool: verify_xlayer_delivery. Your MCP client discovers the parameters and handles initialization. The server is stateless. Discovery is free. Tool calls require an x402-capable client to handle PAYMENT-REQUIRED and PAYMENT-SIGNATURE; ordinary MCP clients can discover the tool but cannot pay automatically.

Call the HTTP API

The same verification is available to OKX.AI A2MCP buyers and other HTTP clients:

curl -X POST https://holonagentservice.lingoai.io/verify \
  -H 'Content-Type: application/json' \
  -d '{"transactionHash":"0x1761a092116069e3e0e8e9352f3eba439b249e9b5e14898f4c196abeb0cd6b93"}'
ParameterChecks
transactionHash · requiredReceipt, execution status, block inclusion and observed confirmations on X Layer mainnet.
expectedPaymentExact ERC-20 event: token, sender, recipient and amountRaw. Supply all four; the amount is in base units.
allowanceExplicit token, owner and spender. Returns allowance at the end of the transaction block and current snapshot block; unavailable values remain unknown.
contractAddressExpected transaction recipient. Third-party business state is not inferred from generic logs.
jobIdEvent binding and current job state in the Holon mainnet canary escrow.
manifestCidHolon manifest and referenced document bytes, SHA-256, size and CID integrity. Supports CIDv1 raw SHA-256 blocks, up to 8 KiB for the manifest and 16 KiB for the document.
expectedDigestExpected Keccak-256 of manifest bytes; requires manifestCid. With jobId, the onchain deliverable digest is also checked.

Preview the payment challenge

The example is the project's published 0.10 USDC settlement. This preview requests the payment challenge. It does not sign or pay. Use an x402-capable agent to authorize a paid call.

Read the result

Inspect status (PASS, WARNING or FAIL), warnings, verificationStatus, verified, and each entry in checks. A completed HTTP request can return mismatch or not_found; neither is successful verification. Upstream outages return an error.

interpretation contains the AI summary, findings with evidence references, suggested next checks and limitations. deterministicInterpretation preserves the code-generated conclusion. AI text is advisory: it never changes the verdict, transaction facts or checks. Only structured public evidence is sent to the model; delivery document text and payment credentials are excluded. If the required AI explanation is unavailable, no new payment is settled.

Confirmations are observations, not a finality guarantee. Token logs do not establish an arbitrary token's economic value. File integrity checks establish byte consistency, not authorship or content quality. Without a job ID or trusted expected digest, IPFS integrity is checked independently of the transaction.

For the complete input schema and supported escrow address, open capabilities. Existing A2A report delivery is available through ASP #13847. No private-key custody or fund operations in the verifier. Not investment advice or a security audit.