# The Tomedes API

Welcome to the Tomedes API documentation. If you need fast solutions to your translation tech, the Tomedes public APIs can make it easier for you to translate, automate, and ultimately streamline difficult processes. Our Tomedes APIs are usually used for three reasons:

* One reason to use our APIs is for high volumes of content. If you need a fast solution to large volumes of content, a simple API workflow would ease that problem. The APIs we have are designed for you to use for high amounts of data.
* The second reason is to offer translation to your end-users. The information or content solicited from your customers can be passed on through our APIs and helps our translators understand the context and content.
* The third reason to use our APIs is to automate. Processes that usually won’t be able to run without the help of shared data and programming interactions from developers to businesses are solved by automation. More automation for automation is a key concept of Tomedes and its APIs.
* Other reasons to use our APIs are: simplicity, efficiency, speed, and the ability to customize.

Tomedes will continue to add more and more APIs to provide more solutions to our users.

## Want to jump right in?

Feeling like an eager beaver? Jump in to the quick start docs and get making your first request:

{% content-ref url="api/api-endpoint-summary" %}
[api-endpoint-summary](https://developers.tomedes.com/api/api-endpoint-summary)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developers.tomedes.com/the-tomedes-api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.