Matrix is the intent layer of the Paxeer network. It compiles what you say into typed plans, simulates them before anything signs, and executes them on a chain built for agents.
Cortex handles understanding, the MCL runtime holds state, the bridge resolves tools, the executor settles. Each boundary is typed, each hop is logged, and the whole trace is yours.
you ─→ cortex // language → intent mcl // state, memory, session scope bridge // tools, version-pinned executor // sign + settle, chain 125 ↳ receipt on paxscan.paxeer.app
A closed verb vocabulary and a low-hallucination planner mean intents compile predictably. There is no "creative" execution path.
Spend caps, allow-lists, slippage bounds, time windows. Plans that violate them never reach a signature.
Paxeer's agent fee lane settles intents at chain speed. Agent loops re-plan inside a second.
Every executed plan is reconstructable from its IR. Disputes resolve from the record, not from memory.
Plans that fail simulation are discarded and never billed. The rate card is published and versioned on-chain.
Through Deus, an intent can hire registered services mid-plan — settled lazy-net with co-signed vouchers.
Standing intents with the scheduler precompile. Conditions watched on-chain, executed without you online.
See pricing →One API from prompt to receipt. Ship natural-language money movement without building a planner.
Read the docs →Onboard via skill.md, transact from an AgentWallet, build attestation history on Deus.
Agent docs →No. Authentication and signing happen through Paxport — ed25519 DID auth and EIP-712 signing from your own wallet. Matrix prepares plans; you (or your scoped agent session) sign them.
Plans that fail simulation are discarded before any signature exists and are never billed. Plans that fail on-chain are surfaced with the full trace and receipt for replay.
Matrix is Paxeer-native (HyperPaxeer, chain ID 125). Settlement, scheduling, streams, and attestation use chain-level precompiles that don't exist elsewhere — that's where the 400 ms loop comes from.
The current planner is selected for plan determinism and low hallucination rate, and the planner version is recorded in every IR. You can pin behavior to a rate-table and planner version.