Skip to content
Back to skills

Iblai Api Agent Disclaimer

ASecurity

Manage an ibl.ai agent's disclaimers via the platform API — the Advisory text (saved through the agent settings endpoint) and the User Agreement (create/update/activate). Use when adding legal or advisory notices users must see or accept.

  • 15 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 20, 2026
ai-agentsbashapi

Works with

  • api

Security analysis

A100/100

Scanned September 20, 2026

npx -y skills add iblai/vibe --skill iblai-api-agent-disclaimer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Iblai Api Agent Disclaimer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Iblai Api Agent Disclaimer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/iblai-iblai-api-agent-disclaimer/badge)](https://www.skillsdirectory.com/skills/iblai-iblai-api-agent-disclaimer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: iblai-api-agent-disclaimer
description: Manage an ibl.ai agent's disclaimers via the platform API — the Advisory text (saved through the agent settings endpoint) and the User Agreement (create/update/activate). Use when adding legal or advisory notices users must see or accept.
metadata:
  kind: api
---

# iblai-api-agent-disclaimer

Manage an agent's disclaimers via the API: the Advisory text (a single field on
the agent's `settings/`) and the User Agreement (its own create / update /
activate lifecycle). Use when adding legal or advisory notices users must see or
accept.

## Auth & conventions

- **Base URL:** `https://api.iblai.app`
- **Header:** `Authorization: Api-Token $IBLAI_API_KEY` on every request.
- **Path vars:** `{org}` = `$IBLAI_ORG`, `{username}` = `$IBLAI_USERNAME`,
  `{mentor}` = the agent's unique id (e.g. `d17dc729-60fd-4363-81a0-f67d9318b03e`).
- Not connected yet? Run **`/iblai-api-login`** first to populate `IBLAI_ORG`,
  `IBLAI_USERNAME`, and `IBLAI_API_KEY`.

## Reads

- **GET** `https://api.iblai.app/dm/api/ai-mentor/orgs/{org}/users/{username}/mentors/{mentor}/settings/` — Advisory text lives in the `disclaimer` field.
- **GET** `https://api.iblai.app/dm/api/ai-mentor/orgs/{org}/users/{username}/disclaimers/?mentor_id={mentor}&scope=mentor` — User Agreement list (read `results[0]` for the active agreement).

## Writes

- **PUT** `…/users/{username}/mentors/{mentor}/settings/` — save **Advisory** text:
  ```json
  {
    "disclaimer": "string"
  }
  ```
- **POST** `…/users/{username}/disclaimers/` — create a **User Agreement**:
  ```json
  {
    "content": "string (required)",
    "mentors": ["uuid"],
    "scope": "mentor",
    "active": "boolean"
  }
  ```
- **PATCH** `…/users/{username}/disclaimers/{id}/` — update content or toggle activation:
  ```json
  {
    "content": "string"
  }
  ```
  or
  ```json
  {
    "active": "boolean"
  }
  ```

## Example

Create and activate a User Agreement for an agent:

```bash
curl -X POST \
  "https://api.iblai.app/dm/api/ai-mentor/orgs/$IBLAI_ORG/users/$IBLAI_USERNAME/disclaimers/" \
  -H "Authorization: Api-Token $IBLAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "By continuing, you agree to use this assistant for educational purposes only.",
    "mentors": ["'"$MENTOR"'"],
    "scope": "mentor",
    "active": true
  }'
```

## Notes

- The **Advisory** is one field (`disclaimer`) on the agent `settings/` — send only
  that key in the PUT; other settings are left unchanged.
- The **User Agreement** is a separate object users must accept; activate exactly one
  per agent via `active: true`, and deactivate others with a PATCH `active: false`.
- The disclaimers list endpoint is filtered with `mentor_id` + `scope=mentor`; the
  current agreement is the first item in `results`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.