AffixIOAFFIXIO
Contact
Frequently Asked Questions

Questions people ask about AffixIO

Zero-knowledge proofs, AI agent governance, post-quantum readiness, EU AI Act compliance, and how stateless verification fits into your stack, answered.

Zero-knowledge proofs Know Your Agent Stateless policy engine Post-quantum ready EU AI Act 2026 GDPR Article 25 Defensible evidence No PII at verifier

Understanding AffixIO & AI Agents

YES|NO

Understanding AffixIO

What is AffixIO? +

AffixIO is a stateless verification engine, a truth layer that sits between a request and an action and returns a single signed yes or no. It evaluates eligibility, identity, and policy in real time without storing personal data at the verifier, and produces a cryptographic proof of every decision for audit.

role: truth_layer@verifier · retention: none
What does "truth layer" mean in practice? +

A truth layer grounds automated systems in verifiable facts before they act. Instead of trusting a black-box model score, a downstream system asks AffixIO a binary question (is this payment eligible? is this agent authorised?) and receives a cryptographically signed allow or deny with no ambiguity and no silent inference.

How is AffixIO different from an identity provider or IAM? +

Identity providers manage sessions and issue tokens. AffixIO does neither. It is stateless: no session is created, no profile is stored at the verifier, and no token persists between calls. It answers a single policy question per request and attaches a signed proof to the result.

boundary: stateless_only · sessions: none
What is a stateless verification engine? +

A stateless verification engine processes each request independently with no standing memory of prior requests. Every call receives the same policy evaluation from scratch. This eliminates profile drift, cross-contamination of decisions, and the compliance risk of holding unnecessary identity state.

AI Agents & Agentic Systems

Can AffixIO verify AI agents before they act autonomously? +

Yes. AffixIO intercepts each agent action at the decision boundary and returns a signed allow or deny before the action executes. This applies to tool calls, payment instructions, data access requests, and API calls made by autonomous or semi-autonomous AI agents.

gate: agent_action@boundary · proof: signed_allow_v2
What is Know Your Agent (KYA) and how does AffixIO address it? +

Know Your Agent (KYA) is the emerging requirement to verify non-human identities (service principals, LLM agents, and automated workflows) with the same rigour applied to human users. AffixIO provides a verifiable, policy-bound gate for each agent action, producing signed evidence that a specific agent was authorised at a specific point in time.

How does AffixIO prevent an AI agent from acting outside its authorised scope? +

Each AffixIO request carries a scope boundary. If an agent's action falls outside the authorised scope (wrong data type, wrong recipient, wrong value range). The decision engine returns a signed deny and the action is blocked. The signed proof is retained as evidence that the boundary was enforced.

boundary: scope_violation · outcome: DENY · proof: retained
Does AffixIO support agentic payment verification? +

Yes. AffixIO can gate payment instructions from AI agents by evaluating eligibility, merchant authorisation, and transaction scope before funds move. The signed allow or deny is replayable, giving payment processors and compliance teams a cryptographic record for every automated transaction.

Cryptography & Compliance

ZK|PQ

Zero-Knowledge Proofs & Cryptography

How does AffixIO use zero-knowledge proofs? +

Zero-knowledge proofs allow AffixIO to prove a fact (age over threshold, account in good standing, credential valid) without revealing the underlying data. The verifier receives proof that the condition is true, not the raw value, so no personal information crosses the verification boundary.

proof_type: zk · pii_transmitted: false
What is a signed yes/no decision and how is it verified? +

Each AffixIO outcome is a binary result (allow or deny), accompanied by a cryptographic signature covering the request identifier, the policy evaluated, and the timestamp. Any downstream system can verify the signature independently without calling AffixIO again.

Is AffixIO post-quantum ready? +

AffixIO is designed for long-lived assurance. The proof architecture is aligned with NIST post-quantum cryptography standards including ML-KEM hybrid schemes, protecting against harvest-now-decrypt-later attacks where adversaries collect signed proofs today intending to break them with future quantum computers.

crypto: pq_hybrid · standard: NIST-ML-KEM
Can I audit decisions without seeing personal data? +

Yes. AffixIO's audit surface uses zero-knowledge techniques so an auditor can verify that a policy was applied correctly without accessing the raw attributes of the subject. This satisfies the audit requirement while preserving data minimisation obligations under GDPR and the EU AI Act.

Compliance & Regulation

How does AffixIO help meet EU AI Act obligations? +

The EU AI Act's general application deadline is August 2026. For high-risk AI systems it requires verifiable logging, human oversight gates, and demonstrable risk management. AffixIO provides signed decision records, policy-bound gates before autonomous actions, and a replayable audit trail, each satisfying a specific obligation under the Act.

framework: EU_AI_Act · deadline: 2026-08-02
Does AffixIO support GDPR Article 25 privacy by design? +

Yes. By processing verification requests without storing personal data at the verifier, AffixIO implements data minimisation and privacy by default as required under GDPR Article 25. Zero-knowledge proof surfaces allow attributes to be verified without being transmitted or retained.

Is AffixIO relevant for DORA or MiCA compliance? +

Yes. DORA requires financial entities to demonstrate operational resilience and audit trails for automated decisions. MiCA requires crypto-asset service providers to enforce eligibility gates and maintain records. AffixIO's signed proofs and stateless architecture directly support both frameworks.

frameworks: DORA · MiCA · proof_retention: operator
What is defensible evidence and how does AffixIO produce it? +

Defensible evidence is documentation that can withstand regulatory scrutiny, not just a policy statement that controls exist, but cryptographic proof that a specific control was applied at a specific moment. AffixIO signs every decision, making each allow or deny independently verifiable and tamper-evident.

Integration & Operations

API|OPS

Integration & Operations

How quickly does AffixIO integrate? +

AffixIO exposes a single POST endpoint. Integration is one packet in, one signed response out. It does not require replacing your existing identity stack, database, or data model. Most integrations reach production within days.

endpoint: POST /verify · response: signed_result
Does AffixIO work in offline or low-connectivity environments? +

Yes. AffixIO supports offline verification using locally cached signed credentials that can be evaluated without a live connection. Decisions made offline are reconciled when connectivity returns, and the signed proof chain remains intact throughout.

mode: offline_reconcile_ready
What is the latency of an AffixIO verification decision? +

AffixIO is designed for sub-millisecond policy evaluation at the verification boundary. The stateless architecture eliminates session lookup overhead, and the single-packet request model minimises round-trip cost. Production deployments typically measure p99 latency well under 10ms.

p99_latency: <10ms · session_lookup: none
Where is personal data stored? +

Personal data is not stored at the AffixIO verifier. The verifier receives only what is needed to evaluate the current request, returns a signed result, and retains nothing from the subject's attributes. Operational logs cover request metadata only, never personal data values.

pii_at_verifier: none · log_scope: metadata_only