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

First External Commercial Purchase of an Atinamos Service

Status

CONFIRMED EXTERNAL COMMERCIAL PURCHASE — 28 August 2026.

On 28 August 2026, Atinamos observed an unrelated external client complete a real x402 purchase of Atinamos JSON Repair.

The client paid 0.005 USDC on Base mainnet. Coinbase x402 verification succeeded, settlement succeeded, and the paid Atinamos service returned HTTP 200.

This establishes external commercial use. It does not, by itself, prove that the purchasing client was an independently autonomous AI agent.

What happened

The retained operational evidence records the following sequence in UTC:

16:17:11.481  external client POST /agent/json-repair → 402 Payment Required
16:17:12.429  Coinbase CDP x402 /verify → 200 OK
16:17:13.610  Coinbase CDP x402 /settle → 200 OK
16:17:13.850  external client POST /agent/json-repair → 200 OK

The corresponding Base transaction succeeded seconds later:

Network: Base mainnet (eip155:8453)
Asset: USDC
Amount: 0.005 USDC
Transaction: 0x00482f136e90f01053699dd6c48b8c0e6e7f0b3598510c83654a1b77a562316b
Block: 50572244

The public record deliberately redacts the external source IP and omits Atinamos payment-recipient account details.

Why Atinamos classifies this as external commercial use

The event was checked against the documented controlled Atinamos buyer and test flows.

The payer associated with the on-chain transfer did not match the documented Atinamos experimental buyer wallets reviewed during the investigation, and the event was not identified as one of the known controlled purchase tests.

The server-side sequence also shows the expected progression of a successful x402 commercial request:

payment required
→ payment supplied
→ payment verified
→ settlement accepted
→ paid service delivered

The narrow conclusion supported by the evidence is therefore:

An external client purchased and consumed an Atinamos paid machine service.

The client had inspected other paid services first

Approximately 11 minutes before the successful purchase, the same external source probed several Atinamos paid routes and received HTTP 402 responses, including:

  • JSON Repair;
  • Technical SEO Crawl;
  • Buyer Check.

It later returned to JSON Repair, supplied a valid x402 payment and received the paid result.

That behaviour is consistent with a machine client inspecting commercial service options before paying for one. It is not sufficient evidence to identify the client as an autonomous AI agent or to reconstruct its decision logic.

Why this matters to the Atinamos research

Earlier on the same day, Atinamos completed Proof #3 — A Bounded Autonomous Buyer With External Discovery.

Proof #3 demonstrated the buyer side under controlled Atinamos operation:

external discovery
→ evidence lookup
→ buyer policy
→ autonomous seller selection
→ bounded payment
→ fulfilment
→ exact validation

At the time, one question remained deliberately separate: would an unrelated external customer actually purchase an Atinamos service?

This event answers the narrower commercial question yes.

It does not yet answer the stronger provenance question: was the external purchaser itself an independently autonomous AI agent?

What the evidence supports

This observation supports that:

  • an unrelated external client reached an Atinamos paid x402 endpoint;
  • a valid x402 payment was supplied;
  • Coinbase payment verification returned HTTP 200;
  • Coinbase settlement returned HTTP 200;
  • 0.005 USDC settlement was observed on Base;
  • the paid JSON Repair request returned HTTP 200;
  • the event was not identified as one of the documented controlled Atinamos purchase tests.

What the evidence does not support

It does not establish that:

  • the buyer was definitely an autonomous AI agent;
  • an LLM selected Atinamos;
  • a specific marketplace caused the purchase;
  • the buyer will return;
  • this represents broad market adoption;
  • Atinamos JSON Repair will always fulfil successfully.

Atinamos does not promote the evidence to a stronger claim than the observation supports.

Public evidence

The sanitised technical record is published in the public Atinamos research repository:

The raw server logs, source IP and operational payment-account details remain private evidence.

Conclusion

On 28 August 2026, Atinamos observed its first confirmed external commercial purchase: an unrelated external client paid 0.005 USDC via x402 for Atinamos JSON Repair, settlement completed on Base, and the paid service returned HTTP 200.

This is a market-adoption observation, not an Atinamos verification verdict on its own service.