cello

name	cello
description	Read the status of a Hyperledger Cello deployment through its REST API. Use when the user asks to inspect Cello, Fabric networks, nodes, peers, orderers, channels, chaincodes, or organizations.

Cello API

Read-only inspection of a running Cello API Engine.

Setup

• Base URL: http://localhost:8080/api/v1
• Credentials: read from ~/.cello/credentials, an env-style file with CELLO_EMAIL=... and CELLO_PASSWORD=... (create it once, chmod 600).
• Auth: send the JWT from ~/.cello/token as the Authorization: JWT <token> header. If ~/.cello/token is missing, run the login helper below first. Tokens expire after ~1 hour, so on any 401 re-run the helper and retry the request.

Login helper:

mkdir -p ~/.cello
set -a; . ~/.cello/credentials; set +a
curl -s -X POST http://localhost:8080/api/v1/login \
     -H "Content-Type: application/json" \
     -d "{\"email\":\"$CELLO_EMAIL\",\"password\":\"$CELLO_PASSWORD\"}" \
  | jq -r '.data.token' > ~/.cello/token
chmod 600 ~/.cello/token

If login fails or the token is empty or null, ask the user to verify ~/.cello/credentials and API availability. Do not guess credentials.

Successful responses use {status, msg, data}; error responses may not.

List endpoints default to per_page=10; use per_page=100 for inspection and page further only when .data.total > 100.

Topics — load the matching file as needed

User mentions…	Read this file
nodes, peers, orderers	nodes.md
channels	channels.md
chaincodes, smart contracts	chaincodes.md
organizations, members	organizations.md

Load only the file relevant to the user's question, not all of them.