High-Level System Overview

All traffic enters through one gateway. Domain services do the protocol work. Shared infrastructure provides caching and telemetry.

System shape (mental model)

Acceso is a unified access layer between blockchain networks and consuming applications. It hides upstream complexity behind stable, versioned contracts.

REST / SDK        WebSockets        Webhooks
    \                |                /
     \               |               /
      \              |              /
              API Gateway
        (auth, quotas, routing)
                    |
          Normalized contracts
                    |
     Domain services + cache + telemetry
                    |
          Upstreams (RPCs, vendors)

Acceso exposes multiple integration surfaces. They all route through the same normalization and safety layers.

This is the simplified view. For the full internal service breakdown, see Overall Architecture.

What you integrate with

• REST APIs for request/response reads and analytics.

• SDKs (TypeScript, Python) aligned to the REST resources.

• WebSockets for low-latency streams.

• Webhooks for event-driven workflows.

• Dashboard for API keys, usage, and alerts.

Where to dive deeper

Stable boundary (slow-changing)

• Versioned API resources

• Stream and webhook contracts

• SDK surface and types

This is what you code against.

Internal boundary (fast-changing)

• RPC providers and failover policy

• Protocol adapters and parsers

• Cache strategy and derived datasets

• Internal service implementations

This can evolve without client rewrites.

Stability vs evolution

• Fault isolation. One protocol issue should not take down everything.

• Independent scaling. Hot domains scale without overprovisioning others.

• Clear ownership. Each service owns its parsing, caching, and upstream logic.

Why the “service-per-domain” split matters

• Authentication and key validation.

• Quotas and rate enforcement.

• Parameter validation and request sanitization.

• Version-aware routing to domain services.

• Consistent error formatting and response wrapping.

• Request identifiers for end-to-end traceability.

The gateway keeps behavior consistent across services.

What the gateway guarantees

• End-to-end request behavior: Request Flow & Data Lifecycle

• Building blocks: Core Components

• Full system view: Overall Architecture