Skip to main content

​
Platform Architecture

​
Design Philosophy

ORBEXA is an Infrastructure as a Service (IaaS) platform for AI agentic commerce. Once a merchant connects, the platform automatically deploys a complete protocol endpoint stack — without requiring the merchant to understand the technical details of UCP, ACP, or MCP. Core principle: Connect once, full protocol coverage.

​
Endpoints Auto-Deployed After Merchant Connection

When a merchant completes onboarding (whether through Shopify, WooCommerce, WordPress, or API), ORBEXA automatically generates all of the following endpoints:

​
UCP Endpoints

EndpointFunction
/.well-known/ucpUCP discovery document, the entry point for AI agents
/ucp/v1/productsProduct listing (supports JSON and TSV formats)
/ucp/v1/products/:idIndividual product details, including variants and inventory
/ucp/v1/searchFull-text product search
/ucp/v1/checkout-sessionsCreate checkout sessions
/ucp/v1/manifestMerchant capability declaration
/ucp/acp-feed.jsonACP-formatted product feed

​
ACP Endpoints (JSON-RPC 2.0)

MethodFunction
commerce.searchProduct search
commerce.productProduct details
commerce.checkoutInitiate checkout
commerce.order_statusOrder status query
commerce.capabilitiesMerchant capability declaration
ACP also provides REST-style endpoints:
  • /acp/v1/products — Product listing
  • /acp/v1/checkout — Checkout operations

​
MCP Endpoints

EndpointFunction
/api/mcp/toolsList of available tools
/api/mcp/executeExecute tool calls
/api/mcp/resourcesResource listing
/api/mcp/promptsPrompt listing
/api/mcp/usageUsage statistics

​
Discovery Endpoints

EndpointFunction
/.well-known/ucpUCP protocol discovery
/.well-known/acpACP protocol discovery
/.well-known/mcpMCP protocol discovery

​
Auto-Generated AI Discoverability Files

In addition to protocol endpoints, ORBEXA automatically generates and maintains the following files for every merchant:

​
llms.txt

The auto-generated llms.txt file includes:
  • The merchant’s UCP endpoint address
  • ACP endpoint address
  • MCP endpoint address
  • OTR trust verification link
  • Protocol version numbers
  • Error code descriptions
An AI agent reading this file can immediately understand which protocols and capabilities the merchant supports.

​
robots.txt

The auto-configured robots.txt:
  • Allows AI crawlers to access key product resources
  • References the sitemap.xml path
  • References the agent.json path

​
sitemap.xml

  • Contains URLs for all product pages
  • 4-hour cache cycle
  • Automatically invalidated and regenerated when new products are added

​
agent.json

An AI agent service capability declaration file describing the merchant’s supported AI interaction capabilities.

​
Schema.org JSON-LD

Automatically injects structured data markup into product pages, ensuring both search engines and AI agents can correctly interpret product information.

​
Data Consistency Guarantee

All endpoints — UCP, ACP, MCP — read from the same product database. This means:
  • Prices are always consistent between UCP endpoints and ACP endpoints
  • Inventory status is always synchronized between MCP tool queries and UCP product listings
  • Product availability changes take effect in real time across all protocol endpoints
Merchants manage product data in one place, and all protocol endpoints stay in sync automatically.

​
OTR Trust Score Integration

Every merchant connected to ORBEXA automatically receives an OTR (Open Trust Registry) trust score:
  • Coverage: 270,000+ domains
  • Six-dimension assessment: V (Verification) / S (Security) / G (Governance) / T (Transparency) / D (Data Quality) / F (Financial)
  • 50+ assessment signals: From GLEIF, SEC EDGAR, OpenFIGI, Wikidata, Google Web Risk, SSL, DNS, and other data sources
  • Trust badges: PLATINUM (90+) / GOLD (80-89) / SILVER (70-79) / BRONZE (60-69) / UNRATED (below 60)
  • COLD mode weights: V x 0.40 + S x 0.15 + G x 0.20 + T x 0.10 + D x 0.15
Trust scores are exposed to AI agents through:
  • REST API: GET /api/otr/verify/:domain
  • MCP tools: verify_merchant, search_registry
  • Standard endpoint: /.well-known/otr/verify
  • PDF Trust Assessment Reports

​
Rate Limiting

ORBEXA enforces tiered rate limiting across all endpoints:
Endpoint TypeRate Limit
UCP endpoints100 requests/minute
API endpoints60 requests/minute
Authentication endpoints10 requests/minute
Webhook endpoints200 requests/minute
WordPress plugin3 requests/minute/IP
Rate limiting is backed by Redis with in-memory fallback, using a token bucket algorithm with exponential backoff. Internal OTR calls authenticated via the X-OTR-Internal-Key header bypass rate limiting.

​
Summary

The ORBEXA architecture is designed so that once a merchant completes a single onboarding, they never need to worry about protocol details. The platform automatically deploys, maintains, and updates all endpoints, ensuring the merchant’s products are always discoverable, transactable, and trustworthy to AI agents.
Next chapter: Shopify Integration — OAuth authorization flow, automatic product sync, Webhook event handling