AI-Safe: Enterprise Compliance Gateway is a robust API designed to streamline organizational adherence to GDPR and the EU AI Act. It offers automated tools for data protection compliance, risk assessments, and regulatory reporting, ensuring that businesses can integrate AI technologies responsibly while safeguarding user privacy. With real-time monitoring and actionable insights, AI-Safe empowers enterprises to navigate complex compliance requirements effectively.
{"status":"COMPLIANT","clean_prompt":"Hello, my name is [REDACTED_NAME] and my email is [REDACTED_EMAIL].","entities_found":3,"security_alert":"None"}
curl --location --request POST 'https://zylalabs.com/api/12285/compliance+nexus+api+for+ai+governance/23068/sanitize+user+inputs+-+block+malicious+code' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"prompt": "Hello, my name is John Doe and my email is [email protected]."
}'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Compliance Nexus API for AI Governance simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
High-performance security middleware for LLM integrations. Automatically detects and redacts PII (Personally Identifiable Information) including names, emails, phones, and credit cards from prompts before they reach the LLM. Features built-in protection against prompt injection and jailbreak attempts. Essential for businesses using OpenAI, Anthropic, or Gemini in regulated markets (GDPR, HIPAA, EU AI Act). Zero-log execution for maximum privacy.
The Sanitize User Inputs endpoint returns a JSON object containing the compliance status, a sanitized version of the input prompt, the number of entities found (e.g., PII), and any security alerts. For example, it may return `{"status":"COMPLIANT","clean_prompt":"Hello, my name is [REDACTED_NAME]...","entities_found":3,"security_alert":"None"}`.
The key fields in the response data include `status` (indicating compliance), `clean_prompt` (the sanitized input), `entities_found` (count of detected PII), and `security_alert` (any identified security issues). These fields help users assess compliance and security effectively.
The Sanitize User Inputs endpoint accepts parameters such as the raw user input prompt. Users can customize their requests by providing different input strings that may contain PII or malicious code, allowing the API to process and sanitize them accordingly.
The response data is organized in a structured JSON format. It includes a top-level object with fields for compliance status, the sanitized prompt, the count of entities found, and any security alerts, making it easy to parse and utilize programmatically.
Typical use cases for the Sanitize User Inputs endpoint include ensuring compliance with GDPR and the EU AI Act when processing user inputs in AI applications, protecting sensitive information in customer interactions, and preventing prompt injection attacks in AI models.
Data accuracy is maintained through real-time monitoring and automated detection algorithms that identify and redact PII. The API employs robust security measures to ensure that only compliant and sanitized data is processed, minimizing the risk of errors.
Users can expect standard data patterns where PII is consistently redacted in the `clean_prompt` field, and the `entities_found` field reflects the number of detected sensitive items. For example, if a prompt contains multiple PII types, the count will increase accordingly.
Users can effectively utilize the returned data by integrating the sanitized prompts into their AI applications, ensuring compliance with regulations. The `status` field helps assess compliance, while the `entities_found` count can inform further data handling or security measures.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund