02.1 — gateway
LIVEGEO Gateway
The catalog becomes machine-readable for agents: public llms.txt, /geo endpoints with structured answers, and explicitly declared crawl policies.
verify shop.catyai.io/llms.txt ↗01 / System — what we build
AI architecture, proven live.
> Network AI Protocol (N▍
We design and operate the infrastructure through which AI agents discover, evaluate and buy products — with public cryptographic proof, not slide decks. The proof is called CatyAI and it is running now.
We are an architecture firm for systems that sell. PayAi-X designs, builds and operates the commerce infrastructure for the AI-agent era: machine-readable gateways, cryptographically signed answers, catalogs with millions of clean products, and the attribution rails that turn a recommendation into a measurable sale.
Every claim on this page has a public endpoint behind it. Verification is one click away — exactly as it should be.
About PayAi-X
Who is PayAi-X?
PayAi-X is a technology company specialized in software development, artificial intelligence and automation solutions for business.
Our mission is to build products that simplify financial, operational and decision-making processes using AI that is safe, fast and easy to integrate.
Solid Engineering
Best practices in software development
AI Ethics
Responsible and transparent AI
Security First
Bank-grade protection
Results Driven
Measurable business impact
Our vision
Useful AI
Real business value
Explainable AI
Transparent decision-making
Responsible AI
Humans and AI working together
02 / Proof
CatyAI · live system
02.2 — trust
LIVETSO — the trust object
Every answer carries a Trust & Safety Object: Ed25519 signature, kid, signed timestamp, source hash. Public keys live in the JWKS — any third party validates what the system said, without taking our word for it.
verify /jwks.json ↗02.3 — protocol
LIVEMCP Server
Over 50 tools exposed to agents via the Model Context Protocol: semantic search, price comparison, product card rendering.
endpoint /api/mcp · POST02.4 — catalog
LIVECatalog + Google CSS
3.8 million+ products from the 2Performant network, with deterministically validated GTIN. PayAi-X operates as a Google CSS partner.
verify shop.catyai.io ↗03 / NAP
Network AI Protocol · zero-trust
Probability is not proof. Signature is.
Every claim about a product carries the digital signature of the store that authorized it. Like a notary’s stamp, placed on every answer.
Running in production in CatyAI, on real traffic, since April 2026 — and you can test it yourself, without an account, in the next section.
STEP 01
The store signs its data
technical: Ed25519 · RFC 8032 · RFC 8785
STEP 02
The AI reads only what is signed
technical: source-bounded retrieval · Qdrant
STEP 03
Every claim passes a filter
technical: 4 invariants · unverified_claim → block
STEP 04
Everything remains provable
technical: TSO · JWKS · RFC 7517
Other systems try to teach the model not to make mistakes. NAP removes the possibility of mistake: what the store has not authorized does not exist in the answer.
EU AI Act · Directive 2005/29/EC · FTC §5 · 16 CFR Part 255
04 / Verification
no account · no NDA · without our consent
01
Fetch the public JWKS
GET api.catyai.io/.well-known/jwks.json — open, unauthenticated, RFC 7517 compliant. It contains the public verification keys.
02
Resolve the key by kid
The signed answer declares the key’s kid; you match it with the JWKS entry. The signer’s identity is public and established.
03
Verify the signature
Ed25519 over the canonicalized payload (RFC 8785). If a single byte changed, verification fails. Deterministic, reproducible.
# reproduce the proof on a production answer — right now
$ curl -s -X POST https://shop.catyai.io/geo/v2/answer \
-H 'Content-Type: application/json' \
-H 'User-Agent: GPTBot/1.0' \
-d '{"question":"ce anvelope iarna recomanzi?","lang":"ro","domain":"shop.catyai.io"}'
# → trust.signature: EdDSA · kid ↔ JWKS · signed timestamp · source hashRFC 8032 — EdDSARFC 8037 — JOSERFC 7517 — JWKSRFC 8785 — JSON Canonicalization
published IETF standards · zero proprietary drafts
05 / Integration
for AI platforms · three paths, one standard
A — SDK
SDK Integration
The platform invokes the verification SDK before serving any commercial output. Verification remains a side-channel — control of the generation flow stays entirely with the platform.
2–4 weeks of engineering · minimal risk
B — Gateway
Sidecar Gateway
Commercial answers pass through a NAP gateway that returns a signed, verified answer — or an explicit refusal. Centralized enforcement, with contractual SLA and failover.
4–8 weeks · explicit SLA
C — Native
Native protocol
NAP at the model boundary: every token in commercial scope resolves to a signed source span. The deepest integration, the smallest residual risk surface.
8–16 weeks · maximum investment, minimal risk
STAGE 01
Scoping call — 45 minutes
Current commercial surface, risk classification, existing mitigation stack, jurisdictional exposure.
STAGE 02
Technical due diligence — one week
Access to the production endpoint, threat-model walkthrough, canonicalization spec review. No commercial commitment.
PATH A
Fixed-scope project — 6–10 weeks
One defined commercial surface, written acceptance criteria, verifiable deliverable. Best for the highest-risk vertical.
PATH B
Multi-quarter advisory
Embedded provenance support: protocol evolution, regulator responses, audit-readiness across multiple product surfaces.
the disclosure boundary
Public materials — this page, the JWKS endpoint, the verification procedure — require no agreement and are verifiable in real time. Threat model, detailed API surface and roadmap are discussed under mutual NDA.
06 / Case studies
measured figures, not promises
CS.01 — own platform
LIVECatyAI — end-to-end agentic commerce
We designed and operate the entire chain: a public catalog of 3.8M+ products, an agent-readable gateway, cryptographically signed answers and attribution measurable down to the merchant, through the 2Performant network.
3.8M+
public products
50+
MCP tools
100%
signed answers
CS.02 — semantic engine
LIVESearch that understands “no frills”
Our own acceptance battery: 25 queries × 11 verticals. We proved rank pollution (40.1% dead vectors in the index), deleted 1.63M points, and coverage zeros disappeared — “anvelope”: 0 → 10 correct results.
52→67%
negation, in progress
1.63M
dead vectors removed
0→10
“tires” coverage
CS.03 — catalog engineering
LIVE57,771 pseudo-categories, merged without SEO loss
Taxonomy consolidation with mandatory dry-run and risk measured before execution: the touched surface had 62 impressions/28 days. Result: coherent pages, clean redirects, zero regression.
57.8K→22K
pages consolidated
301
clean redirects
0
SEO regression
CS.04 — feed audit
SERVICEFeed diagnostic for merchants
Premium fashion retailer, Gomag platform: 26 of 76 products with defects blocking listing — identified and fixed before the first leu was spent on campaigns. The audit is part of setup, not an extra invoice and not a freebie.
26/76
products with defects
<48h
diagnostic time
07 / Principles
non-negotiable
P.01
Solid engineering
Systems built on foundations, not hacks. Complete, verified code, with rollback written before deploy.
P.02
Security first
Keys, secrets and data treated as critical infrastructure. We sign what we say; we never ask for blind trust.
P.03
Measurable or it doesn’t exist
Every delivered system comes with its metrics. If you can’t measure the effect, we haven’t finished it.
P.04
Honest AI
No model-invented figure goes into production. Critical data comes from source, not from an LLM.
08 / Structure
dual entity
EU entity
PayAi-X S.R.L.
- Registration
- CUI RO48134813
- Registered office
- Bucharest, Romania
- Founded
- 2023
- Role
- Engineering · operations · EU clients
20:41:08
Bucharest · local
International entity
PayAi-X FZE
- Registered office
- Dubai, UAE
- Zone
- DWTC Free Zone
- Role
- Cloud infrastructure · international contracts
21:41:08
Dubai · local
09 / Contact — 20 minutes
We discuss what we build after you see what we have built.
If you are a merchant, a platform or a partner and you want infrastructure that survives verification — not presentations — write to us. The first discussion: 20 minutes, with the live system open in front of you.
Ioan Adrian Vitan · founder