canonical: https://jentic.com/apis/tokenjay.app/tokenjay

# Tokenjay App TokenJay API services

Please see usage policies on tokenjay.app. The API exposes 27 endpoints.

## For AI agents

Programmatically creates a new payment request. will return request id to check for transaction s, preparetransaction. Covers 27 operations.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Creates a new payment request. Will return request id to check for transaction s
- prepareTransaction
- replaceTokenAmountInputFields
- doCreateBabelBox
- Lists price and available volume for a certain token

## Use cases

### Identity and Authentication Operations

Use the TokenJay API services to perform identity auth operations programmatically. The API provides 27 endpoints covering core functionality including creates a new payment request. will return request id to check for transaction s, preparetransaction, replacetokenamountinputfields.

Example prompt: Call POST `/payment/addrequest` to creates a new payment request. will return request id to check for transaction s

### Automated tokenVerification Management

Automate tokenverification operations by combining multiple TokenJay API services endpoints. Agents can preparetransaction and then replacetokenamountinputfields in a single workflow.

Example prompt: Call POST `/mosaik/tokenburn/prepare` to preparetransaction, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TokenJay API services 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 none tokens manually.

Example prompt: Search Jentic for 'creates a new payment request. will return request id to check for transaction s', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/payment/addrequest` | Creates a new payment request. Will return request id to check for transaction s |
| POST | `/mosaik/tokenburn/prepare` | prepareTransaction |
| POST | `/mosaik/babelfee/newoffer/new-input` | replaceTokenAmountInputFields |
| POST | `/mosaik/babelfee/newoffer/doit` | doCreateBabelBox |
| GET | `/tokens/prices/{tokenId}` | Lists price and available volume for a certain token |
| GET | `/tokens/prices/all` | Lists all token prices and available volume |
| GET | `/tokens/listGenuine` | Lists all genuine tokens known |
| GET | `/tokens/listBlocked` | Lists all blocked tokens |

## Key resources

- **tokenVerification** — Ergo Platform Genuine Tokens Verification
- **peerDetection** — Detecting nodes to use for submitting transactions
- **paymentPortal** — ErgoPay payment portal

## Why Jentic

- **Setup:** Wiring the TokenJay API by hand means working through its payment, mosaik, and token endpoints, shaping each request, and handling retries yourself. Through Jentic you install once, import TokenJay from the API Directory, and your agent calls it.
- **Permission scoping:** TokenJay addresses most operations through the request body, with token prices read by a token id in the URL path used only as a lookup, so scope the agent by the operations it needs, such as reading token prices or the genuine token list. You choose that set, so write operations like preparing a token burn are only available if you include them.
- **Credential handling:** This TokenJay spec declares no credential, so there is nothing for Jentic One to store; any credential your deployment requires is held encrypted by your own instance and injected at execution time, never in the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get a token's price' or 'list genuine tokens', and Jentic returns the matching TokenJay operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the TokenJay API services use?

The TokenJay API services uses no authentication. 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 creates a new payment request. will return request id to check for transaction s with the TokenJay API services?

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

### What are the rate limits for the TokenJay API services?

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 creates a new payment request. will return request id to check for transaction s through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'creates a new payment request. will return request id to check for transaction s'. Jentic returns the matching TokenJay API services operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the TokenJay API services have?

The TokenJay API services exposes 27 endpoints covering tokenverification, peerdetection, paymentportal operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which TokenJay operations the agent may call, so you can grant read-only access such as GET `/tokens/prices/{tokenId}`, GET `/tokens/prices/all`, or GET `/tokens/listGenuine` while withholding everything else. Write operations like POST `/mosaik/tokenburn/prepare` or POST `/payment/addrequest` are only reachable if you explicitly include them in that set. Any credential your deployment needs is held encrypted by your own instance and injected at execution time, never exposed in the agent's context.