A Move L1 with the indexer and oracle already in the network.
Indexer, oracle and cross-chain messaging are part of the network, not three more vendors to integrate. We are also building a model router on top, with a budget for every agent, so your onchain agents will get models and chain data from one stack.
# Balances and recent transactions for one account
query AccountActivity($owner: String) {
balances(
where: { owner: { _eq: $owner } }
) { asset amount }
transactions(
where: { sender: { _eq: $owner } }
limit: 20
) { version timestamp success }
}Move, parallel execution, fast finality.
Cedra runs the Move VM with Block-STM parallel execution and its own BFT consensus, so independent transactions do not wait for each other.
- Designed throughput
- 10k+TPS
- Designed finality
- <1s
- Execution
- Block-STMparallel
Design targets from the Cedra architecture docs.
-
Linear types for assets
Built inResources cannot be copied or dropped by accident. Bring what you know from other Move chains.
-
Your own network inside the network
Built inDeploy a sub-network with its own gas economics, validator set and governance when your app needs it.
Less integration work before your first user.
The pieces most dApps rent from third parties come with the chain, so your app does not depend on a provider deciding to support it.
Usually you integrate
- Chain datathird-party indexer
- Randomnessexternal oracle
- Other chainsseparate bridge protocol
- AI models for agentsseparate router and keys
On Cedra
- Indexer, GraphQLbuilt into the chain
- Oracle, VRF randomnessbuilt into the chain
- Cross-chain messagingbuilt into the chain
- Models with a limit per agentin development
Wallets, DeFi, NFT, an explorer and security teams already list themselves on Cedra. Projects on Cedra →
Onchain agents need models too.
We are building a model router into the Cedra stack: one API for frontier and open-source models, with a budget for every agent.
Cedra for AI agents →-
A key and a limit per agent
PlannedEach agent will get its own key and spending limit, so one agent cannot drain the shared balance.
-
Models and chain data together
In developmentYour agent will reason with frontier and open-source models through one API and read the chain through the same stack. Our goal: every model served directly by its provider, not a reseller.
What Move developers ask first.
I already write Move. How much changes?
Cedra runs the Move VM, so the language and mental model carry over. Check the docs for framework and tooling differences before porting.
Do I need a separate indexer?
No. Cedra ships an indexer with a GraphQL API for balances, NFTs and transaction history.
What does the oracle provide?
Verifiable randomness is built in today. See the docs for the current list of data the oracle supports.
Can I run my own network?
Yes. Sub-networks let a project run with its own gas economics, validators and governance.
When can my agents use models through Cedra?
It is in development. Join the early access list and you will get a key when your wave opens.
Get an early key. We invite in waves.
The router is in development. We will let developers in by waves, as many as we can onboard by hand. Tell us what hurts most and we will use it to decide who goes first.
- An API key before public launch
- Beta access to per-agent keys and spending limits as they ship
- A say in which models and providers we add first
What happens after you sign up. We read your answers and place you in a wave. When your wave opens, you will get an email with your key and a quickstart. Waves are small on purpose, so each group gets real attention from the team. We do not have wave dates yet.