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

# Radixdlt Radix Gateway API - Babylon

This API is exposed by the Babylon Radix Gateway to enable clients to efficiently query current and historic state on the RadixDLT ledger, and intelligently handle transaction submission. It is designed for use by wallets and explorers, and for light queries from front-end dApps. For exchange/asset integrations, back-end dApp integrations, or simple use cases, you should consider using the Core AP. The API exposes 36 endpoints.

## For AI agents

Programmatically get gateway status, get network configuration. Covers 36 operations.

## Scope

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

## Capabilities

- Get Gateway Status
- Preview Transaction
- Submit Transaction
- Access Radix Gateway API - Babylon payments resources via REST API

## Use cases

### Payments Operations

Use the Radix Gateway API - Babylon to perform payments operations programmatically. The API provides 36 endpoints covering core functionality including get gateway status, get network configuration, get construction metadata.

Example prompt: Call POST `/status/gateway-status` to get gateway status

### Automated SubAPIs Management

Automate subapis operations by combining multiple Radix Gateway API - Babylon endpoints. Agents can get network configuration and then get construction metadata in a single workflow.

Example prompt: Call POST `/status/network-configuration` to get network configuration, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Radix Gateway API - Babylon 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 'get gateway status', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/status/gateway-status` | Get Gateway Status |
| POST | `/status/network-configuration` | Get Network Configuration |
| POST | `/transaction/construction` | Get Construction Metadata |
| POST | `/transaction/preview` | Preview Transaction |
| POST | `/transaction/preview-v2` | Preview Transaction V2 |
| POST | `/transaction/submit` | Submit Transaction |
| POST | `/transaction/committed-details` | Get Committed Transaction Details |
| POST | `/transaction/status` | Get Transaction Status |

## Key resources

- **SubAPIs** — The Gateway API is split into 5 sub APIs:
- **Status** (`/status/*`) - For status and configuration
- **Concepts** — Interacting with this API effectively may require knowledge about the Radix Babylon Transaction Mode
- **Architecture** — ## Request-Response Format

The API is designed in a JSON-RPC-like style, using HTTP as a transport
- **Examples** — ## Querying for entity data, including fungible and non-fungible resources.

The Gateway API has dif
- **Status** — Query information about the Gateway API status.

## AI readiness

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.

- **Score:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 46 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 74 / 100
- **View full report:** https://jentic.com/apis/radixdlt.com/radixdlt/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Radix Gateway API by hand means choosing between the mainnet.radixdlt.com and stokenet.radixdlt.com hosts and handling retries across its POST transaction and status operations yourself, even though it needs no auth. Through Jentic you install once, import Radix Gateway from the API Directory, and your agent calls it without wiring the request bodies.
- **Permission scoping:** The Radix Gateway API carries its transaction and status targets in the request body rather than a resource id in the path, so limit the agent to the operations it needs, such as previewing a transaction or reading transaction status. You choose which operations are allowed, so a submit is not included unless you add it.
- **Credential handling:** Radix Gateway needs no credential, so there is nothing to store: your own Jentic One instance still runs the call without exposing any secret to the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'preview a Radix transaction' or 'check transaction status', and Jentic returns the matching Radix Gateway operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Radix Gateway API - Babylon use?

The Radix Gateway API - Babylon 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 get gateway status with the Radix Gateway API - Babylon?

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

### What are the rate limits for the Radix Gateway API - Babylon?

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 get gateway status through Jentic?

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

### How many endpoints does the Radix Gateway API - Babylon have?

The Radix Gateway API - Babylon exposes 36 endpoints covering subapis, concepts, architecture operations.

### Can I limit what my agent is allowed to do with the Radix Gateway API - Babylon?

Yes. Because you run your own self-hosted Jentic One instance, your own rules decide which Radix Gateway operations the agent may call, and the API carries its transaction and status targets in the request body rather than a path id, so you scope access at the operation level. You can allow read-only work such as previewing a transaction or checking transaction status while leaving out POST `/transaction/submit`, which is not included unless you explicitly add it. The agent can only invoke the operations you have permitted.