Core Components
Component map
Acceso is a set of coordinated components that behave like one platform. Each component has a clear boundary and scaling model.
Clients
-> Gateway (auth + quotas + routing)
-> Domain services (protocol logic)
-> Upstreams + caches + derived views
-> Delivery (WS + webhooks)Owns the “platform contract”. Stays thin and deterministic.
API Gateway / API Server (public edge)
Authentication and API key validation.
Rate limiting, quotas, and abuse controls.
Request validation and version-aware routing.
Response wrapping and consistent errors.
Request identifiers and telemetry propagation.
Each domain service owns its protocol logic and failure modes.
Domain services (internal)
Solana service: chain reads, parsing, token/account views.
DeFi analytics service: trades, liquidity, derived market views.
Polymarket service: market metadata, orderbooks, trades.
ZK proof service: proof generation and verification workflows.
x402 payment service: payment negotiation and settlement flows.
Notification service: WebSockets and webhook delivery.
Real-time systems reuse the same normalized data primitives as REST. That keeps shapes consistent across delivery channels.
Real-time delivery
Redis for caching and coordination on hot paths.
Observability (logs, metrics, tracing) for production diagnosis.
Upstream pools (RPC providers, protocol adapters) with resilience patterns.
Shared infra supports all services. It is not exposed directly to clients.
Shared infrastructure
See responsibilities per service in Service Boundaries & Responsibilities.
WebSockets for streams and low-latency feeds.
Webhooks for event-driven notifications and automation.
SDKs and dashboard
SDKs mirror the API surface with typed methods and safer defaults.
Dashboard manages API keys, usage, and alert configuration.
Last updated