canonical: https://jentic.com/apis/swaggerhub.prx-enco/blockchain-as-a-service-application-programming-in

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

swaggerhub.prx-enco/blockchain-as-a-service-api version 2.0.0. The API exposes 20 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically creates a new chain, retrieves a list of chains you have access to.. Covers 20 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Creates a new chain
- Retrieves a list of chains you have access to.
- Deletes the chain. Requires the chain to have no more nodes. This is irreversibl
- Adds a new customized node to the chain
- Monitor Blockchain-as-a-Service Application Programming Interface operational status and events

## Use cases

### Developer Tools Operations

Use the Blockchain-as-a-Service Application Programming Interface to perform developer tools operations programmatically. The API provides 20 endpoints covering core functionality including creates a new chain, retrieves a list of chains you have access to., retrieves info about a given chain.

Example prompt: Call POST /chains to creates a new chain

### Automated Chain management Management

Automate chain management operations by combining multiple Blockchain-as-a-Service Application Programming Interface endpoints. Agents can retrieves a list of chains you have access to. and then retrieves info about a given chain in a single workflow.

Example prompt: Call GET /chains to retrieves a list of chains you have access to., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Blockchain-as-a-Service Application Programming Interface endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'creates a new chain', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/chains` | Creates a new chain |
| GET | `/chains` | Retrieves a list of chains you have access to. |
| GET | `/chains/{chainName}` | Retrieves info about a given chain |
| DELETE | `/chains/{chainName}` | Deletes the chain. Requires the chain to have no more nodes. This is irreversibl |
| POST | `/chains/{chainName}/nodes` | Adds a new customized node to the chain |
| GET | `/chains/{chainName}/nodes` | Retrieves a list of current nodes |
| GET | `/chains/{chainName}/nodes/{nodeName}` | Retrieves information about a given node |
| PUT | `/chains/{chainName}/nodes/{nodeName}` | Updates the given node |

## Key resources

- **Chain management** — Adding or removing chains
- **Node management** — Adding, removing and editing nodes
- **Voting** — Voting on various actions
- **Notifications** — Retrieving notifications
- **Block explorer** — Retrieving info regarding the blocks in the blockchain

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Blockchain-as-a-Service Application Programming Interface use?

The Blockchain-as-a-Service Application Programming Interface uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I creates a new chain with the Blockchain-as-a-Service Application Programming Interface?

Yes. Use the POST /chains endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Blockchain-as-a-Service Application Programming Interface?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I creates a new chain through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'creates a new chain'. Jentic returns the matching Blockchain-as-a-Service Application Programming Interface operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Blockchain-as-a-Service Application Programming Interface have?

The Blockchain-as-a-Service Application Programming Interface exposes 20 endpoints covering chain management, node management, voting operations.

### Can I limit what my agent is allowed to do with the Blockchain-as-a-Service API?

Yes. Jentic One is self-hosted, so you set the rules that decide which operations and credentials your agent may use. Because this API puts the chain name in the URL path (`/chains/{chainName}/...`), you can pin the agent to a single chain and allow only the calls you want, such as creating and reading nodes with POST and GET `/chains/{chainName}/nodes.` Destructive operations like DELETE `/chains/{chainName}` or updating a node with PUT are excluded unless you explicitly add them.