Explore verification

Atinamos Evidence Receipt

Production signed evidence · one timestamped observation · no trust score

This page is a human-readable view of the signed Evidence Receipt held in the Atinamos Assurance append-only application register. It records what Atinamos observed during one machine-service invocation. It does not certify the service as permanently trusted, safe, recommended or guaranteed to behave the same way in future.

You can pay to be tested. You cannot pay to be trusted.

View the raw signed JSON · Evidence Receipt schema · Published signing key

Receipt identity

Field Value
Receipt ID atinamos:receipt:10e40afd-f6b1-57bd-9c1e-0a4a1695a428
Receipt version 1.0-draft
Issued at 2026-09-07T11:42:57.000596Z
Provider keyronne.com
Service Keyronne JSON Repair
Service ID atinamos:service:sha256:01438440eb46a74c57726cca5890ca0ec9c4932d5bed4120296d307220cbd3bb
Endpoint https://keyronne.com/api/json-repair
HTTP method POST
Observation started 2026-09-07T11:42:53.565564Z
Observation completed 2026-09-07T11:42:56.448751Z

Observed outcome

Payment settlement and the advertised kind of deliverable were observed. Factual correctness and quality were not evaluated.

Field Value
Outcome class settled_fulfilment_correctness_not_evaluated
Attribution none
Requested by atinamos-generic-fulfilment-bazaar-proof
Funding source atinamos_research

The funding source identifies who paid for the observation. It is not a favourable-rating field and does not change the recorded result.

Observation stages

Stage Status Reason
Endpoint reachability pass
Contract observation pass
Payment authorisation pass
Authorised invocation submission pass
Settlement observation pass
Fulfilment observation pass
Assertion evaluation not_reached CORRECTNESS_NOT_EVALUATED_BY_FULFILMENT_ASSURANCE

Payment contract observed

Field Value
Protocol x402
Version 2
Scheme exact
Network eip155:8453
Amount 0.001 USDC
Asset eip155:8453/erc20:0x833589fcd6edb6e08f4c7c32d4f71b54bda02913
Recipient 0xb86f95ef5fa904318ea9df3b59adce099b478fc4

Assertions

Assertion Version Result Description
generic-transaction-fulfilment:advertised-deliverable 1.0 not_evaluated Atinamos checks whether the advertised kind of machine deliverable was returned. Factual correctness and quality of the returned content are not evaluated.

Evidence commitments

The underlying operational evidence does not all need to be public. These SHA-256 commitments identify the retained evidence used to construct the receipt without publishing private verifier material.

Artifact Type Digest Visibility
artifact:verification-evidence assurance_runner_package sha256:1734e2c5d9ed6aacc8c59d65771235fc535d29587167c5037146674b27a0694f private_commitment
artifact:payment-contract payment_contract sha256:f2c995eeba60c412c5b375f15fd059534e9c76162bbec5843c5467b346fce9a8 private_commitment
artifact:assertions assertion_results sha256:03eda01ffffcf736d6770b82250b0fef6dcc0541f19e5857de88a0506ddd0a1d private_commitment
artifact:service-response service_response sha256:b4b36ee0e6729f7b5419d0cd19574869698c67dbff224b752fc477945cfd302d private_commitment

Cryptographic integrity

The Ed25519 signature covers the RFC8785-canonical signed payload bytes directly. content_hash is a separate SHA-256 commitment over those same canonical payload bytes. The top-level integrity object is not itself part of the signed payload; the signed issuer.key_id identifies the key that must be used for verification.

Field Value
Issuer key ID atinamos-assurance-ed25519-202609-002
Status signed
Canonicalisation RFC8785
Canonical profile atinamos-evidence-receipt-v1-number-free
Hash algorithm SHA-256
Content hash sha256:5c323567ce6e97d858153d0403ed93182db8fc1b502b9103d356e282abe77d76
Signature algorithm Ed25519
Signature encoding base64url-no-pad
Signature present yes
Public key Published key document

Limitations carried by this receipt

  • FUTURE_BEHAVIOUR_NOT_ESTABLISHED — This receipt records one observation and does not establish future service behaviour.
  • TRAFFIC_DISTINGUISHABILITY_NOT_EVALUATED — This observation does not establish that verifier traffic was indistinguishable from ordinary buyer traffic.
  • CONTENT_CORRECTNESS_NOT_EVALUATED — This observation records whether the advertised deliverable was returned. It does not establish the factual correctness or quality of its contents.

How to independently inspect it

  1. Retrieve the raw signed receipt JSON.
  2. Validate it against the Evidence Receipt schema.
  3. Read the signed issuer.key_id and retrieve the corresponding public key from the Atinamos public key directory.
  4. Remove the top-level integrity member, canonicalise the remaining receipt using RFC8785 under the stated number-free profile, and compute SHA-256 over the canonical UTF-8 bytes.
  5. Confirm that digest equals integrity.content_hash, then verify the Ed25519 signature over those same canonical bytes.

What this receipt does not mean

  • It is not a trust score.
  • It is not a claim that the service is safe to buy from in every circumstance.
  • It does not predict future behaviour.
  • A later successful observation would not erase an earlier failure, and a later failure would not rewrite this observation.
  • Receipt volume must not be interpreted as reputation; each observation stands on its own evidence and timestamp.

Atinamos provides evidence. The buyer decides what that evidence means and whether to spend.