TAP Integration Overview
Available APIs
TAP uses the AI service for caption/tag recommendations, content safety moderation, and completed-conversation topic detection. The AI service returns results only; TAP applies accepted updates, moderation decisions, or downstream reporting decisions on its side.
The paths below use the TAP APIM AI prefix. When calling the Mastra app directly for local or environment smoke tests, omit the /ai prefix.
| API | Endpoint | Description |
|---|---|---|
| Image Tagging and Caption Suggestions | POST /ai/tap/tools/tagging-suggestions | Preferred synchronous image/media tagging tool endpoint with the standard { data } envelope |
| Content Safety | POST /ai/tap/tools/content-safety | TAP policy moderation with the standard { data } tool envelope |
| Topic Detection | POST /ai/tap/tools/topic-detection | Synchronous completed-conversation topic classification with the standard { data } tool envelope |
Authentication
All TAP endpoints require these headers:
| Header | Value |
|---|---|
Authorization | Bearer {access_token} |
Ocp-Apim-Subscription-Key | {subscription_key} |
Content-Type | application/json |
The tagging and topic detection integrations do not require TAP dashboard, public API, Annex, or write credentials in the AI service.
For backwards compatibility, existing image tagging callers can continue using POST /ai/tap/workflows/tagging-suggestions. New callers should use the tool endpoint.
Flow
For image tagging request and response schemas, see the TAP Image Tagging API.
For topic detection request and response schemas, see the TAP Topic Detection API.
For moderation request and response schemas, see the TAP Content Safety API.