canonical: https://jentic.com/apis/amazonaws.com/managedblockchain # AWS Amazon Managed Blockchain Jentic publishes the only available OpenAPI specification for Amazon Managed Blockchain, keeping it validated and agent-ready. Amazon Managed Blockchain is a fully managed service for creating and operating blockchain networks built on open-source frameworks such as Hyperledger Fabric and read access to Ethereum. The control plane covers networks, members, peer nodes, proposals, voting, accessor tokens, and tag management. It removes the operational burden of provisioning ordering services, certificate authorities, and peer nodes so teams can focus on chaincode and application logic. ## For AI agents Provision and operate Hyperledger Fabric blockchain networks, manage members, peer nodes, and governance proposals through one API. ## Scope Does not handle smart contract execution, wallet management, or token transfers - use for blockchain network, member, node, and governance provisioning only. ## Capabilities - Create Hyperledger Fabric blockchain networks with configurable framework and edition - Invite members to a network through governance proposals and votes - Provision and update peer nodes with chosen instance types and availability zones - Submit and vote on proposals for network membership and configuration changes - Issue accessor tokens that grant signed access to Ethereum nodes for read calls - List and inspect networks, members, nodes, proposals, and invitations across regions - Tag networks and resources for cost allocation and access control ## Use cases ### Supply Chain Consortium Network Manufacturers, logistics partners, and retailers stand up a permissioned Hyperledger Fabric network on Managed Blockchain to share traceability records. The API creates the network, admits each partner as a member through governance proposals, and provisions peer nodes per organization. AWS handles ordering services, certificate authorities, and node patching so the consortium owns only the chaincode and integration code. Example prompt: Call CreateNetwork with FRAMEWORK=HYPERLEDGER_FABRIC and STARTER edition, then create a member for our organization with an admin user, and provision a single peer node in us-east-1a ### Decentralised Application Backend dApp teams use Managed Blockchain accessors to issue read-only access tokens for Ethereum mainnet and testnets without running their own nodes. CreateAccessor returns a billing token used to authorise JSON-RPC read calls; the API also handles listing and revoking accessors. This pattern offloads node operations and lets the agent focus on transaction crafting via wallets external to AWS. Example prompt: Call CreateAccessor with AccessorType=BILLING_TOKEN, then list current accessors and return the active token for use against Ethereum read endpoints ### Network Governance Workflows Consortium operators use proposal and voting endpoints to admit or remove members, change configuration, and audit decisions. CreateProposal opens the vote, ListProposals shows open and closed items, and VoteOnProposal records each member's choice. All actions are tagged with members and timestamps so the consortium has an audit trail of governance. Example prompt: List open proposals on the network, then vote YES on a specific ProposalId on behalf of MemberId m-ABC123 ### AI Agent Blockchain Operations AI agents use Managed Blockchain through Jentic to provision nodes, monitor network status, and execute governance actions on behalf of operators. Jentic isolates AWS Signature v4 credentials in the vault and exposes the network, member, node, and proposal operations as discoverable tools so the agent can answer 'add a peer node in eu-west-1' without learning the AWS SDK. Example prompt: Search Jentic for 'create a blockchain peer node', load the CreateNode operation, and execute it for NetworkId n-NET123 and MemberId m-MEM123 with an InstanceType of bc.t3.medium in availability zone eu-west-1a ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /networks | Create a new blockchain network | | POST | /networks/{networkId}/members | Create a member within a network | | POST | /networks/{networkId}/members/{memberId}/nodes | Create a peer node for a member | | POST | /networks/{networkId}/proposals | Create a governance proposal | | POST | /networks/{networkId}/proposals/{proposalId}/votes | Vote on a proposal | | GET | /networks/{networkId} | Describe a blockchain network | | POST | /accessors | Create an Ethereum accessor token | ## Key resources - **Networks** — Create, describe, list, and delete blockchain networks - **Members** — Manage member organizations within a Hyperledger Fabric network - **Nodes** — Provision, list, update, and delete peer nodes for a member - **Proposals** — Create, list, and vote on governance proposals - **Invitations** — Accept or reject invitations to join a network - **Accessors** — Manage billing tokens for Ethereum read access ## Why Jentic - **Setup:** Wiring Managed Blockchain by hand means implementing AWS SigV4 signing, targeting the regional host such as managedblockchain.us-east-1.amazonaws.com, and building your own polling for asynchronous network, member, and node readiness. Through Jentic you install once, import Amazon Managed Blockchain from the API Directory, store the AWS access key once, and your agent calls it. - **Permission scoping:** Managed Blockchain puts the network id in the URL path (/networks/{networkId}/...), so a rule can pin your agent to one network: it can create members, nodes, and proposals for that network and nothing else. You choose the operations it may call, so destructive ones like network or node deletion are not included unless you add them. - **Credential handling:** Your AWS access key is stored once, encrypted, by your own Jentic One instance and used to sign each Managed Blockchain request with SigV4 at execution time. The raw secret never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a blockchain peer node' or 'vote on a governance proposal', and Jentic returns the matching Managed Blockchain operation such as CreateNode with its input schema so the agent calls the right endpoint without browsing the AWS reference. ## Related APIs - **Amazon QLDB Session** — QLDB is a centralized immutable ledger; Managed Blockchain is multi-party - **Alchemy** — Alchemy provides hosted Ethereum node access; Managed Blockchain accessors do similar for AWS-hosted workloads - **Amazon CloudWatch** — CloudWatch ingests peer node logs and metrics from Managed Blockchain ## FAQ ### Why is there no official OpenAPI spec for Amazon Managed Blockchain? AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Managed Blockchain 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 Amazon Managed Blockchain API use? The control-plane API uses AWS HMAC request signing (Signature Version 4) with an access key ID and secret access key scoped via IAM. Through Jentic, AWS credentials sit in the encrypted vault and are signed into each request server-side, so the agent only handles short-lived scoped sessions. ### Can I provision peer nodes with the Amazon Managed Blockchain API? Yes. POST /networks/{networkId}/members/{memberId}/nodes creates a peer node with a chosen InstanceType (e.g. bc.t3.medium) and AvailabilityZone. GET on the same path lists existing nodes; the per-node DescribeNode endpoint returns status, framework attributes, and logging configuration. ### What are the rate limits for the Amazon Managed Blockchain API? AWS does not document per-second request limits for Managed Blockchain control-plane operations in the public spec. Instead, soft quotas apply to the number of networks, members per network, and nodes per member. Check the AWS service quotas console for current limits in your region. ### How do I create a governance proposal through Jentic? Search Jentic for 'create a blockchain proposal' to surface POST /networks/{networkId}/proposals. Load the schema with the Jentic SDK (pip install jentic), then execute it with the proposing MemberId and the Actions object describing the change. Use VoteOnProposal to record subsequent votes. ### Is Amazon Managed Blockchain free? No. Managed Blockchain charges per member per hour, per peer node by instance hours, and for data written and storage on the network. There is no free tier - see the AWS Managed Blockchain pricing page for current rates by framework and edition. ### Can I limit what my agent is allowed to do with the Amazon Managed Blockchain API? Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. Managed Blockchain carries the network id in the URL path (/networks/{networkId}/...), so a rule can pin the agent to a single network where it can create members, nodes, and proposals and nothing outside it. You choose the exact operations it may call, so destructive ones such as network or node deletion are excluded unless you explicitly add them.