A public inventory of the stack we actually have.
This catalog is intentionally backed by the same lane and registry families the repos expose. It is here to make the breadth legible without flattening the architecture or hiding the real work under generic product language. The live public view now includes protocol-family, lifecycle-stage, market-class, and verification-service matrices instead of only headline counts.
xytara catalog
xytara currently exposes 27 integrations across 21 top-level public lane families.
- Works with MCP and agent clients such as: claude mcp, openai codex (client compatibility profiles, not partnerships)
- Framework compatibility profiles: autogen, langchain, langgraph, semantic kernel, crewai, llamaindex
- Protocols and transports: a2a, a2c, acp, grpc, kafka, mcp, mqtt, nats, ros2, webhook_event_bus
- Canonical rails: evm, base, usdc (live: x402 USDC on Base); bsv_teranode (catalog/reference only, not live settlement)
- Major rails family: antelope, constellation_dag, digibyte_dgb, hedera_hbar, kaspa_kas, metal, polkadot_dot, proton_xpr_and_metal, solana (catalog/reference only, not live settlement)
- Interface and interop contracts: openapi, asyncapi, cloudevents, auth_interop, identity_interop
xoonya catalog
xoonya currently exposes 6 proof integrations across 14 top-level public lane families.
- Works with MCP and agent clients such as: claude mcp, openai codex (client compatibility profiles, not partnerships)
- Framework compatibility profiles: autogen, langchain, langgraph, semantic kernel
- Canonical rails: evm, base, usdc (live: x402 USDC on Base); bsv_teranode (catalog/reference only, not live settlement)
- Major rails family: antelope, proton_xpr_and_metal, solana (catalog/reference only, not live settlement)
- Proof lanes: proof_bridge, external_proof_import, result_package_trust, erc8004
Catalog operations
The public stack does not stop at lane headlines. It already includes explicit discovery, registry, review, promotion, interface contract, and interop surfaces so integrators can inspect, classify, and operationalize breadth without guessing.
- xytara operations: /v1/integrations, /v1/integrations/summary, /v1/integrations/classes, /v1/integrations/protocols, /v1/integrations/settlement-modes, /v1/integrations/review/submission-bundle, /v1/integrations/review/submission-bundle-set, /v1/integrations/review/registry-snapshot, /v1/integrations/promotion-readiness, /v1/integrations/promotion-workflow, /v1/integrations/promotion-actions
- xoonya operations: /v1/integrations, /v1/integrations/summary, /v1/integrations/snapshot, /v1/integrations/promotion-readiness, /v1/integrations/promotion-workflow
- Family matrix: 9 families
- Lifecycle matrix: 13 stages
- Market matrix: 6 classes
Live matrices
The current public inventory is easier to use when the core matrices sit up front. Families, lifecycle stages, market classes, provider journeys, delivery, durability, and proof surfaces are already part of the live catalog truth.
- Families: 9
- Lifecycle stages: 13
- Market classes: 6
- Provider journeys: 0
- Delivery summaries: 1
- Trust portability profiles: 1
Catalog summary · Provider journeys · Delivery summary · Public proof summary · Site map
Why this is architecturally sound
The catalog is broad, but the core remains disciplined. xytara owns runtime and commercial consequence. xoonya owns proof and followthrough. Adapters, standards, and ecosystem lanes sit around those centers rather than replacing them.