Note the retired agent backends in the tool and LLM skills

[Joetib]

Companion to iblai/iblai-dm-pro#3005, which retires three agent backends in DM 4.363.0 — Google ADK/A2A, OpenAI Assistants, and the OpenAI Agents SDK. Tracked by iblai/iblai-platform#2416.

Two documented endpoints change their filtering semantics as a result. Neither is a shape change — same URLs, same auth, same response schema — so this is a docs-only update to two skills.

What changed on the platform

available-tools/ (iblai-api-agent-tool) used to return a different tool set per agent backend, selected by the agent's allow_google_agent / allow_openai_agent / allow_openai_assistant flags. Every agent now runs on the base agent, so it returns the base-agent set uniformly. An agent that previously ran on a retired backend sees a larger list than before.

mentor-llms/?mentor_id= (iblai-api-agent-llm) used to narrow the provider/model cards to a single provider for agents on the Google ADK/A2A and OpenAI Agents SDK backends, because those backends were locked to one provider. The parameter still scopes the request to an agent and still 404s if that agent doesn't exist in the org, but it no longer narrows — every agent gets the org's full authorized list.

What is deliberately not here

The users/{user_id}/google-agents/ list and detail endpoints are removed by #3005, but this repo never documented them, so there is nothing to delete. I checked for google-agents, google_agents, GoogleAgent, and every retired backend name across the skills and MCP server — no other references exist.

Verification

$ grep -rn "google-agents\|google_agents\|GoogleAgent" --include="*.md" --include="*.py" --include="*.json" .
(no matches)

$ grep -rn "openai-assistant\|openai-agent\|google-agent\|allow_openai\|allow_google_agent" --include="*.md" .
(no matches)

Both notes are additive; no existing prose was invalidated, since the old narrowing was never documented.