Relysia Blockchain API
25
AI ReadinessNon-Ready (F)25/100
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.
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.
1
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" | sh2
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 instanceJentic 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.
Login Endpoint.
Change password Endpoint
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
Login Endpoint.
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
Login Endpoint.
POST
/v1/password/change
Change password Endpoint
GET
/v1/user
Profile details.
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
R
Relysia Blockchain API
- Non-Ready (F)25/100
71
Foundational Compliance63
Developer Experience & Jentic Compatibility8
AI-Readiness & Agent Experience88
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
71
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
82%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
9%
Example Density
How richly the API is illustrated with examples.
95%
Example Validity
Percentage of examples that conform to their schemas.
48%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
8
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
13%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
21%
Summary Coverage
Coverage of summaries across operations/tags/info.
88
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: ASignals: 1
88%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>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.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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.
GET STARTED