Technical SEO Crawl — paid production execution
On 28 August 2026 Atinamos ran one bounded, self-funded production purchase against the live Atinamos Technical SEO Crawl service.
Evidence boundary: this is a controlled seller/runtime experiment. It is not an independent Atinamos Verification classification and it is not evidence of unrelated external buyer demand.
Live machine contract
The production endpoint is:
POST https://agent.atinamos.co.uk/agent/technical-seo-crawl
The observed x402 contract required:
x402: v2
scheme: exact
network: eip155:8453 (Base mainnet)
asset: USDC
price: 0.05 USDC
settlement: on successful job acceptance
The request body requires a public url. The service is asynchronous: after a paid job is accepted, the buyer receives a job ID and polls status_url for the later crawl outcome.
Settlement and later fulfilment are deliberately separate evidence stages. A settled payment does not by itself establish that the crawl completed.
Controlled payment
The bounded buyer made one paid request for:
target: https://atinamos.co.uk/
maximum spend: 0.05 USDC
paid HTTP status: 202
job: xr-e6143412c6084a999710fd0fbcfdbe64
transaction: 0x73f0b51abb0b7129c5b4f07cc14d5e0ef6162135b153176a2cc54e1dd9fa54b3
No repeat purchase was made merely to influence marketplace indexing.
Crawl fulfilment
The worker completed the job with:
status: completed
mission_status: COMPLETED
report_complete: true
failure_class: null
technical_result: PASS_WITH_WARNINGS
Coverage was complete for the bounded target:
| Measure | Observed value |
|---|---|
| Crawl limit | 250 |
| Targets processed | 17 |
| HTML pages audited | 17 |
| Remaining URLs | 0 |
| Rate-limited targets | 0 |
| Other inaccessible targets | 0 |
| Errors | 0 |
| Warnings | 4 |
The four website warnings were one META_DESCRIPTION_LENGTH finding and three TITLE_LENGTH findings.
PASS_WITH_WARNINGS describes the website findings, not a failure of the paid service. The execution itself completed and produced its report.
Public artifacts
The completed job published:
Both later returned HTTP 200 from the public site.
The retrieved result.json was 33,306 bytes. Its SHA-256 matched the worker-produced evidence hash exactly:
df7230bc1c457cc4bf9d676d8a3ec3ff84a809070fec0501a02fc41e5f495ac6
That establishes integrity of the exact published JSON bytes checked in this run.
Machine discovery surfaces
After deployment, the Atinamos Agent Shop homepage and public catalogue both showed Technical SEO Crawl as live at 0.05 USDC.
The Shop MCP catalogue also exposed:
technical_seo_crawl
The first post-settlement Coinbase Bazaar query did not yet return the exact endpoint. A later read-only check returned the resource without any additional payment:
resource: https://agent.atinamos.co.uk/agent/technical-seo-crawl
serviceName: Atinamos Technical SEO Crawl
x402Version: 2
scheme: exact
network: eip155:8453
amount: 50000
lastUpdated: 2026-08-28T15:29:32.624Z
tags: technical-seo, seo-audit, website-crawl, site-health, evidence
50000 represents 0.05 USDC in six-decimal USDC base units.
The observed transition from initial absence to later Bazaar presence is useful discovery evidence, but it does not establish that a self-funded transaction is required for indexing. Bazaar inclusion is also not a trust, quality or external-demand signal.
What this supports
Under the recorded conditions, the live Atinamos service completed:
x402 payment contract
→ bounded USDC payment
→ asynchronous job acceptance
→ Ubuntu worker execution
→ bounded crawl
→ completed result
→ public JSON and HTML artifacts
→ exact SHA-256 verification
→ later Coinbase Bazaar discovery of the exact resource
What this does not support
This controlled run does not prove unrelated external-agent adoption, independent customer demand, that a self-purchase is required for Bazaar indexing, permanent future reliability, a universal website-quality verdict or an independent Atinamos Verification classification of the Atinamos-owned seller.
For independent buyer-facing evidence, Atinamos continues to keep seller claims, marketplace observations, buyer behaviour and verifier observations as separate evidence classes.
Technical record
The supporting public technical research note is published in the Atinamos agent-verification-research repository.