Aradia Developer Portal and Public API | | Shipping This Week
Today we want to share that this step is essentially done. The Developer Portal, the public
API and the interactive documentation are built and running on our infrastructure. We are
finishing the final details and polishing the experience, and we will publish all three as
soon as they are ready, within this week.
What is coming
The public API exposes the NFT data Aradia indexes across Astar, through ten versioned
endpoints under /v1:
- Collections list and single collection detail.
- NFTs in a collection, and single NFT detail with metadata.
- Current ownership, and the full NFT portfolio of any wallet.
- Transfer history per collection and per token.
- Global NFT activity across Astar.
- Indexer status, with the last confirmed and last seen block.
Every response is cursor paginated, so a client can walk a full collection without the page
drift that offset pagination produces on a dataset that is still growing.
What the API will serve
These are the current figures from our production index on Astar mainnet:
- 4,969 collections indexed.
- 1,292,378 NFTs.
- 1,126,820 transfer events.
- 381,028 wallets holding at least one indexed NFT.
Those numbers are the reason we built this.
The Developer Portal
The portal is where a developer will manage their own access:
- Connect a wallet and create API keys.
- Rename, rotate and revoke keys. A secret is shown once, at creation, and never again.
- Scoped permissions per key, so a key can be limited to exactly the data it needs.
- Request history and usage, to see what an integration is actually consuming.
- Rate limit profile per key.
Documentation you can run
The documentation is generated from our OpenAPI specification, so what it describes and what the API returns cannot drift apart quietly.
Each endpoint has a console that sends a real request. To remove the friction of trying it,
the docs issue a demo token automatically, with no wallet, no registration and no form:
- Read-only scopes across collections, NFTs, owners, transfers, activity and status.
- Its own conservative rate limit, separate from real API keys.
- Short lived, and replaced automatically when it expires.
- Replaceable at any moment by your own key, if you want to test with your real limits.
The intent is that you can open the documentation and get a real response from the API
within seconds of arriving. We think that matters more than a longer feature list.
Why we are doing this
Aradia is not only a marketplace. To our knowledge we remain the only team building an
end-to-end NFT marketplace and indexing platform fully dedicated to Astar Network, and the
index behind it has value independently of our own interface.
Every new Astar project that needs NFT data faces the same choice today: build an indexer,
or do without. Building one is months of work, plus the permanent cost of keeping it correct
through reorgs, RPC failures and metadata that arrives late or never. We have already paid
that cost. Sharing it is cheaper for the ecosystem than paying it again per project.
We also keep backups of our indexed data, because a large part of Astar’s NFT history now
only exists in a readable form inside indexes like this one.
Being straight about what is not finished
We would rather state the gaps than let anyone discover them:
- The public reliability dashboard for coverage, latency and uptime is not complete. The
status endpoint is built and returns the last confirmed and last seen block, but the
coverage metric it reports is still being calibrated, and we are not going to publish a
number we do not yet trust. - Marketplace endpoints for listings, offers and sales are not part of this release. The
NFT and ownership data is. Marketplace data follows once that contract data settles. - The Aradia Astar MCP remains in development, on the timeline we described in July.
What we are asking for
If you are building on Astar and you need NFT data, we would like to hear what is missing
before we publish, not after. Concretely:
- Which endpoint you need and do not see in the list above.
- Which field you need in a response.
- Where a rate limit would get in the way of a real integration.
We would rather shape this around actual integrations than around our own guesses. If your
project needs a limit above the standard profile, tell us and we will look at it case by
case.
Next steps
August: Data infrastructure
- Public API for NFT data. Complete, publishing this week.
- Endpoints for collections, metadata, ownership and transfers:
- Wallet NFT portfolio endpoints:
- Global activity endpoint:
- Interactive API documentation: final details
- API keys, scopes, rate limits and versioning:
- Developer portal with key management and usage history: final details
- Continuous UX and performance improvements to the app: Ongoing
September: Astar MCP
- Public release of the Aradia Astar MCP, as described in our last post.
- Structured access to Astar documentation and ecosystem resources for AI agents and
developer tools. - Marketplace endpoints: listings, offers, sales and statistics.
- First public infrastructure, reliability and adoption report.
Our long-term contribution to Astar cannot be measured by trading volume alone, especially in the current NFT cycle. It should be measured by indexed assets, historical coverage, infrastructure reliability, API usage and integrations with other Astar applications. This release is the first one where that last item becomes something anyone can verify from outside.
We will post the portal, documentation and API links here the moment they go live.
See you on chain 
