canonical: https://jentic.com/apis/swaggerhub.prx-enco/blockchain-management-api

# Prx Enco Blockchain Management API

The Blockchain Management API provides endpoints to manage your (fuel) wallets and smart contracts. Besides that it also provides endpoints to retrieve transaction information. The API exposes 35 endpoints.

## For AI agents

Programmatically autocomplete resource for chains, autocomplete resource for contracts. Covers 35 operations.

## Scope

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

## Capabilities

- Autocomplete resource for chains
- Retrieve available chains
- Deploy/import a smart contract
- Query and filter Blockchain Management API records by parameters
- Monitor Blockchain Management API operational status and events

## Use cases

### Payments Operations

Use the Blockchain Management API to perform payments operations programmatically. The API provides 35 endpoints covering core functionality including autocomplete resource for chains, autocomplete resource for contracts, autocomplete resource for contract methods.

Example prompt: Call GET `/autocomplete/chains` to autocomplete resource for chains

### Automated General Management

Automate general operations by combining multiple Blockchain Management API endpoints. Agents can autocomplete resource for contracts and then autocomplete resource for contract methods in a single workflow.

Example prompt: Call GET `/autocomplete/chains/{chainId}/contracts` to autocomplete resource for contracts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Blockchain Management API 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 none tokens manually.

Example prompt: Search Jentic for 'autocomplete resource for chains', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/autocomplete/chains` | Autocomplete resource for chains |
| GET | `/autocomplete/chains/{chainId}/contracts` | Autocomplete resource for contracts |
| GET | `/autocomplete/chains/{chainId}/contracts/{contractName}/methods` | Autocomplete resource for contract methods |
| GET | `/autocomplete/chains/{chainId}/wallets` | Autocomplete resource for wallets |
| GET | `/chains` | Retrieve available chains |
| POST | `/chains/{chainName}/contracts` | Deploy/import a smart contract |
| GET | `/chains/{chainName}/contracts` | Retrieve all your contracts on a chain |
| GET | `/chains/{chainName}/contracts/{contractName}` | Retrieve a specific contract |

## Key resources

- **General** — General endpoints
- **Wallets** — Endpoints to manage your wallets and make transfers
- **Contracts** — Endpoints to manage your smart contracts and make invocations on them
- **Block explorer** — Endpoint to retrieve info about a certain transaction, address or block
- **Autocomplete** — Endpoints to support autocompletion on the chains, wallets and contracts for the requested user

## Why Jentic

- **Setup:** Wiring the Blockchain Management API by hand means pointing your client at the `/bc-mgmt/1.0.0` base path and handling its chain, contract, and wallet endpoints yourself. Through Jentic you install once, import Blockchain Management API from the API Directory, 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 read contracts and wallets on that chain and nothing else. You choose the operations it may call, so movement of funds like a wallet transfer is not included unless you add it.
- **Credential handling:** This API requires no credential, so there is nothing for your own Jentic One instance to store. When you later add an authenticated endpoint, its secret is stored once, encrypted, and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list contracts on a blockchain' or 'look up a wallet on a chain', and Jentic returns the matching Blockchain Management API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Blockchain Management API use?

The Blockchain Management API uses no authentication. 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 autocomplete resource for chains with the Blockchain Management API?

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

### What are the rate limits for the Blockchain Management API?

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 autocomplete resource for chains through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'autocomplete resource for chains'. Jentic returns the matching Blockchain Management API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Blockchain Management API have?

The Blockchain Management API exposes 35 endpoints covering general, wallets, contracts operations.

### Can I limit what my agent is allowed to do with the Blockchain Management API?

Yes. Because Jentic One is self-hosted, your own rules decide which Blockchain Management API operations and credentials the agent can use. Since this API carries the chain name in the URL path (`/chains/{chainName}/...`), you can pin the agent to a single chain and allow only read operations such as retrieving contracts and wallets on that chain. Fund-moving calls like a wallet transfer stay off-limits unless you explicitly add them to the agent's allowed operations.