Community FAQ
Quick answers to common community questions. Each item expands with details.
Product and platform
What problem does Acceso solve?
Acceso removes the need to manage multiple RPCs, indexers, and protocol-specific APIs. It provides a unified, normalized data infrastructure for Solana and related ecosystems.
Is Acceso suitable for production systems?
Yes. Acceso is designed with rate limits, fault tolerance, observability, and strict access controls suitable for production workloads.
Is Acceso “just another data API”?
No. Acceso is a data infrastructure layer that combines APIs, real-time systems, analytics, micropayments, and privacy primitives under one architecture.
Does Acceso store the full blockchain?
No. Acceso persists derived, indexed, and operational data needed for performance and reliability.
How do I authenticate?
Acceso uses API keys for machine-to-machine authentication. Keys are validated at request entry before any domain work runs.
How do I get an API key?
Use the Acceso Dashboard to create a key for your environment. Keys are shown once at creation time.
Does Acceso support real-time updates?
Yes. Acceso supports real-time systems such as streaming and event notifications.
How do rate limits and quotas work?
Limits are enforced at the gateway. They are tied to your API key policy and plan tier.
How do you handle data freshness and upstream failures?
Upstreams can degrade or fail. Acceso uses validation, caching, and resilience controls to keep behavior predictable.
What should I do if I see errors or downtime?
Check the system status first. If the issue persists, contact support with a timestamp and request identifiers when available.
Token
Do I need to hold the token to use Acceso?
No. Core API access does not require holding $ACCESO. The token enhances access and benefits but does not gate basic functionality.
Why launch the token on Pump.fun?
Pump.fun provides a decentralized, permissionless launch environment with strong on-chain visibility. It supports organic discovery without aggressive paid marketing.
How do you reduce “rug” or misuse concerns?
The developer allocation is 100% locked for one year, publicly verifiable. Platform behavior and transparent on-chain artifacts matter more than promises.
Coverage and expansion
Will Acceso support chains beyond Solana?
The architecture is multi-chain capable. Expansion will happen only when quality and reliability can be maintained.
How do you decide what to support next?
We prioritize based on usage signals, reliability constraints, and integration pain points. We prefer additions that unlock multiple use cases.
Community and communication
Where should I send feedback or feature requests?
Use the feedback channel listed in the official contact details. Include your use case and expected request/response shape when possible.
What information helps you debug issues fastest?
Share:
Approximate timestamp.
Endpoint or feature area.
Request identifier (if returned).
Expected vs actual outcome.
Last updated