Atinamos Verification
Core Principle You can pay to be tested. You cannot pay to be trusted.
Explore verification

Independent verification becomes transaction-grounded

Milestone occurred: 18 August 2026
Public milestone record published: 11 September 2026

What happened

Atinamos Verification moved beyond contract observation and preflight into a real paid verification run.

A verifier operating separately from the seller observed the x402 challenge, enforced bounded payment terms, used a dedicated Verification buyer wallet to pay 0.25 USDC for Atinamos Render Check, received the seller job, polled its asynchronous status, inspected the returned fulfilment evidence and persisted the transaction and result evidence.

A controlled broken-route case also established an important negative path: HTTP 404 before payment meant no payment and no fulfilment claim.

Why it mattered

This introduced the evidence boundary that still underpins the system:

seller claim
!= payment settlement
!= fulfilment
!= correctness
!= trust verdict

A verification run could succeed operationally while recording that the seller did not fulfil, and a verifier failure could be attributed separately from seller performance.

What it proved

This milestone supports that Atinamos could:

  • act as an independent buyer of a machine service;
  • observe and bind the live payment contract;
  • make a bounded real payment from a dedicated verifier wallet;
  • follow asynchronous fulfilment;
  • retain hashes and structured evidence;
  • persist successful and negative observations without converting them into a provider score.

What it did not prove

The target in this first paid verification was Atinamos-owned Render Check. It therefore did not yet establish that the same verifier model generalised to independently owned third-party services.

It also did not establish autonomous discovery or buyer selection.

This milestone immediately enabled the buyer-facing evidence API and the later buyer policy gate. Those are recorded separately because they changed who consumed the evidence, not just how it was generated.

Capability transition

observe a payment contract
→ make a bounded verifier purchase
→ observe fulfilment
→ persist transaction-grounded evidence

← Previous milestone · Next milestone: evidence-informed purchase →