canonical: https://jentic.com/apis/azure.com/blockchain-management-client # Microsoft Azure BlockchainManagementClient Jentic publishes the only available OpenAPI specification for BlockchainManagementClient, keeping it validated and agent-ready. The Azure Blockchain Service management API provisions blockchain members and transaction nodes that participate in a managed Quorum or Ethereum-like consortium. It exposes lifecycle, key listing, and key regeneration operations for both members and transaction nodes, plus consortium discovery and SKU listings to plan deployments. ## For AI agents Provision Azure Blockchain members and transaction nodes, manage their API keys, and discover consortiums for managed ledger deployments. ## Scope Does not submit transactions, deploy smart contracts, or query ledger state - use for blockchain member and transaction node lifecycle management only. ## Capabilities - Provision and tear down blockchain members within a consortium across regions - Provision additional transaction nodes attached to a blockchain member - List and regenerate the API keys for a blockchain member or transaction node - Enumerate consortium members visible to a given blockchain member - List consortiums available in a region for joining or onboarding - Check name availability and list SKUs prior to creating a member ## Use cases ### Spin up a private consortium Enterprise teams provision their first blockchain member with BlockchainMembers_Create after running Locations_CheckNameAvailability and Skus_List. Once the member is online, BlockchainMembers_ListApiKeys returns the credentials a backend service uses to submit transactions, with regeneration available through the regenerate endpoint when keys need to rotate. Example prompt: Run Locations_CheckNameAvailability for 'fintech-member-eu', then BlockchainMembers_Create with consortium settings, then BlockchainMembers_ListApiKeys to retrieve credentials ### Scale out transaction throughput When a single transaction node becomes a bottleneck, ops teams add additional nodes via TransactionNodes_Create under the existing blockchain member. Each node has its own API key set, returned by TransactionNodes_ListApiKeys, that can be load-balanced from the application tier for higher transaction throughput. Example prompt: Call TransactionNodes_Create on the existing blockchain member, then TransactionNodes_ListApiKeys to register the node in the load balancer ### Key rotation after a leak Security incident response involves rotating both the blockchain member and transaction node API keys. BlockchainMembers_ListRegenerateApiKeys and TransactionNodes_ListRegenerateApiKeys mint new key pairs in place, after which clients are reconfigured. This is the only path to invalidate keys without redeploying the member. Example prompt: Call BlockchainMembers_ListRegenerateApiKeys for the affected member, then update each transaction node by calling TransactionNodes_ListRegenerateApiKeys ### AI agent integration via Jentic A blockchain ops agent uses Jentic to manage members and transaction nodes without learning ARM. The agent searches Jentic for 'provision an Azure Blockchain member', loads BlockchainMembers_Create, and executes with structured input. Jentic mints AAD tokens against management.azure.com so the agent never holds the underlying credential. Example prompt: Use Jentic search 'provision an Azure Blockchain member', load BlockchainMembers_Create, and execute ## Key endpoints | Method | Path | Description | | --- | --- | --- | | PUT | /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Blockchain/blockchainMembers/{blockchainMemberName} | Create or update a blockchain member | | POST | /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Blockchain/blockchainMembers/{blockchainMemberName}/listApiKeys | List API keys for a blockchain member | | POST | /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Blockchain/blockchainMembers/{blockchainMemberName}/regenerateApiKeys | Regenerate API keys for a blockchain member | | PUT | /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Blockchain/blockchainMembers/{blockchainMemberName}/transactionNodes/{transactionNodeName} | Create or update a transaction node | | POST | /subscriptions/{subscriptionId}/providers/Microsoft.Blockchain/locations/{locationName}/checkNameAvailability | Check whether a blockchain member name is available | | POST | /subscriptions/{subscriptionId}/providers/Microsoft.Blockchain/locations/{locationName}/listConsortiums | List consortiums available in a region | ## Key resources - **BlockchainMembers** — Top-level blockchain member resource - supports list, get, create, update, delete plus key listing and regeneration. - **TransactionNodes** — Additional transaction nodes under a blockchain member - supports list, get, create, update, delete plus key listing and regeneration. - **Locations** — Region-scoped operations - name availability checks and consortium discovery. - **Skus / Operations / OperationResults** — SKU enumeration, resource provider operations, and async operation result polling. ## Why Jentic - **Setup:** Wiring the BlockchainManagementClient by hand means setting up Azure AD OAuth2 against management.azure.com, handling long-running provisioning for members and nodes, and threading blockchain member and transaction node ids through every Microsoft.Blockchain path yourself. Through Jentic you install once, import the BlockchainManagementClient from the API Directory, store the Azure AD credential once, and your agent calls it. - **Permission scoping:** This API puts the member and transaction node ids in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Blockchain/blockchainMembers/{blockchainMemberName}/transactionNodes/{transactionNodeName}), so a rule can pin your agent to one blockchain member and its nodes. You choose the operations it may call, so sensitive ones like listing or regenerating API keys are not included unless you add them. - **Credential handling:** Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'provision an Azure Blockchain member' or 'add a transaction node', and Jentic returns the matching BlockchainMembers or TransactionNodes operation with its input schema so the agent calls the right ARM path without browsing the Microsoft.Blockchain reference. ## Related APIs - **Azure Deployment Manager** — Coordinates staged rollouts of resources, including blockchain members across regions. - **Azure Resource Management** — ARM is the underlying control plane that hosts Microsoft.Blockchain resources. - **Azure Compute Management** — For self-hosted blockchain nodes on plain VMs rather than the managed service. ## FAQ ### Why is there no official OpenAPI spec for BlockchainManagementClient? Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call BlockchainManagementClient via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the BlockchainManagementClient API use? The API uses Azure Active Directory OAuth 2.0 declared as azure_auth with the implicit flow. Tokens are presented as Bearer headers against management.azure.com. Through Jentic, the AAD client secret stays in the vault and only short-lived scoped tokens reach the agent. ### Can I submit transactions to a blockchain with this API? No. This API manages the lifecycle of blockchain members and transaction nodes plus their API keys. Submitting transactions, deploying smart contracts, and querying ledger state happens against the transaction node's RPC endpoint using the API keys returned by ListApiKeys, not through this management API. ### What are the rate limits for the BlockchainManagementClient API? Azure Resource Manager applies subscription-level throttling, typically 12,000 read and 1,200 write requests per hour, surfaced via x-ms-ratelimit-remaining headers. The Blockchain management API does not document additional limits beyond ARM. ### How do I provision a blockchain member through Jentic? Run pip install jentic, then use the async client to search 'provision an Azure Blockchain member', load BlockchainMembers_Create, and execute with subscriptionId, resourceGroupName, blockchainMemberName, and a body specifying the consortium and protocol. Jentic returns the operation result so you can poll Operations_Get. ### Is Azure Blockchain Service still accepting new deployments? Microsoft retired Azure Blockchain Service in September 2021. The API and OpenAPI spec remain useful for managing existing deployments and for integration testing, but new deployments cannot be created on the public service. ### Can I limit what my agent is allowed to do with the Microsoft Azure Blockchain API? Yes. Because you run Jentic One yourself, your own rules decide which operations the agent may call, so you can allow lifecycle calls like BlockchainMembers_Create or TransactionNodes_Create while withholding sensitive ones such as BlockchainMembers_ListApiKeys or the regenerate-key operations. Since this API carries the member and transaction node ids in the URL path, you can pin the agent to a single blockchain member and its nodes rather than your whole subscription. The Azure AD credential is stored by your instance and injected only at execution time, so the agent never sees the underlying secret.