azeth_update_service_batch
Batch update up to 5 metadata fields (endpoint, description, capabilities, etc.) for your registered service in a single call.
Instructions
Update multiple metadata fields for your registered service in one call.
Use this when: You need to change several metadata fields at once (e.g., endpoint + description + capabilities).
Supported metadata keys: "endpoint", "description", "capabilities", "name", "entityType", "pricing". For capabilities, provide a JSON array string (e.g., '["translation", "nlp"]').
Note: Catalogs are off-chain. Update your catalog by updating your endpoint response.
Returns: Confirmation with the final transaction hash.
Note: On the current (v1.3) contracts the updates execute as SEQUENTIAL transactions, not atomically — the deployed GuardianModule cannot validate batch UserOperations. If an update fails midway, the error reports how many updates already landed. Maximum 5 key-value pairs per batch.
Example: { "updates": [{"key": "endpoint", "value": "https://api.example.com/v2"}, {"key": "description", "value": "Updated service"}] }
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | Target chain. Defaults to AZETH_CHAIN env var or "baseSepolia". Accepts "base", "baseSepolia", "ethereumSepolia", "ethereum" (and aliases like "base-sepolia", "eth-sepolia", "sepolia", "eth", "mainnet"). | |
| updates | Yes | Array of {key, value} pairs to update. Max 5 updates per batch. |