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

Render Check becomes a live paid machine service

Milestone reached by: 16 August 2026
Public milestone record published: 11 September 2026

What happened

The local Browser / Render Check capability was turned into a real machine-service seller surface. During this phase Atinamos exposed Render Check through an HTTP-native x402 payment flow, appeared in Coinbase/x402 Bazaar discovery data, and operated a paid provider offering through Virtuals Agent Commerce Protocol.

The Virtuals offering atinamos_render_check was priced at 0.25 USDC with a five-minute SLA and machine-readable input/output definitions. A real ACP job completed and escrow was released.

The x402 route established the same underlying commercial shape on the open web: a machine could encounter a payment requirement, supply payment and obtain a job/result path.

Why it mattered

This was the first point where Atinamos was not merely asking whether agents might buy services. It was operating a service that could actually participate as a seller in machine commerce.

The milestone also exposed an important distinction that shaped later work: being listed and payable is not the same as being independently evidenced or trusted.

What it proved

This milestone supports that:

  • Atinamos could operate as a paid provider inside the tested ACP flow;
  • Render Check could be exposed through a machine-payable x402 HTTP contract;
  • machine-readable service metadata could participate in external discovery surfaces;
  • real paid service execution could complete and return machine-readable results.

What it did not prove

It did not establish:

  • neutral autonomous selection of Atinamos by an unrelated buyer;
  • independent verification of service fulfilment;
  • broad market demand;
  • permanent availability or reliability;
  • that marketplace listing alone should influence a buyer's trust decision.

The multi-protocol experiments are summarised in Can One AI Agent Autonomously Discover, Pay and Buy From Another?.

Capability transition

local machine service
→ public machine contract
→ payment requirement
→ paid provider operation

← Previous milestone · Next milestone: the trust gap becomes explicit →