Opérations de l'API Mirra Voice

VérifiéPrudence

Opérations pour l'historique des appels vocaux, transcriptions et métadonnées via l'API REST Mirra Voice. Nécessite une clé API et utilise curl/jq.

Spar Skills Guide Bot
Data & IAIntermédiaire
28/07/2026
Claude CodeCursorCodex
#voice-api#transcripts#rest-api#call-history#curl

Recommandé pour

Synthèse automatique

Interroge l'API Mirra Voice pour récupérer l'historique des appels vocaux, les détails d'un appel, les transcriptions et les résumés via des requêtes curl POST.

Points forts

  • Un point d'entrée POST unique avec resourceId/method : les opérations sont faciles à enchaîner
  • Tableau des opérations explicite (historique, détails, transcription, résumé, recherche, appel actif) avec les arguments documentés
  • Filtres utiles côté API : portée, statut, groupe, plage de dates et pagination limit/offset
  • Réponses JSON prêtes à être filtrées avec jq

Limites

  • Le SKILL.md fournit la clé API via des variables d'environnement non définies : il faut demander la clé et l'URL à l'utilisateur
  • Le document est tronqué après getCallDetails, donc les arguments de getCallTranscript, getCallSummary, searchTranscripts et getActiveCall ne sont pas détaillés
  • Aucune gestion d'erreurs, de limites de débit ou de rotation de clé n'est décrite
Quand l'utiliser

À utiliser lorsqu'un utilisateur veut consulter ses appels vocaux Mirra, retrouver une transcription ou chercher un mot prononcé dans ses conversations.

Quand l'éviter

À éviter si vous n'avez pas de clé API Mirra valide ou si vous cherchez une intégration SDK native plutôt que des appels REST bruts.

Analyse de sécurité

Prudence
Score qualité88/100

The skill performs legitimate REST API calls to retrieve call history and transcripts, using curl and jq. The main concern is that the API key is transmitted to a user-configurable endpoint, which could become an exfiltration vector if the user supplies a malicious URL. No destructive or obfuscated commands are present.

Points d'attention
  • •Sends the user's API key in an x-api-key header to a configurable API_URL; if a custom untrusted URL is provided, the key could be exposed.
Comment cette analyse est faite

Exemples

Recent ended calls
List my last 5 ended Mirra voice calls with their duration and participant count.
Search transcripts
Search my Mirra call transcripts for any mention of 'pricing' and show me the matching segments with speakers.
Summarize a call
Get the transcript summary for call call_1750459861273_qbhg8we and tell me what was decided.

name: mirra-voice description: "Use Mirra to voice call history, transcripts, and call metadata. Covers all Voice SDK operations via REST API." allowed-tools: Read, Bash(curl:, jq:)

Mirra Voice

Voice call history, transcripts, and call metadata

Prerequisites

You need the user's API key. Ask for these if not provided:

  • API_KEY: Mirra API key (generated in Mirra app > Settings > API Keys)
  • API_URL: Defaults to https://api.fxn.world (only ask if they mention a custom server)

API Call Pattern

All operations use a single POST endpoint with the resource ID and method in the body:

curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
  -H "Content-Type: application/json" \
  -H "x-api-key: ${API_KEY}" \
  -d '{
    "resourceId": "voice",
    "method": "{operation}",
    "params": { ...args }
  }' | jq .

Replace {operation} with the operation name from the table below.

Legacy alternative: POST ${API_URL}/api/sdk/v1/voice/{operation} with args as the request body also works but is not recommended for new integrations.

Available Operations

| Operation | Description | |-----------|-------------| | getCallHistory | List voice calls the user participated in, with filters for scope, status, and date range. Return... | | getCallDetails | Get full metadata and participant list for a specific call. Use the call's agoraCallId (from getC... | | getCallTranscript | Get transcript segments for a voice call. Each segment contains the speaker, text, timing, and co... | | getCallSummary | Get a human-readable formatted transcript summary for a voice call. Returns speaker-attributed te... | | searchTranscripts | Full-text search across transcript segments. Searches the text content of all transcripts the use... | | getActiveCall | Check if there is an active (in-progress) voice call in a specific chat or group. Returns call de... |

Operation Details

getCallHistory

List voice calls the user participated in, with filters for scope, status, and date range. Returns call metadata (no transcript content). Use getCallTranscript or getCallSummary to retrieve transcript text for a specific call.

Arguments:

  • scope (string, optional): Filter by call scope: "direct" (1-on-1 with AI), "group", "user" (user-to-user), or "meeting" (public shareable). Omit to return all scopes.
  • status (string, optional): Filter by call status: "active", "ended", "cancelled". Defaults to all statuses.
  • groupId (string, optional): Filter calls to a specific group by group ID.
  • startDate (string, optional): Filter calls created on or after this date (ISO 8601, e.g. "2025-01-15T00:00:00Z").
  • endDate (string, optional): Filter calls created on or before this date (ISO 8601).
  • limit (number, optional): Maximum number of calls to return (default: 20, max: 100).
  • offset (number, optional): Number of results to skip for pagination (default: 0).

Returns:

AdapterOperationResult: Returns { data: { count, offset, limit, calls[] } }. Each call has: id, agoraCallId, scope, status, createdAt, endedAt, durationMs, participantCount, videoEnabled, meetingTitle.

Example:

curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
  -H "Content-Type: application/json" \
  -H "x-api-key: ${API_KEY}" \
  -d '{"resourceId":"voice","method":"getCallHistory","params":{"status":"ended","limit":5}}' | jq .

Example response:

{
  "count": 2,
  "offset": 0,
  "limit": 5,
  "calls": [
    {
      "id": "6789abc",
      "agoraCallId": "call_1750459861273_qbhg8we",
      "scope": "group",
      "status": "ended",
      "createdAt": "2025-06-01T10:00:00Z",
      "endedAt": "2025-06-01T10:45:00Z",
      "durationMs": 2700000,
      "participantCount": 3,
      "videoEnabled": false,
      "meetingTitle": ""
    }
  ]
}

getCallDetails

Get full metadata and participant list for a specific call. Use the call's agoraCallId (from getCallHistory) or the MongoDB _id.

Arguments:

  • callId (string, required): The agoraCallId or MongoDB _id of the call.

Returns:

AdapterOperationResult: Returns { data: { id, agoraCallId, scope, status, createdAt, endedAt, durationMs, videoEnabled, meetingTitle, participants[] } }. Each participant has: userId, username, isGuest, guestName, joinedAt, leftAt, status.

Example:

curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
  -H "Content-Type: application/json" \
  -H "x-api-key: ${API_KEY}" \
  -d '{"resourceId":"voice","method":"getCallDetails","params":{"callId":"call_1750459861273_qbhg8we"}}' | jq .

Example response:

{
  "id": "6789abc",
  "agoraCallId": "call_1750459861273_qbhg8we",
  "scope": "group",
  "status": "ended",
  "createdAt": "2025-06-01T10:00:00Z",
  "endedAt": "2025-06-01T10:45:00Z",
  "durationMs": 2700000,
  "videoEnabled": false,
  "meetingTitle": "",
  "participants": [
    {
      "userId": "user_001",
      "username": "alice",
      "isGuest": false,
      "guestName": "",
      "joinedAt": "2025-06-01T10:00:00Z",
      "leftAt": "2025-06-01T10:45:00Z",
      "status": "LEFT"
    }
  ]
}

getCallTranscript

Get transcript segments for a voice call. Each segment contains the speaker, text, timing, and confidence. Results are sorted by time. For a human-readable summary instead of raw segments, use getCallSummary.

Arguments:

  • callId (string, required): The agoraCallId or MongoDB _id of the call.
  • mirraTriggeredOnly (boolean, optional): If true, return only segments where a Mirra voice command was detected. Default: false.
  • limit (number, optional): Maximum segments to return (default: 50, max: 200).
  • offset (number, optional): Number of segments to skip for pagination (default: 0).

Returns:

AdapterOperationResult: Returns { data: { callId, count, offset, limit, totalSegments, segments[] } }. Each segment has: id, speakerUserId, speakerUsername, text, startMs, endMs, confidence, isFinal, mirraTriggered.

Example:

curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
  -H "Content-Type: application/json" \
  -H "x-api-key: ${API_KEY}" \
  -d '{"resourceId":"voice","method":"getCallTranscript","params":{"callId":"call_1750459861273_qbhg8we","limit":10}}' | jq .

Example response:

{
  "callId": "call_1750459861273_qbhg8we",
  "count": 2,
  "offset": 0,
  "limit": 10,
  "totalSegments": 42,
  "segments": [
    {
      "id": "seg_001",
      "speakerUserId": "user_001",
      "speakerUsername": "alice",
      "text": "Hey, let's discuss the Q2 roadmap.",
      "startMs": 1200,
      "endMs": 3800,
      "confidence": 0.95,
      "isFinal": true,
      "mirraTriggered": false
    }
  ]
}

getCallSummary

Get a human-readable formatted transcript summary for a voice call. Returns speaker-attributed text in "Speaker: text" format. Useful for AI context, summaries, and recaps. For raw segment data, use getCallTranscript instead.

Arguments:

  • callId (string, required): The agoraCallId or MongoDB _id of the call.
  • maxLength (number, optional): Maximum character length of the summary (default: 2000). Transcript is truncated with "[Transcript truncated...]" if it exceeds this.
  • startMs (number, optional): Only include segments starting at or after this millisecond offset from call start.
  • endMs (number, optional): Only include segments ending at or before this millisecond offset from call start.

Returns:

AdapterOperationResult: Returns { data: { callId, summary, characterCount } }. The summary is a formatted string with "Speaker: text" lines.

Example:

curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
  -H "Content-Type: application/json" \
  -H "x-api-key: ${API_KEY}" \
  -d '{"resourceId":"voice","method":"getCallSummary","params":{"callId":"call_1750459861273_qbhg8we"}}' | jq .

Example response:

{
  "callId": "call_1750459861273_qbhg8we",
  "summary": "alice: Hey, let's discuss the Q2 roadmap.\nbob: Sure, I think we should prioritize mobile performance.\nalice: Agreed. Let's also look at the onboarding flow.",
  "characterCount": 158
}

searchTranscripts

Full-text search across transcript segments. Searches the text content of all transcripts the user has access to. Results include the call context and matching segments.

Arguments:

  • query (string, required): Text to search for in transcript content (case-insensitive substring match).
  • groupId (string, optional): Limit search to transcripts from calls in a specific group.
  • startDate (string, optional): Only search transcripts from calls created on or after this date (ISO 8601).
  • endDate (string, optional): Only search transcripts from calls created on or before this date (ISO 8601).
  • limit (number, optional): Maximum number of matching segments to return (default: 20, max: 100).

Returns:

AdapterOperationResult: Returns { data: { query, count, results[] } }. Each result has: segmentId, callId (agoraCallId), speakerUsername, text, startMs, confidence, callCreatedAt.

Example:

curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
  -H "Content-Type: application/json" \
  -H "x-api-key: ${API_KEY}" \
  -d '{"resourceId":"voice","method":"searchTranscripts","params":{"query":"roadmap","limit":5}}' | jq .

Example response:

{
  "query": "roadmap",
  "count": 1,
  "results": [
    {
      "segmentId": "seg_001",
      "callId": "call_1750459861273_qbhg8we",
      "speakerUsername": "alice",
      "text": "Hey, let's discuss the Q2 roadmap.",
      "startMs": 1200,
      "confidence": 0.95,
      "callCreatedAt": "2025-06-01T10:00:00Z"
    }
  ]
}

getActiveCall

Check if there is an active (in-progress) voice call in a specific chat or group. Returns call details if active, or an empty result if no call is in progress.

Arguments:

  • chatInstanceId (string, optional): Check for an active call in a specific chat instance.
  • groupId (string, optional): Check for an active call in a specific group. Provide either chatInstanceId or groupId.

Returns:

AdapterOperationResult: Returns { data: { hasActiveCall, call? } }. If active, call contains: id, agoraCallId, scope, status, createdAt, participantCount, videoEnabled.

Example:

curl -s -X POST "${API_URL}/api/sdk/v2/resources/call" \
  -H "Content-Type: application/json" \
  -H "x-api-key: ${API_KEY}" \
  -d '{"resourceId":"voice","method":"getActiveCall","params":{"groupId":"group_123"}}' | jq .

Example response:

{
  "hasActiveCall": true,
  "call": {
    "id": "6789abc",
    "agoraCallId": "call_1750459861273_qbhg8we",
    "scope": "group",
    "status": "active",
    "createdAt": "2025-06-01T11:30:00Z",
    "participantCount": 2,
    "videoEnabled": false
  }
}

Response Format

All SDK responses return the operation payload wrapped in a standard envelope:

{
  "success": true,
  "data": { ... }
}

The data field contains the operation result. Error responses include:

{
  "success": false,
  "error": {
    "code": "ERROR_CODE",
    "message": "Human-readable error message"
  }
}

Tips

  • Use jq . to pretty-print responses, jq .data to extract just the payload
  • For list operations, results are in data.results or directly in data (check examples)
  • Pass --fail-with-body to curl to see error details on HTTP failures
  • Store the API key in a variable: export API_KEY="your-key"

Du fichier au premier essai

Le téléchargement contient exactement le contenu affiché sur cette fiche. Cette copie peut différer de la dernière version du dépôt source.

Consulter la source et ses fichiers annexes

Ce téléchargement contient uniquement SKILL.md. Les scripts, références, modèles et dépendances éventuels ne sont pas inclus. Récupérez les fichiers nécessaires depuis la source en conservant leur arborescence avant de poursuivre.

1. Télécharger le fichier

Télécharger SKILL.md

Depuis la racine d’un projet de test, enregistrez le fichier sous .skill-downloads/mirra-voice-api-operations-ms47vp2o/SKILL.md, ou utilisez la commande suivante. Ce dossier sert à examiner la skill avant son installation.

Commande pour macOS/Linux ou WSL : un shell POSIX et curl sont nécessaires. Sous Windows sans WSL, utilisez le bouton de téléchargement et créez le dossier manuellement.

mkdir -p '.skill-downloads/mirra-voice-api-operations-ms47vp2o' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/mirra-voice-api-operations-ms47vp2o/download' --output '.skill-downloads/mirra-voice-api-operations-ms47vp2o/SKILL.md.part' && mv '.skill-downloads/mirra-voice-api-operations-ms47vp2o/SKILL.md.part' '.skill-downloads/mirra-voice-api-operations-ms47vp2o/SKILL.md'

2. Vérifier les prérequis

Lisez SKILL.md avant de l’utiliser. Si le fichier cite des scripts ou services externes, examinez-les et préparez les accès nécessaires dans votre environnement de test.

Outils déclarés par l’auteur (à vérifier dans votre agent) : Read, Bash(curl:*, jq:*)

Extrait original : Prerequisites

You need the user's API key. Ask for these if not provided:

  • API_KEY: Mirra API key (generated in Mirra app > Settings > API Keys)
  • API_URL: Defaults to https://api.fxn.world (only ask if they mention a custom server)

Les plateformes de la fiche sont des indications du catalogue. Les chemins ci-dessous suivent la documentation des outils ; ils ne prouvent pas que cette skill y a été exécutée. Aucune version minimale de ces outils n’est attestée pour cette fiche.

3. Charger la skill

Après vérification, copiez le dossier complet dans le projet avec l’une des commandes ci-dessous, puis ouvrez une nouvelle session de l’outil. La commande s’arrête si un dossier du même nom existe déjà : comparez les fichiers avant de le remplacer.

Claude Code
test -f '.skill-downloads/mirra-voice-api-operations-ms47vp2o/SKILL.md' && test -s '.skill-downloads/mirra-voice-api-operations-ms47vp2o/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/mirra-voice' && cp -R '.skill-downloads/mirra-voice-api-operations-ms47vp2o' '.claude/skills/mirra-voice'

Cursor
test -f '.skill-downloads/mirra-voice-api-operations-ms47vp2o/SKILL.md' && test -s '.skill-downloads/mirra-voice-api-operations-ms47vp2o/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/mirra-voice' && cp -R '.skill-downloads/mirra-voice-api-operations-ms47vp2o' '.cursor/skills/mirra-voice'

Codex
test -f '.skill-downloads/mirra-voice-api-operations-ms47vp2o/SKILL.md' && test -s '.skill-downloads/mirra-voice-api-operations-ms47vp2o/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/mirra-voice' && cp -R '.skill-downloads/mirra-voice-api-operations-ms47vp2o' '.agents/skills/mirra-voice'

OpenSkills

OpenSkills doit déjà être installé. La procédure locale install/read est contrôlée avec OpenSkills 1.5.0, qui exige Node.js ≥ 20.6.0. Aucun slug du catalogue n’est résolu automatiquement.

Installation officielle d’OpenSkills
openskills install './.skill-downloads/mirra-voice-api-operations-ms47vp2o'

openskills read 'mirra-voice-api-operations-ms47vp2o'

La lecture doit afficher le contenu du fichier installé et son dossier de base. Elle ne lance ni la skill ni ses dépendances.

Pour un agent qui lit AGENTS.md, synchronisez ensuite l’index. Cette commande modifie AGENTS.md : relisez le diff avant de l’utiliser.

openskills sync

Mode manuel ou autre outil : joignez SKILL.md à une conversation, ou ouvrez-le dans un agent capable de lire les fichiers. Ajoutez les ressources annexes nécessaires. Il n’existe pas de dossier universel reconnu par tous les outils.

4. Faire un premier essai

Utilisez une entrée courte et fictive : un endpoint d’API, un petit document ou un brief d’interface. Dans une nouvelle conversation, joignez le fichier ou donnez son chemin à l’agent, puis adaptez cette demande :

Lis .skill-downloads/mirra-voice-api-operations-ms47vp2o/SKILL.md et applique ses instructions à cet exemple : [décrire une entrée de test]. Indique les fichiers, dépendances ou accès qui manquent. Produis le résultat demandé par la skill sans inventer de données ni exécuter de script non examiné.

Résultat attendu : une sortie correspondant aux instructions de la skill, ou une liste précise des prérequis manquants. Une simple confirmation de lecture ne valide pas le premier usage. Si une ressource externe est indisponible, ce parcours reste à tester.

Skills similaires