Product sentence
AffixIO sits before the action and proves whether an agent should be allowed to act.
Migration guide
Move from AffixIO 1.x to 2.0 beta without guessing the package.
This page exists to remove ambiguity. The canonical npm package remains affixio. Use the beta tag for 2.0 testing and keep production on stable until you are ready.
| Old surface | Use now | Why it matters |
|---|---|---|
@affix-io/sdk legacy | affixio | Use the public canonical package to avoid scoped package ambiguity. |
@affix-io/sdk-light legacy | affixio with the selected proof mode | HMAC and UltraHonk are proof modes in the public package, not separate current product names. |
| Legacy Node 18 examples | Node.js 20 or later | New docs and beta work should target one runtime baseline. |
| Crypto-first language | Permission-first language | Lead with the business decision, then explain ZK, ML-DSA-65 and Merkle audit as implementation evidence. |
Recommended framing
KYA sentence
Authentication asks who is calling. KYA asks whether this agent is allowed to do this, here, now.
Payment sentence
Payment systems move money. AffixIO proves the permission and evidence layer before the payment action is attempted.
Capability matrix
| Capability | Package | Licence | Remote service |
|---|---|---|---|
| Local policy decision | Available through SDK flows | Depends on account entitlement | Licence heartbeat may apply |
| HMAC evidence | Package mode | Tier gated where applicable | Optional sync |
| UltraHonk proof | Package capability where bundled | Tier gated where applicable | Optional or required by workflow |
| ML-DSA-65 attestation | Not just a local claim | Tier gated where applicable | Requires AffixIO attestation service |
| Merkle audit | SDK can prepare audit material | Tier gated where applicable | Requires connected audit service |