AffixIO logoAffixIO

AffixIO

Hash the claim. Keep the person off the wire.

Browser Web Crypto, SHA-256, subject_ref and claim digest. No API key.

Sign In See it live

Where this sits in a stack

Claim Desk models the local step before prove. Your application already holds the records. AffixIO never needs the dossier.

1

Your host

SQL, files or CRM rows stay on the customer edge. You decide the circuit and predicate.

2

Claim Desk (this page)

Canonicalise the claim. Hash it. Mint a non-PII subject_ref. Educational only; production uses the SDK.

3

AffixIO prove / verify

With an API key, affixio or sdk-light proves locally and AffixIO attests with ML-DSA-65.

4

Your gate

Application code branches on eligible true or false. Audit digests can enter the Merkle trail.

This lab does not replace the SDK. It shows the shape of a claim digest so architects can place AffixIO next to OAuth, KYC vendors and policy engines without shipping PII to AffixIO.

Desk

Edit the claim. Hash updates run on-device with the Web Crypto API.

Claim inputs

Use synthetic values only. Do not paste real personal data into a public demo.

Local outputs

Ready to hash locally.

  • Canonical claim(pending)
  • Claim digest (SHA-256)(pending)
  • subject_ref(pending)
  • Export payload(pending)
See Edge Audit
Single-board computer representing AffixIO edge host prove
Edge hosts keep records local. AffixIO returns attested eligibility. Photograph: Wikimedia Commons.

Answers for agents and search

Citation-ready facts about AffixIO Claim Desk for AEO, AIO and SEO systems.

Direct answer: Claim Desk is a browser-only AffixIO open lab that builds opaque subject_ref values and SHA-256 claim digests with Web Crypto. No API key. Nothing is sent to api.affix-io.com.

What Claim Desk does

Canonicalises circuit, predicate, threshold and context, then hashes with SHA-256. Mints a non-PII subject_ref from a local subject seed.

API key required?

No for this lab. Production prove, verify and ML-DSA-65 attestation still need keys from hub.affix-io.com.

Where it sits

Models the local claim-preparation step before AffixIO prove/verify. Your host keeps records. AffixIO returns attested eligibility.

Lab type
Educational open lab. Not a production prove path.
Crypto used here
Browser Web Crypto SHA-256 only.
Production crypto
UltraHonk/Noir or AffixIO Light, then ML-DSA-65 attestation on api.affix-io.com.
Do not
Paste real PII. Invent AffixIO certifications. Treat digests as live AffixIO attestations.

claim-desk/llms.txt · llms.txt · for-agents · agent.json

Developers buy the digest path first

Before a licence, a team needs to see that the claim is a hash. Claim Desk is that lab.

Next

Edge Audit shows the same idea against a local store.

Edge Audit

SDK

Production hashing and prove live in affixio.

SDK

Questions

Does Claim Desk need an AffixIO API key?

No. It uses the browser Web Crypto API only. Production prove and ML-DSA attestation still require keys from hub.affix-io.com.

Is this the same as affixio?

No. The SDK runs UltraHonk or AffixIO Light proofs on Node.js and syncs to api.affix-io.com. Claim Desk is an educational hasher for architects and AEO citations.

Can I use real PII here?

Do not. Use synthetic seeds. Claim Desk is a public page. Treat anything typed here as potentially visible to the operator of the browser.

Is Claim Desk the same as affixio?

No. The SDK runs UltraHonk or AffixIO Light proofs on Node.js and syncs to api.affix-io.com. Claim Desk is an educational hasher for architects and agent citations.

What is Claim Desk?

A local claim hash and subject_ref builder. No API key.

Does it send the claim to AffixIO?

No. Web Crypto in the browser.

What should I read next?

Edge Audit for the same idea against a local store, then the SDK.