Prx Enco Blockchain-as-a-Service Application Programming Interface

Setup

Wiring the Blockchain-as-a-Service Application Programming Interface by hand means running the OAuth2 client-credentials flow against api.enco.io/token, managing token refresh, and calling the chain and node endpoints at api.enco.io yourself. Through Jentic you install once, import Blockchain-as-a-Service Application Programming Interface from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

This API puts the chain name in the URL path (/chains/{chainName}/...), so a rule can pin your agent to one chain: it can create and read nodes on that chain and nothing else. You choose the operations it may call, so destructive ones like deleting a chain or replacing a node are not included unless you add them.

Credential isolation

Your Blockchain-as-a-Service client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a new blockchain' or 'add a node to a chain', and Jentic returns the matching Blockchain-as-a-Service operation with its input schema so the agent calls the right endpoint without browsing the reference docs.