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

# Regiondo API documentation

The Regiondo API (<a href="https://sandbox-api.regiondo.com/docs/Regiondo_API_workflow.png" target="_blank">API Workflow diagram </a>) is organized around <a href="http://en.wikipedia.org/wiki/Representational_state_transfer" target="_blank">RESTful</a>. Our API is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors. We use built-in HTTP featu. The API exposes 55 endpoints secured with apiKey authentication.

## For AI agents

Programmatically list of locales, currency information. Covers 55 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for ai and machine learning only.

## Capabilities

- List of locales
- Currency information
- Returns a single category
- Add to hold before purchase
- View all hold requests
- Prolong previous hold request

## Use cases

### AI and Machine Learning Operations

Use the Regiondo API documentation to perform ai ml operations programmatically. The API provides 55 endpoints covering core functionality including list of locales, currency information, list categories.

Example prompt: Call GET `/account/locale` to list of locales

### Automated Account Management

Automate account operations by combining multiple Regiondo API documentation endpoints. Agents can currency information and then list categories in a single workflow.

Example prompt: Call GET `/account/currency` to currency information, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Regiondo API documentation 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 'list of locales', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/account/locale` | List of locales |
| GET | `/account/currency` | Currency information |
| GET | `/categories` | List categories |
| GET | `/categories/{categoryId}` | Returns a single category |
| POST | `/checkout/hold` | Add to hold before purchase |
| GET | `/checkout/hold` | View all hold requests |
| PUT | `/checkout/hold` | Prolong previous hold request |
| DELETE | `/checkout/hold` | Remove hold request |

## Key resources

- **Account** — Operations related to Account
- **Categories** — Operations related to Categories
- **Checkout** — Operations related to Checkout
- **Languages** — Operations related to Languages
- **Locations** — Operations related to Locations

## 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:** 47 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 43 / 100
  - Developer Experience & Jentic Compatibility: 39 / 100
  - AI-Readiness & Agent Experience: 36 / 100
  - Agent Usability: 93 / 100
  - Security: 50 / 100
  - AI Discoverability: 61 / 100
- **View full report:** https://jentic.com/apis/regiondo.com/regiondo/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 Regiondo API by hand means setting your key in the X-API-ID header, choosing between the production api.regiondo.com and sandbox-api.regiondo.com hosts, and building your own retry handling. Through Jentic you install once, import the Regiondo API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Regiondo API puts the category id in the URL path (`/categories/{categoryId}`) alongside body-based checkout endpoints, so a rule can pin your agent to reading a given category and its account settings. You choose the operations it may call, so state-changing ones like holding or deleting a checkout are not included unless you add them.
- **Credential handling:** Your Regiondo API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list categories' or 'get account locale', and Jentic returns the matching Regiondo API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Openai** — Alternative ai ml API
- **Anthropic** — Alternative ai ml API
- **Cohere** — Complementary ai ml API
- **Huggingface** — Complementary ai ml API

## FAQ

### What authentication does the Regiondo API documentation use?

The Regiondo API documentation uses an API key passed in the `X-API-ID` 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 list of locales with the Regiondo API documentation?

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

### What are the rate limits for the Regiondo API documentation?

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 list of locales through Jentic?

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

### How many endpoints does the Regiondo API documentation have?

The Regiondo API documentation exposes 55 endpoints covering account, categories, checkout operations.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which Regiondo operations and credentials your agent may use. Since the API puts the category id in the URL path (GET `/categories/{categoryId}`) alongside account reads like GET `/account/locale` and GET `/account/currency`, you can pin the agent to reading a specific category and its account settings. State-changing checkout operations, such as POST `/checkout/hold` or DELETE `/checkout/hold`, are only available to the agent if you explicitly add them.