Install Jentic One Beta

Connect the Relysia Blockchain API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Relysia Blockchain API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frelysia.com%2Frelysia" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frelysia.com%2Frelysia" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Relysia Blockchain API.

Utility_getData

Mint a Token.

Get STAS token details.

Resolve address and paymail alias information.

User Registration.

GET STARTED

Start building with Relysia Blockchain API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Relysia Blockchain API for, with concrete tasks.

★ Developer Tools Operations

Use the Relysia Blockchain API to perform developer tools operations programmatically. The API provides 85 endpoints covering core functionality including utility_getdata, mint a token., get stas token details..

Call GET / to utility_getdata

Automated admin Management

Automate admin operations by combining multiple Relysia Blockchain API endpoints. Agents can mint a token. and then get stas token details. in a single workflow.

Call POST /v1/issue to mint a token., then verify the result

AI Agent Integration via Jentic

AI agents discover and call Relysia Blockchain 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 apiKey tokens manually.

Search Jentic for 'utility_getdata', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

85 endpoints — relysia makes blockchain adoption frictionless and easy.

METHOD

PATH

DESCRIPTION

GET

Utility_getData

POST

/v1/issue

Mint a Token.

GET

/v1/token/{id}

Get STAS token details.

GET

/v1/URI

Resolve address and paymail alias information.

POST

/v1/signUp

User Registration.

POST

/v1/auth

POST

/v1/password/change

Change password Endpoint

GET

/v1/user

Profile details.

GET

Utility_getData

POST

/v1/issue

Mint a Token.

GET

/v1/token/{id}

Get STAS token details.

GET

/v1/URI

Resolve address and paymail alias information.

POST

/v1/signUp

User Registration.

POST

/v1/auth

POST

/v1/password/change

Change password Endpoint

GET

/v1/user

Profile details.

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Relysia by hand means sending its authToken and serviceID headers to api.relysia.com and mapping its sign-up, auth, and token endpoints yourself. Through Jentic you install once, import Relysia from the API Directory, store the token and service id once, and your agent calls it.

Permission scoping

Relysia puts the token id in the URL path (/v1/token/{id}), so a rule can pin your agent to reading one token and its URI. You choose the operations it may call, so issuing tokens or changing a password is not included unless you add them.

Credential isolation

Your Relysia authToken and serviceID 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 'read a token' or 'issue a token', and Jentic returns the matching Relysia operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Relysia Blockchain API through Jentic.

What authentication does the Relysia Blockchain API use?

The Relysia Blockchain API uses an API key passed in the `authToken` header. 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 utility_getdata with the Relysia Blockchain API?

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

What are the rate limits for the Relysia Blockchain 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 utility_getdata through Jentic?

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

How many endpoints does the Relysia Blockchain API have?

The Relysia Blockchain API exposes 85 endpoints covering admin, transactions, utility operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Relysia operations and credentials your agent may use. Because Relysia puts the token id in the URL path at GET /v1/token/{id}, you can pin the agent to reading one token and resolving its URI while excluding write operations like minting a token at POST /v1/issue or changing a password at POST /v1/password/change. The agent can only call the endpoints you allow, and your encrypted authToken and serviceID are injected at execution time rather than exposed in the agent context.

Relysia Blockchain API

Name: Relysia Blockchain API
Brand: Relysia Blockchain API
Availability: InStock

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey85 EndpointsREST

For Agents

Programmatically utility_getdata, mint a token.. Covers 85 operations with apiKey authentication.

Use for: I need to utility_getdata, I want to mint a token., Search for stas token details., Find all resolve address and paymail alias information.

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

Relysia makes blockchain adoption frictionless and easy. The API exposes 85 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Relysia Blockchain API to your agent

Capabilities

Start building with Relysia Blockchain API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Relysia Blockchain API