canonical: https://jentic.com/apis/relysia.com/relysia

# Relysia Blockchain API

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

## For AI agents

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

## Scope

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

## Capabilities

- Utility_getData
- Mint a Token.
- Get STAS token details.
- Resolve address and paymail alias information.
- User Registration.
- Login Endpoint.
- Change password Endpoint

## Use cases

### 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..

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

| 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. |

## Key resources

- **admin** — Operations related to admin
- **Transactions** — Blockchain transaction related APIs.
- **Utility** — Useful blockchain tools.
- **Wallets** — Blockchain wallet management related APIs.
- **paymail** — BSV alias related APIs

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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.