# Get started

## [Telematics SDK powers telematics inside Mobile apps](https://raxeltelematics.com/telematics-sdk)

![](https://2858820347-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtaiRtygxVgZO0fJZJ-%2F-MRKOXntRvNA5qrBB_sW%2F-MRKRymYpVOFVfpGnrdQ%2Ftransportation.png?alt=media\&token=17a39041-d326-49bf-915e-e3e8ce4fa297)

## What we provide

![](https://2858820347-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtaiRtygxVgZO0fJZJ-%2F-MTFJPr8EBJC-0uO9HAT%2F-MTFJYqpgFtbt67IN0Es%2FScreen%20Shot%202021-02-05%20at%2011.10.54%20AM.png?alt=media\&token=b247efad-2d7e-490a-8ef9-c0f0d238ed79)

## Why it is better to work with us?

### In-house development vs our Telematics

* Telematics SDK provides **contactless telematics** powered by **AI**
* Telematics SDK **reduces R\&D and maintenance cost by 90%**
* Telematics SDK **reduces time to market** of any tracking apps from years **to a day**

### Analysis

|                     In-house development                     |                                       Telematics SDK                                      |
| :----------------------------------------------------------: | :---------------------------------------------------------------------------------------: |
| Long development cycle \~24 months, cost approximately $900k |                           Integration takes less than 60 minutes                          |
|     Expensive and inefficient maintenance \~$350k a year     | Saas model. Pay per usage. No licence fee and maintenance fee for Telematics SDK and APIs |

## :point\_right: [SDK Features](https://docs.telematicssdk.com/product-description/sdk-features)

## Telematics Platform features

{% content-ref url="platform-features/back-end-as-a-service" %}
[back-end-as-a-service](https://docs-old.telematicssdk.com/platform-features/back-end-as-a-service)
{% endcontent-ref %}

{% content-ref url="platform-features/leaderboard-1" %}
[leaderboard-1](https://docs-old.telematicssdk.com/platform-features/leaderboard-1)
{% endcontent-ref %}

{% content-ref url="platform-features/car-service" %}
[car-service](https://docs-old.telematicssdk.com/platform-features/car-service)
{% endcontent-ref %}

{% content-ref url="platform-features/fnol-inspections-and-damage-recognition" %}
[fnol-inspections-and-damage-recognition](https://docs-old.telematicssdk.com/platform-features/fnol-inspections-and-damage-recognition)
{% endcontent-ref %}

{% content-ref url="platform-features/sns" %}
[sns](https://docs-old.telematicssdk.com/platform-features/sns)
{% endcontent-ref %}

{% content-ref url="platform-features/3rd-party-data-processing" %}
[3rd-party-data-processing](https://docs-old.telematicssdk.com/platform-features/3rd-party-data-processing)
{% 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://docs-old.telematicssdk.com/master.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.