
Overview
Acceso is a full-stack blockchain data and infrastructure platform. It standardizes how developers, applications, and autonomous systems access Solana and adjacent on-chain markets.
Acceso is a unified access layer over RPC, indexing, protocol adapters, and real-time delivery. You integrate once, then query a consistent schema across services.
Acceso is infrastructure, not a one-off tool. It is built around stable interfaces, operational safety, and long-term extensibility.
Why Acceso exists
Production Solana systems typically require:
Multiple RPC providers and failover logic
Indexers and backfills for accounts, tokens, and transactions
Protocol-specific APIs for trades, liquidity, and routing
Price aggregation across fragmented sources
Custom real-time listeners, alerting, and delivery guarantees
Separate layers for auth, quotas, metering, and observability
Acceso consolidates these responsibilities into one platform. Teams spend time on product logic, not maintaining data plumbing.
What Acceso provides
Acceso provides:
Unified Solana data APIs Normalized endpoints for accounts, balances, tokens, transactions, DEX trades, and OHLCV market data.
DeFi analytics layer Protocol-agnostic analytics across Raydium, Orca, Jupiter, and Pump.fun. Includes liquidity, swaps, and launch activity.
Prediction market integration Structured access to Polymarket markets, pricing, orderbooks, trades, and historical data.
Real-time systems WebSocket streams and webhook alerts for low-latency updates and event-driven workflows.
SDK ecosystem TypeScript and Python SDKs aligned with API resources. Includes typed interfaces, retries, and batching.
Payment-aware API infrastructure Optional HTTP-402-style micropayment flows for programmatic and agent-driven API consumption.
Privacy & verification layer Zero-knowledge proof services for verifiable computation and data validation without exposing sensitive inputs.
Who Acceso is built for
Acceso is used by:
Solana application developers
Trading systems and execution bots
AI agents and autonomous workflows
Analytics platforms and dashboards
Teams operating high-throughput and latency-sensitive systems
It scales from local prototypes to production deployments with strict reliability requirements.
Design principles
Acceso is built around a small set of principles:
Unified access One API key, one schema, and consistent behavior across services.
Production reliability Rate limiting, caching, failover strategies, observability, and structured errors are first-class.
Modular architecture Solana, DeFi, Polymarket, ZK, payments, and notifications can evolve without breaking consumers.
Future-ready infrastructure Designed for agent-driven usage, pay-per-call access, and privacy-preserving verification.
How to use this documentation
Use this documentation in two modes:
Orientation: start with platform concepts and system design.
Implementation: use the API, SDK, WebSocket, and webhook references.
Most sections are implementation-first. Expect concrete parameters, error behavior, and operational notes.
Getting started
To begin using Acceso:
Create an account at
https://acceso.devGenerate an API key from the dashboard
Store the key as a secret in your environment
Choose your integration surface (REST, SDK, WebSocket, webhooks)
Start building against the unified API
The following sections break down every part of the platform in detail.
Last updated