Install
$ agentstack add skill-iblai-api-iblai-tokens ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ● Network access Used
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
iblai-tokens
Manage the organization's Platform API Tokens — the keys that authenticate every ibl.ai API call. List the tokens, create a new Api-Token (the secret is shown only once), and delete a token by name. Tokens are platform_key-scoped, not agent-scoped.
Auth & conventions
- Base URL:
https://api.iblai.app - Header:
Authorization: Api-Token $IBLAI_API_KEYon every request. - Path vars:
{org}=$IBLAI_ORG,{username}=$IBLAI_USERNAME. - Host: these endpoints live under
…/dm/api/core/…. - Not connected yet? Run
/iblai-loginfirst to populateIBLAI_ORG,
IBLAI_USERNAME, and IBLAI_API_KEY.
Reads
- GET
https://api.iblai.app/dm/api/core/platform/api-tokens/?platform_key={org}— list API keys.
Writes
- POST
https://api.iblai.app/dm/api/core/platform/api-tokens/— create a token (returns the secret only once):
``json { "username": "string (required)", "name": "string (required)", "key": "", "platform_key": "{org} (required)", "created": "ISO datetime (required)", "expires": "'' or seconds-string (required)", "expires_in": "seconds-string | undefined" } ``
- DELETE
https://api.iblai.app/dm/api/core/platform/api-tokens/{name}?platform_key={org}— delete a key by name. Destructive — confirm with the user first.
Example
Create a new Platform API Token named prod-integration (capture the secret from the response — it is shown only once):
curl -X POST \
"https://api.iblai.app/dm/api/core/platform/api-tokens/" \
-H "Authorization: Api-Token $IBLAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"username": "'"$IBLAI_USERNAME"'",
"name": "prod-integration",
"key": "",
"platform_key": "'"$IBLAI_ORG"'",
"created": "2026-06-12T00:00:00Z",
"expires": ""
}'
Notes
- The create response returns the token secret only once — store it
immediately; it cannot be retrieved again afterward.
/iblai-loginuses this samePOST …/platform/api-tokens/endpoint to mint
the Api-Token it stores as IBLAI_API_KEY.
- Delete is by token name (not id), and is scoped to the org via
platform_key={org}.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.