canonical: https://jentic.com/apis/nebl.io/neblio

# Nebl Neblio REST API Suite

Neblio publishes the canonical OpenAPI document for this suite itself, in the NeblioTeam swagger-docs repository on GitHub, and the Jentic entry was imported from that document. The Neblio REST API Suite exposes 50 endpoints for interacting with the Neblio blockchain and NTP1 tokens, covering token issuance, transfer and burn, address and transaction lookup, raw transaction broadcast, block exploration, and node-level controls. The suite combines NTP1-specific helpers under /ntp1 with a Bitcoin-style /ins explorer interface, allowing developers to issue custom assets, query holders, and broadcast signed transactions against ntp1node.nebl.io.

## For AI agents

Issue, transfer, and burn NTP1 tokens on the Neblio blockchain, look up addresses and transactions, and broadcast signed transactions.

## Scope

Does not custody private keys, host wallets, or provide fiat on-ramps - use for Neblio NTP1 and chain-data operations only.

## Capabilities

- Issue new NTP1 tokens with `/ntp1/issue` and a custom symbol and metadata
- Send and burn NTP1 tokens through `/ntp1/sendtoken` and `/ntp1/burntoken`
- Look up token metadata and stakeholders via `/ntp1/tokenmetadata` and `/ntp1/stakeholders`
- Inspect Neblio addresses, balances, and transactions through the /ins explorer endpoints
- Broadcast signed raw transactions with `/ntp1/broadcast` and `/ins/tx/send`
- Resolve token symbols to token ids using `/ntp1/tokenid/{tokensymbol}`

## Use cases

### Custom Asset Issuance on Neblio

A token issuer mints a new NTP1 asset by submitting an issuance request with the desired symbol, supply, divisibility, and metadata. The Neblio REST API builds the unsigned transaction, the issuer signs it locally, then broadcasts it via `/ntp1/broadcast.` The new token id is then queryable via `/ntp1/tokenid` for downstream wallets and exchanges.

Example prompt: POST `/ntp1/issue` with symbol, amount, issueAddress, and metadata, sign the returned transaction hex, then POST `/ntp1/broadcast` with the signed transaction.

### Token Holder Snapshot for Airdrops

A project team takes a snapshot of all addresses holding a specific NTP1 token before an airdrop. The `/ntp1/stakeholders/{tokenid}` endpoint returns the current holder set with balances, which the team feeds into their airdrop transaction builder. Combined with `/ntp1/sendtoken`, the airdrop is executed in batches without needing to run a full Neblio node.

Example prompt: GET `/ntp1/stakeholders/{tokenid}` for the target token id and feed the holder list into a `/ntp1/sendtoken` loop.

### Block Explorer Backend

A wallet or explorer UI uses the /ins endpoints to render block, transaction, and address detail pages without running a Neblio full node locally. `/ins/block`, `/ins/tx`, and `/ins/addr` return Bitcoin-style JSON suitable for direct rendering. This avoids the operational overhead of running and indexing a full chain while keeping latency low.

Example prompt: GET `/ins/addr/{address}` for a wallet address and render the balance and transaction history in the explorer UI.

### Agent-Driven Token Operations

An AI agent that manages a token treasury uses Jentic to discover Neblio operations and execute mint, transfer, or burn calls under policy. The agent searches for the right operation, loads the input schema, and submits the request while Jentic handles the rpcAuth basic credentials so the agent never sees the node password.

Example prompt: Search Jentic for 'send NTP1 tokens between addresses', load the schema for `/ntp1/sendtoken`, and execute it with the source, destination, token id, and amount.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/ntp1/issue` | Issue a new NTP1 token |
| POST | `/ntp1/sendtoken` | Send NTP1 tokens between addresses |
| POST | `/ntp1/burntoken` | Burn NTP1 tokens |
| POST | `/ntp1/broadcast` | Broadcast a signed transaction |
| GET | `/ntp1/tokenid/{tokensymbol}` | Resolve token symbol to id |
| GET | `/ntp1/tokenmetadata/{tokenid}` | Get token metadata |
| GET | `/ntp1/stakeholders/{tokenid}` | List token holders |
| GET | `/ntp1/addressinfo/{address}` | Get address balance and transactions |

## Key resources

- **NTP1 Tokens** — Issue, send, burn NTP1 tokens and query metadata
- **Stakeholders** — Look up holders of a given token id
- **Transactions** — Broadcast and inspect signed transactions
- **Blocks** — Query Neblio blocks by hash or index
- **Addresses** — Inspect Neblio address balances and transaction history
- **Raw RPC** — Broadcast raw transactions via `/ntp1/broadcast` and `/ins/tx/send`

## Why Jentic

- **Setup:** Wiring the Neblio REST suite by hand means setting up the rpcAuth basic credentials, encoding NTP1 issue, send, and burn payloads correctly, and broadcasting signed transactions against the node host yourself. Through Jentic you install once, import the Neblio suite from the API Directory, store the node credentials once, and your agent calls it.
- **Permission scoping:** The state-changing Neblio operations carry the token, amount, and destination inside the request body rather than as a resource id in the URL path, so you limit the agent to the operations it needs, such as reading token metadata or address info. You choose that operation set, so issue, sendtoken, burntoken, and broadcast are not included unless you add them.
- **Credential handling:** Your Neblio rpcAuth username and password 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 'issue an NTP1 token' or 'look up token metadata by id', and Jentic returns the matching Neblio operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Blockchain.com API** — Bitcoin-focused blockchain explorer and wallet API
- **Blockfrost** — Cardano blockchain REST API for native assets and transactions
- **CoinGecko** — Aggregated price and market data including NTP1 listings

## FAQ

### Which OpenAPI specification does this Neblio REST API Suite page describe?

It describes the OpenAPI 3.0.0 document Neblio publishes itself. The NeblioTeam swagger-docs repository states that the canonical specification is defined in swagger.json, and the Jentic copy was imported from the swagger.yaml sibling that the same repository publishes alongside it, so both cover the same 50 endpoints, the same ntp1node.nebl.io server, and the same rpcAuth basic scheme. The vendor document is at https://raw.githubusercontent.com/NeblioTeam/neblio-api-swagger-docs/master/swagger.json. What Jentic adds around it is intent-based discovery and credential handling, not a different operation set. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Neblio REST API use?

The spec declares an HTTP basic security scheme named rpcAuth for node-level RPC endpoints; the public NTP1 and explorer paths under ntp1node.nebl.io are read-only and do not require credentials. Through Jentic the basic-auth username and password are stored encrypted in the vault and injected on calls that need rpcAuth.

### Can I issue a new NTP1 token with this API?

Yes. POST `/ntp1/issue` with the token symbol, amount, issuing address, and any metadata. The endpoint returns an unsigned transaction hex that you sign locally with the issuing address's private key, then POST to `/ntp1/broadcast` to publish it to the Neblio network.

### What are the rate limits for the Neblio REST API?

Neblio's public node ntp1node.nebl.io does not publish numeric rate limits in the OpenAPI spec; the operator generally permits sustained low single-digit requests per second per IP. Run your own Neblio node for production-scale throughput.

### How do I look up NTP1 token holders through Jentic?

Run pip install jentic, then search for 'list NTP1 token holders', load the schema for GET `/ntp1/stakeholders/{tokenid}`, and execute it with the token id. Jentic returns the holder list with balances ready for downstream airdrop or analytics processing.

### Does the Neblio REST API sign transactions for me?

No. The `/ntp1/issue`, `/ntp1/sendtoken`, and `/ntp1/burntoken` endpoints return unsigned transaction hex; you must sign with your private key locally and call `/ntp1/broadcast` to submit. Private keys never leave the caller.

### Can I limit what my agent is allowed to do with the Neblio REST API?

Yes. Because you run Jentic One yourself, your own rules decide which Neblio operations and credentials the agent can use, and you pick the exact operation set it may call. You can allow only read operations such as GET `/ntp1/tokenmetadata`, GET `/ntp1/stakeholders`, and GET `/ntp1/addressinfo`, so the agent looks up token metadata, holders, and address balances without any write access. The state-changing operations like `/ntp1/issue`, `/ntp1/sendtoken`, `/ntp1/burntoken`, and `/ntp1/broadcast` are not available to the agent unless you add them, and the rpcAuth node credentials stay under your control and never reach the agent's context.