API Overview
Comprehensive API reference for the MSA (Modular Smart Account) API endpoints.
Flexible APIs for Account Abstraction wallet management, transaction execution, and blockchain interactions.
Endpoint Reference
| API | Method | Description |
|---|---|---|
| Predict Wallet | POST | Predict wallet addresses before creation based on salt and custody type. |
| Create Wallet | POST | Deploy new Account Abstraction wallets on the blockchain. |
| Check Wallet | POST | Verify wallet existence and status on the blockchain. |
| Execute Operation | POST | Execute operations with human-readable parameters. |
| Execute Encoded | POST | Execute pre-encoded UserOperations. |
| Execute Passkey | POST | Execute operations with passkey validation. |
| Estimate Gas | POST | Estimate gas costs for operations before execution. |
| Read Contract | POST | Read smart contract state from the blockchain. |
| Get Receipt | POST | Get transaction receipts by transaction hash. |
| Filter Events | POST | Filter blockchain events based on specified criteria. |
| Sign Message | POST | Sign arbitrary messages with HSM/MPC keys. |
| Passkey Hash | POST | Generate passkey hashes for passkey-based operations. |
| Transact Signer | POST | Execute direct HSM/MPC transactions. |
| Unstuck Transaction | POST | Resolve stuck transactions. |
| Add Event ABI | POST | Add custom event ABIs to the system. |
| Add Error ABI | POST | Add custom error ABIs to the system. |
Authentication
All API endpoints require authentication using HSM/MPC credentials. Authentication is configured through the signer object in request settings.
Signer Configuration
The signer object requires a clientId and either a versionId (for HSM) or assetId (for MPC):
HSM Configuration:
{
"signer": {
"clientId": "your-fireblocks-client-id",
"versionId": "1"
}
}MPC Configuration:
{
"signer": {
"clientId": "your-fireblocks-client-id",
"assetId": "ETH"
}
}Please contact the MSA team for HSM/MPC credentials and API access.
Base URL
All API requests should be made to:
https://api.msa.omnes.techRate Limits
The MSA API implements rate limiting to ensure fair usage:
| Tier | Requests per Minute | Requests per Hour |
|---|---|---|
| Free | 60 | 1,000 |
| Pro | 300 | 10,000 |
| Enterprise | 1,000 | 50,000 |
Error Codes
Common HTTP status codes and their meanings:
| Code | Status | Description |
|---|---|---|
| 200 | OK | Request successful |
| 400 | Bad Request | Invalid request parameters |
| 401 | Unauthorized | Invalid authentication credentials |
| 422 | Unprocessable Entity | Request valid but execution failed |
| 429 | Too Many Requests | Rate limit exceeded |
| 500 | Internal Server Error | Server-side error |
Supported Networks
| Network | Chain ID | RPC Endpoint |
|---|---|---|
| Polygon Amoy (Testnet) | 80002 | https://rpc-amoy.polygon.technology/ |
| Polygon Mainnet | 137 | https://polygon-rpc.com/ |
| Base Sepolia (Testnet) | 84532 | https://sepolia.base.org/ |
| Base Mainnet | 8453 | https://mainnet.base.org/ |
Interactive Documentation
For a complete interactive experience with all endpoints, request/response schemas, and the ability to test API calls directly in your browser, visit the Interactive API Documentation.
Quick Links
🔮 Predict Wallet
Calculate wallet addresses before deployment
🏦 Create Wallet
Deploy Account Abstraction wallets
⚡ Execute Operation
Execute transactions with human-readable parameters
🔧 Interactive Docs
Try endpoints directly in your browser
🚀 Ready to Get Started? Check out our Quick Start Guide or explore the Interactive API Documentation.