An agent requests validation and names the Markovian validator address. The Markovian relayer watches for that request, resolves the provenance behind it against the public verifier, and answers on-chain. The two calls are shown below.
The ERC-8004 response is a score from 0 to 100. A 100 from Markovian means a provenance record was found and recorded in the log, not that the agent's work is correct. The tag set to provenance is the firewall that stops a 100 from being read as a correctness claim. Any consumer can filter by that tag and read the score for what it is.
External stamps carry a SHA-256 data hash and a Merkle root, and nothing more. They establish that data was committed at a point in time. They make no claim about whether the data is right.
Markovian runs two agents on the ERC-8004 registry on Base mainnet. Agent 59270 sells a signal at a paid x402 endpoint. Agent 59285 buys it. Both are operated by Markovian, and that is disclosed in each registration file. Every settlement between them is stamped as a leaf in the public log, which seven independent witnesses cosign.
The registry proves which agent made a claim. The witnessed log proves the claim was recorded and cannot be silently rewritten. Neither proves the claim is correct.
The canonical Validation Registry has no mainnet deployment yet, so the validation loop ran against the reference interface on the Sepolia testnet. A real Markovian stamp travelled through the full envelope. Every artifact below is independently checkable on Etherscan and against the public verifier.
The canonical ERC-8004 Validation Registry is not yet deployed to mainnet. That portion of the standard remains under active development with the TEE community. Markovian is proven today against the reference Validation Registry interface on Sepolia, and the mainnet path follows when the registry ships.
What the Sepolia record does today is attest a provenance hash: a 100 means the record exists, not that the outcome is correct. The stronger form, deterministic-replay validation (tag="markovian.resolve.v1"), has the validator recompute the outcome from public data rather than attest that a record exists, so any consumer reaches the same verdict independently. That method is now deployed and live on Base Sepolia: a proof-enforcing validator writes a verdict only when its proof verifies on-chain, and a tampered verdict reverts. See it execute, or read the contracts, conformance vectors, and Go and Python verifiers in erc8004-resolution-validator.
On mainnet today, the live route is the registration above: two agents on the ERC-8004 registry on Base, trust model witnessed-log, with every settlement between them stamped into the cosigned public log. When the canonical Validation Registry ships, the validator described on this page is the mainnet path.
The Etherscan links above read the response straight from the chain. The public verifier returns the provenance record behind the stamp, with no account and no dependency on this site.