# Introduction Welcome to the Oten Trust integration documentation. Oten Trust provides enterprise-grade threat intelligence for teams that need to detect and block malicious URLs at scale. With ultra-low latency scanning, actionable risk signals, and integration-friendly APIs, Oten Trust helps you embed trust decisions directly into your applications and workflows. Instead of working with fragmented signals or raw reputation data, you get a simple outcome your systems can use immediately: **how risky a URL is, and whether it should be allowed or blocked**. *** ### Why Oten Trust? #### Fast enough for real-time decisions Oten Trust is optimized for **sub-100ms latency**, allowing you to evaluate URLs inline without disrupting the user experience. #### Actionable by design Responses include a clear `risk_score` and an explicit allow/block verdict, making it easy to turn scan results into product or policy decisions. #### Easy to integrate Drop-in REST APIs make Oten Trust simple to adopt across modern stacks and workflows, including **Node.js, Python, Go, PHP**, and CI/CD pipelines. *** ### Who is it for? Oten Trust is built for teams that need to: * Protect users from malicious links * Enforce URL trust policies automatically * Add threat intelligence into product flows * scale security checks without adding operational complexity {% hint style="info" %} Oten Trust is not just a scanning API — it is a decision engine for URL trust. {% endhint %} --- # 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://oten.gitbook.io/oten-trust-support/documentation/api-reference/readme.md?ask= ``` 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.