Integrate AIERC
Connect your platform.
Choose where your platform needs intelligence: its own transaction flow, a network admission point, a protected wallet RPC or the browser connection.
Connect your existing platform
Keep what you've built.
Add intelligence.
Your project keeps its brand and its customer relationships. Choose the connection that fits where your transactions happen.
Applications & marketplaces
Use supported APIs and application integrations to evaluate a proposal before acting. Bring the findings into a branded POS so customers understand the decision.
Networks & private chains
Integrate the Admission SDK into the network's block-building path. Hold a covered transaction for its determination while other eligible transactions continue.
Wallets & existing assets
Use the protected RPC route to examine signed transactions before broadcast. AIERC-XT provides a separate protection point at malicious browser wallet connections.
Native protected tokens
Build AIERC protection into supported token transfers. The mint gate adds a separate check at creation, before deployment through the designated factory.
Choose the control point your project needs
Application integration
An application submits the proposal and relevant authority, receives a determination and applies it before its supported action. Bind the result to the exact recipient, amount, chain and material action fields. A changed transaction cannot reuse an old clearance.
Network admission
The Admission SDK supplies classification and a determination gate for a cooperating network's block-building path. The network integrates the adapter, policy state and record handling with its execution client. It retains its own settlement and block production.
This is an integration package, not a universal one-click change to every external blockchain. The evaluation engine remains a hosted off-chain service. The delivered SDK does not expose the proprietary determination logic.
Wallet RPC and browser extension
The protected RPC evaluates the signed transaction before forwarding it. It does not change custody, alter the signed bytes or guarantee a separate approval prompt for every send. AIERC-XT is the separate malicious wallet-connection refusal point; that refusal is not configurable by the user.
Native protocol and mint gate
AIERC-protected tokens carry a determination requirement in supported transfer operations, with the applicable holder controls. The mint gate evaluates the specified contract before factory deployment and ties creation provenance to the evaluated bytes.
A creation-time assessment does not automatically install protected-transfer behavior in arbitrary contracts. A generic contract-creation flag is not a mint-gate security review.
Infrastructure
Chaingentic uses an EVM execution environment with a Polygon CDK-derived validium design. Execution, proof systems, data availability and production settlement must each be verified separately. A running test chain is not proof that the complete production rollup stack is operating.
Source-visible components may use BUSL-1.1. Visibility on an explorer does not mean every component is open source or that the off-chain engine is included.
Optional project conversation
Tell us what you're building.
Use this optional form to discuss your project or ask for integration and platform-delivery help.