Skip to product choices
IFFInspect first
Updates
EN
Latest · Oct 11 Post-quantum progress: signatures, backups and Tunnel test

Two services · separate claims

Choose the evidence you need.

IFF keeps external endpoint observations separate from portable artifact provenance. Start with what you want to inspect.

Public x402 endpointsExternal observation

x402 Evidence Monitor

See what an external monitor observed from a public x402 endpoint's unpaid response: ownership, protocol behavior, availability, freshness and signed provenance.

No payment is sent. The evidence is not a safety score or delivery guarantee.

Open x402 Monitor

Signed agent artifactsAlpha · Core 0.3

Apostille

Apostille v0.4.0-alpha.1 provides a Go SDK, local CLI and browser verifier. New keys use ML-DSA-65; the hosted service issues Core 0.3 only. Verify portable bundles offline with independently chosen issuer and key pins.

It does not establish content truth, legal identity or legal effect. It also does not prove current ownership or payment authority.

Open Apostille Open source on GitHub Downloads and installation

Post-quantum cryptography · Status as of 2026-10-11

Stronger protection, with a clear scope.

We are upgrading the cryptography that protects evidence and stored backups. Each layer has its own rollout and verification status.

SignaturesLive · new evidence
ML-DSA-65 signs new x402 observations, transparency-log tree heads, Service Receipt v2 and hosted Apostille Core 0.3 certificates. Earlier Ed25519 records remain verifiable and retain their original signature algorithm.
BackupsLive · restore tested
New database backups encrypt data with AES-256 and wrap the file key with hybrid ML-KEM-768 + X25519. A production backup and an isolated PostgreSQL restore passed on October 10. Older backups keep their existing encryption.
Client to CloudflareMeasured
On October 10 (Taipei time), our test client negotiated X25519MLKEM768 with the Cloudflare endpoint for ifandonlyif.io. Other clients may negotiate differently.
Cloudflare TunnelIsolated test passed
On October 11, an isolated Railway test connector negotiated X25519MLKEM768 with Cloudflare over QUIC / TLS 1.3, with certificate verification. A request through the tunnel reached the API health endpoint and returned a matching request ID. Production routing remains unchanged.

This does not make the entire system quantum-safe. Wallet and blockchain signatures and the experimental Groth16 profile remain classical. These upgrades do not prevent stolen keys or compromised hardware, and signed evidence does not establish content truth.

Verify an Apostille bundle Read the rollout details

MCP alpha · For your AI client

Let your agent read the evidence.

MCP (Model Context Protocol) lets compatible AI clients use IFF tools. Our public Streamable HTTP service runs on Railway: no local server, account or API token is needed.

  1. Choose the endpoint for the evidence you need.
  2. Add its URL as a Streamable HTTP server in your MCP client.
  3. Ask your agent to inspect a public endpoint or verify a signed bundle.

x402 Monitor

13 read-only tools

Read public x402 observations, compare payment requirements, and check transparency-log proofs and receipts. No payment is sent.

“What did IFF observe about this x402 endpoint?”
Streamable HTTP endpointhttps://iff-mcp-api-production.up.railway.app/mcp/iff
x402 MCP setup

Apostille

7 read-only tools

Verify bundle signatures or detached ERC-8004 bindings, and read public issuer data. Supply independently chosen issuer/key pins when deciding trust.

“Do this bundle’s signatures match the issuer and key I pinned?”
Streamable HTTP endpointhttps://iff-mcp-api-production.up.railway.app/mcp/apostille
Apostille MCP setup

Checks run on the hosted server; they are not independent verification inside your client. These public tools cannot log in, sign, publish or pay. Never send private keys, original files or ZK witnesses. Use a local verifier when independent verification is required.