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

First paid verification of a third-party machine service

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

What happened

Atinamos Verification completed its first independent paid verification of a machine service that Atinamos did not own or control: x402Node JSON Repair.

The verifier observed the live HTTP 402 contract, enforced a 0.01 USDC recipe-level spend cap, selected Base from the available payment options, paid 0.006 USDC, received HTTP 200 fulfilment and evaluated four objective output assertions. All four assertions passed.

The Base transaction and canonical response SHA-256 were retained as part of the evidence record.

Why it mattered

The earlier transaction-grounded verifier proof had tested Atinamos-owned Render Check. This milestone showed that the model could cross an ownership boundary and inspect a genuinely external service.

It also introduced a recipe-driven direction rather than embedding one provider's logic into the verifier. That was essential if verification was ever going to scale beyond bespoke integrations.

What it proved

This record supports that Atinamos could:

  • independently discover the current executable contract of a third-party paid service;
  • cap spend before payment;
  • perform a real x402 purchase;
  • retain settlement and fulfilment evidence;
  • apply objective output assertions;
  • publish a scoped result without promoting one successful sample into permanent trust.

What it did not prove

One third-party service did not prove general verification across arbitrary machine services. Autonomous discovery and selection were also still separate open questions.

Primary record

External Paid Verification Proof — 22 August 2026 records the x402Node case in the public evidence/study system.

The retained technical record identifies the paid transaction as 0x9f49fa8a1ffd8c4331a5a1400a78f1bdce3488402957847dc18e1b26f2f44af2.

Capability transition

verify own service
→ verify independently owned service
→ objective assertions + bounded spend
→ reusable verification recipe direction

← Previous milestone · Next milestone: autonomous buyer Proof #3 →