Study 6 — TAT Risk Zero-Spend Contract/Discovery Observation

Status

Independent zero-spend contract/discovery observation published.

Atinamos observed the public discovery, contract and explicitly free read-only MCP surfaces exposed by TAT Risk during an approximately two-minute external observation window on 11 September 2026.

No wallet was used. No payment payload was created. The paid endpoint was not invoked. Total spend was 0 USDC.

This record is evidence of what Atinamos observed. It is not a trust score, certification, approval or recommendation to buy.

Service identity

Provider:

TAT Risk

Observed service:

TAT Risk x402 Token Risk API

Primary advertised paid route:

POST https://x402-token-risk-api-6cj2.onrender.com/v1/risk/paid

That paid route was identified from the public service contract but was not invoked during this observation.

Observed server build:

1717b6c332ddef87537818f476b26342e1b551f7

Observation window:

approximately 2026-09-11 09:47–09:49 UTC

What Atinamos observed

The following public HTTP surfaces responded during the observation window:

The observed discovery surfaces exposed mutually consistent x402 contract information within the observation window.

Observed x402 contract

protocol:       x402
version:        2
scheme:         exact
network:        eip155:84532
network name:   Base Sepolia
testnet:        true
mainnet enabled:false
advertised price: $0.05 / 50000 atomic USDC

Across the observed public surfaces, the asset and receiver were consistent.

This is contract/discovery evidence only. It does not establish that payment would settle or that the advertised paid result would be returned.

MCP observation

Atinamos also observed the service MCP surface without entering a paid path.

The following operations succeeded:

initialize
request id: 821a298b-8c1e-49a1-8266-9ae10b408756

tools/list
request id: b42bfe66-ca14-470c-bd8d-f9baa6259dc6

tools/call: list_risk_services
scope: explicitly free / read-only
request id: 439d4088-e51f-41e2-9c45-0b207d2402cc

No paid MCP tool was called.

Negative observation — readiness contract discrepancy

The material negative observation was narrow and repeatable within the observation window:

GET /ready
observed: HTTP 500 INTERNAL_ERROR
occurrences: 2
published expected statuses: HTTP 200 or HTTP 503

Request IDs:

164deb43-4b8d-4461-bac4-3114f777c4a0
47d5a226-20ba-49ea-91e2-36c6355c56e0

Atinamos records this as:

READINESS_CONTRACT_DISCREPANCY

This finding does not mean the service was down. GET /health remained HTTP 200 during the same observation window.

Evidence classification

discovery              OBSERVED
contract_consistency   OBSERVED_CONSISTENT
mcp                    OBSERVED
free_read_only_tool    OBSERVED_SUCCESSFUL
readiness_endpoint     NEGATIVE_OBSERVATION
payment                NOT_EVALUATED
settlement             NOT_EVALUATED
fulfilment             NOT_EVALUATED
correctness             NOT_EVALUATED
quality                 NOT_EVALUATED

What Atinamos deliberately did not test

This observation does not provide seller-performance evidence for the paid service.

Atinamos did not evaluate:

• payment interoperability or acceptance;
• on-chain settlement;
• paid fulfilment;
• correctness of a purchased risk result;
• quality of a purchased risk result.

No wallet, quote, admission flow, signing flow, payment payload or settlement attempt was used.

Spend and independence boundary

observed spend:             0 USDC
independent observation:    true
Atinamos-owned service:     false
paid endpoint invoked:      false
seller-performance evidence:false

This zero-spend evidence class is intentionally separate from Atinamos paid verification runs. It must not increase paid-test, successful-fulfilment or correctness counts.

Provenance

Formal report reference:

Atinamos_TAT_Risk_Zero_Spend_Observation_Report_2026-09-11.pdf

The published record is sanitised. It contains no credentials, authentication headers, wallet material or private data.

Integrity status:

unsigned_observation

This observation is not represented as a signed Assurance receipt. If this evidence class is signed in future, Atinamos will reuse the existing Assurance signing and canonicalisation architecture rather than introduce a separate signing model.

Machine-readable lookup

Buyer agents can retrieve the same evidence class through the public buyer API using the exact service identity:

GET /v1/evidence?endpoint=https%3A%2F%2Fx402-token-risk-api-6cj2.onrender.com%2Fv1%2Frisk%2Fpaid&method=POST

The response identifies this evidence as:

zero_spend_contract_discovery

and keeps paid settlement/fulfilment and correctness evidence unavailable for this observation.

Interpretation boundary

What this record supports: Atinamos independently observed TAT Risk public discovery and machine-contract surfaces, found consistent x402 contract information across the surfaces inspected, successfully exercised the explicitly free read-only MCP path, and reproduced a readiness-endpoint discrepancy twice during the same observation window.

What this record does not support: successful payment, settlement, paid fulfilment, correctness, quality, permanent reliability, provider-wide trust, certification, approval, or a recommendation to purchase the service.

The buyer decides what this evidence means for its own policy.