canonical: https://jentic.com/apis/apptigent.com/apptigent-powertools

# Apptigent PowerTools Developer

The Apptigent PowerTools API provides a large library of data and utility operations over REST. It converts between formats, units, and currencies, transforms and validates text, works with collections and JSON, generates hashes, GUIDs, and QR codes, and handles date, time, and media tasks. Calls authenticate with an API key sent in a request header.

## For AI agents

Lets an AI agent run utility operations: converting formats and units, transforming and validating text, working with collections and JSON, and generating codes and media.

## Scope

Provides stateless utility and transformation operations only; it does not store your data or run model-based language understanding, so pair it with those services when needed.

## Capabilities

- Convert between currencies, units, and measurement systems
- Transform, format, and validate strings and text
- Convert between JSON, CSV, XML, and HTML data
- Work with collections: filter, sort, split, and query
- Generate hashes, GUIDs, QR codes, and random numbers
- Handle date, time, and image and speech media tasks

## Use cases

### Add data transformation to a workflow

Integrations often need to reshape data between steps. The PowerTools API converts between JSON, CSV, XML, and HTML and queries structured data, so a workflow can normalize a payload into the format the next step expects without custom parsing code.

Example prompt: Convert a supplied CSV payload into JSON and return the result.

### Handle conversions and calculations

Apps frequently need currency, unit, and numeric operations. The API converts currencies, distances, weights, and other units and runs a range of calculations, so an integration can offload these without bundling its own math and conversion tables.

Example prompt: Convert an amount between two currencies and return the converted value.

### Process text and generate assets

Content workflows need to clean text and produce small assets. The API translates, formats, and validates strings and generates hashes, GUIDs, QR codes, and speech, so an integration can prepare text and create supporting assets in one place.

Example prompt: Translate a message and generate a QR code linking to its source.

### Give an agent a utility toolbox

An AI agent often needs a quick conversion, format change, or code generated mid-task. Through Jentic the agent discovers the right PowerTools operation by intent and runs it under the integration's API key, returning the converted value or asset without leaving the workflow.

Example prompt: Given a currency amount, convert it and format the result for display.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/ConvertCurrency` | Convert an amount between currencies |
| POST | `/TranslateString` | Translate text into another language |
| POST | `/CSVtoJSON` | Convert a CSV payload into JSON |
| POST | `/FormatDateTime` | Format a date and time value |
| POST | `/CalculateAverage` | Calculate the average of a set of numbers |
| POST | `/TextToSpeech` | Generate speech audio from text |

## Key resources

- **Conversions** — Currency, unit, and measurement conversions
- **Text** — String transformation, translation, and validation
- **Data** — Conversions between JSON, CSV, XML, and HTML
- **Collections** — Filter, sort, split, and query operations on lists
- **Generators** — Hashes, GUIDs, QR codes, and media outputs

## Why Jentic

- **Setup:** Wiring up dozens of utility endpoints yourself means tracking the API key and mapping each conversion or transform you need. With Jentic you install once, import PowerTools from the Directory, and store the API key a single time.
- **Permission scoping:** Running Jentic in your own instance, you decide which PowerTools operations the agent may call, so you can allow conversions and text utilities while withholding media or link operations. Access is granted per operation.
- **Credential handling:** Your PowerTools API key is held encrypted by your own Jentic One instance and injected only when an operation runs, so it never appears in the agent's prompt, logs, or context.
- **Discovery method:** Agents find PowerTools through Jentic's intent search: a request like convert this CSV to JSON resolves to the right operation with inputs and auth prepared.

## Related APIs

- **CloudConvert** — Converts files between a wide range of document and media formats.
- **ConvertAPI** — Converts and processes documents such as PDF and Office files.
- **NLP Cloud** — Runs language models for advanced text understanding and generation.

## FAQ

### Is there an MCP server for the Apptigent PowerTools API?

You do not need a dedicated MCP server. Through Jentic your self-hosted agent can call PowerTools operations directly by intent, so you connect the API without maintaining separate MCP tooling.

### Can I limit which PowerTools operations my agent can call?

Yes. Because you run Jentic yourself, you choose which PowerTools operations your agent can call, so you can allow conversions while withholding media or link operations. Scoping is applied per operation.

### What authentication does the Apptigent PowerTools API use?

PowerTools authenticates with an API key sent in the `X-IBM-Client-Id` request header. Jentic injects the key from your stored credential when a call runs, so it never appears in your agent's prompt.

### What kinds of operations does PowerTools cover?

It covers conversions between currencies and units, transformations between JSON, CSV, XML, and HTML, string and text utilities, collection operations, and generators for hashes, codes, and media.

### Can PowerTools convert data between formats?

Yes. It converts between JSON, CSV, XML, and HTML and can query JSON and XML, so you can reshape a payload into the format the next step expects.

### How does an agent find PowerTools operations in Jentic?

The agent searches Jentic by intent, such as converting a currency amount or a CSV payload, and Jentic returns the matching operation ready to run under your API key.
