Claude Code
File: .mcp.json (raiz do projeto) ou ~/.claude.json
{
"mcpServers": {
"falaai": {
"type": "http",
"url": "https://mcp-falaai.action.tec.br/mcp",
"headers": { "Authorization": "Bearer fai_..." }
}
}
}For teams running AI agents
Same engine as the FalaAI API, a different contract: instead of endpoints, your assistant discovers the tools, picks which one to call and gets the result ready for context. Connect a URL and a fai_ token — no integration code.
From $33.33/month for 90,000 credits
MCP server endpoint
https://mcp-falaai.action.tec.br/mcpcurl -fsS https://api01-falaai.action.tec.br/v1/healthhealth needs no key and costs no credits. Analysis tools use the same Bearer fai_ as the REST API.
Each client uses a different field for a remote server. Copy your block and replace fai_... with your key.
File: .mcp.json (raiz do projeto) ou ~/.claude.json
{
"mcpServers": {
"falaai": {
"type": "http",
"url": "https://mcp-falaai.action.tec.br/mcp",
"headers": { "Authorization": "Bearer fai_..." }
}
}
}File: .vscode/mcp.json
{
"servers": {
"falaai": {
"type": "http",
"url": "https://mcp-falaai.action.tec.br/mcp",
"headers": { "Authorization": "Bearer fai_..." }
}
}
}File: .cursor/mcp.json ou ~/.cursor/mcp.json
{
"mcpServers": {
"falaai": {
"url": "https://mcp-falaai.action.tec.br/mcp",
"headers": { "Authorization": "Bearer fai_..." }
}
}
}File: ~/.gemini/settings.json
{
"mcpServers": {
"falaai": {
"httpUrl": "https://mcp-falaai.action.tec.br/mcp",
"headers": { "Authorization": "Bearer fai_..." }
}
}
}Each client doc is linked under the block. UIs change between versions: what matters is the URL and the Authorization header.
The assistant picks the tool; you do not write HTTP. The fields below are the MCP server contract.
Checks the connection and returns version, uptime, database and API phase.
Turns audio into a transcript with diarization and audio events.
Summary, reason, action, topic and sentiment.
Risk and compliance audit with score, detections and an HTML report.
Segments a WhatsApp export into per-speaker conversations; dry_run estimates without charging.
From the 2-minute test to the file scenario. Every card shows the real path, the effort and the official documentation of the MCP client.
To use the MCP services, connect your client first.
Open quickstartConnect FalaAI's remote MCP server to Claude Code, Cursor, VS Code or Gemini CLI and call the five tools from the chat itself: health (free, no key), transcribe_audio, diagnostic, risk_audit and extract_whatsapp. Audio comes back transcribed with speakers identified; the analysis comes back with a diagnosis, a risk score and traceable HTML — without writing a single line of HTTP. For teams that already work inside an MCP client.
The bot receives the audio, downloads the file via getFile (Telegram's own 20 MB limit — FalaAI's API accepts up to 1 GB) and returns a speaker-identified transcript via transcribe_audio, a diagnosis (diagnostic) and a risk audit (risk_audit). For auditing field calls, voice-note sales and support conversations sent by your team.
For auditing a WhatsApp export: run extract_whatsapp with dry_run=true to preview the conversations, with no AI and no charge; then split the export into conversations and run diagnostic and risk_audit on each one. Built for batches of support, quality and compliance conversations.
WhatsApp exports with voice notes: ask for a dry_run=true preview to see conversations, audio minutes and estimated credits, with no AI and no charge; then extract with voice_note=true, which transcribes voice messages inside extract_whatsapp itself, and summarize each conversation from the response. For quality and support teams that receive WhatsApp exports with audio.
Ask in natural language and the agent walks a local folder, transcribes each audio with speakers identified (transcribe_audio) and audits the risk of each call (risk_audit), returning a table with file, score and verdict. Reading the folder is MCP client code, not a FalaAI tool — the client needs access to the directory. For auditing batches of field recordings, call center and quality calls in one run, with each file's JSON kept as evidence.
Ask for the triage in natural language and the agent walks the batch of conversations the MCP client can read, runs diagnostic once per conversation (dialog, duration_seconds and language) and returns summary, reason, action, label and sentiment. It then filters negative sentiment and delivers the complaint list with reason and suggested action. There is no batch tool: N conversations = N diagnostic calls (plus N transcribe_audio when audio is involved).
For collections compliance and quality: the agent transcribes the recording with speakers identified (transcribe_audio) and runs risk_audit with call_direction=outbound and response_format="v2", flagging any approach outside compliance. The response carries verdict, scores, detections, summary and html_report as base64 gzip for traceable evidence. For auditing active collections calls, negotiation scripts and objection handling without writing HTTP.
Ask for the cost before processing: the agent calls extract_whatsapp with dry_run=true and returns the whatsapp_preview with credits_total, params, windows, items and warnings, without calling AI and with credits_charged=0. You tune gap_minutes, min_messages and the window, approve the preview and only then run the real extraction, which returns the conversations and usage.credits_consumed. The export goes as file_base64 to the MCP server.
The call audio goes through transcribe_audio, diagnostic returns summary, reason, next action, label and sentiment, and the agent logs the note on ticket #123. The CRM is another MCP server (HubSpot, Zendesk or Odoo) connected in the same client: it is not a FalaAI tool and the note is written by the CRM tool, with its own OAuth. It requires an extra MCP connection and someone present to authorize it.
The agent calls health, which is public, needs no key and no credit, and checks status, version, uptime, database and phase before any charged call. Running it hourly and warning when the API or database goes down is not the MCP's job: the schedule lives in your agent or cron, and the alert in Slack, email or a status page. It is the smoke test before the batch.
Compliance needs evidence, not a summary: the agent runs risk_audit on the diarized dialog and returns verdict with level, scores, detections, summary and html_report (base64 gzip). Ask for the decode and the HTML becomes the attachment the client opens in the browser, with the line that triggered each detection. The report only exists with dialog input: plain text returns no html_report.
One call, two languages: language describes the conversation, response_language describes the result. The agent transcribes the audio in Spanish (transcribe_audio) and runs risk_audit with language="es-ES" and response_language="pt-BR": the verdict, the detection labels and the HTML come out in Portuguese. Accepted: pt-BR, en-US and es-ES. For auditing a Spanish-speaking operation and delivering the report in Portuguese without manual translation.
Need a custom integration?
Action implements itThree ways to give your assistant conversation intelligence — and why MCP tools return evidence instead of loose text.
Where it runs
Locked to one product or becomes a manual prompt
Inside your client (Claude Code, VS Code, Cursor, Gemini CLI)
What you write
Hand-built JSON payload for every conversation
No HTTP: the assistant picks the tool and builds the call
Output
Free text that changes on every response
Fixed-schema JSON: turns, detections, risk score and evidence
Proof
No auditable report
Forensic HTML report with quotes and timeline
Cost
Per-seat subscription or opaque credits
Pay per use, with usage.credits_consumed on every response (health is free)
Data
Depends on the plugin vendor
Stateless and zero-storage: no audio, text or result retained
Three closed, consistent axes — sentiment, label and action — mean understanding how the customer felt, what they talked about and how the interaction ended. They are FalaAI Studio's base read and do not change the score: they enrich the analysis, not the rating.
FalaAI Studio applies sentiment analysis, contact classification and outcome detection to every contact center interaction. With this closed vocabulary, quality, compliance and operations teams read thousands of conversations in a standardized way: customer sentiment, the contact label (negotiation, cancellation, complaint, support and more) and the final action (resolved, escalated, abandoned, among others). It is transparency about what the engine delivers — for quality monitoring, risk prioritization and operational intelligence.
Dynamic mapping of the customer's polarity and emotional tone across the entire journey — from full satisfaction to critical friction, enabling real-time identification of micro-shifts in mood and hostility.
Automatic identification of the central vector of the customer's intent, classifying the reason for contact through a closed, robust taxonomy built for high-complexity operations.
Intelligent detection of the interaction's closing status, mapping whether the request was solved, retained, transferred or left unresolved by the agent.
Sentiment, label and action can be customized in a tailored plan, specific to your operation.
FalaAI's structured forensic taxonomy: a proprietary matrix divided into dozens of macro axes and dozens of behavioural and legal sub-criteria. The engine maps from critical compliance deviations to advanced operational quality patterns, delivering literal evidence and calibrated diagnostics for high-demand operations.
FalaAI applies a proprietary forensic taxonomy for contact-center risk auditing: dozens of macro axes and dozens of sub-criteria with legal and behavioural granularity, with literal evidence per turn. It is the closed ruler that guarantees the same reading across 100% of conversations — no sampling, no subjective judgement — for quality monitoring, risk prioritisation and operational intelligence.
Categories and subcategories can be customized in a tailored plan, specific to your operation.
You pay for what you use — minutes of audio or thousands of characters. No per-seat license.
Audio transcription
per minute of audio · Minimum 10
per minute of audio
60
10
Diagnosis
per 1,000 characters · Minimum 15
per 1,000 characters
30
15
Risk Audit
per 1,000 characters · Minimum 90
per 1,000 characters
90
90
WhatsApp import
per imported conversation
per imported conversation
0.15
—
You track usage in the dashboard, upload by upload. Alerts warn you before it runs out.
Monthly credits. If you run out, buy standalone packs that never expire.
What are credits? Learn more →
| Free API | Starter API 90K | Most popular Creator API270K | Scale API 2.7M | |
|---|---|---|---|---|
| Price | Free | $33.33/month | $93.75/month | $833.33/month |
| Credits/month | 2,000one-time credits | 90K | 270K | 2.7M |
| Concurrent analyses | 1 | 3 | 4 | 8 |
| SLA | 99.9% | 99.9% | 99.9% | 99.9% |
| Start Free | Subscribe | Subscribe | Subscribe |
More conversations analyzed at once or specific requirements? We'll tailor it.
If the monthly balance runs out, buy standalone credit packages. They never expire and are only consumed after the plan's balance.
When you create your account, you get 2,000 free credits - no monthly recharge and no expiry. If you need more, buy as many credit packs as you want, whenever you need - they never expire.
Packs by plan
The price per credit drops as the plan grows - so the same pack can have different prices.
Available standalone credit packages (price per credit varies by plan):
Standalone never expires. Consumed after the monthly balance. Available in the dashboard.
BuyAvailable standalone credit packages (price per credit varies by plan):
Standalone never expires. Consumed after the monthly balance. Available in the dashboard.
BuyAvailable standalone credit packages (price per credit varies by plan):
Standalone never expires. Consumed after the monthly balance. Available in the dashboard.
BuyAvailable standalone credit packages (price per credit varies by plan):
Standalone never expires. Consumed after the monthly balance. Available in the dashboard.
BuyTranscription: audio minutes/month. Diagnostic/Audit: enter in thousands of characters (e.g. 1 = 1,000 chars, 5 = 5,000).
Choose a plan
What fits in the plan
Reference: 1 min ~ 800 characters · 5 min ~ 4,000 · 10 min ~ 8,000
Use as a guide to estimate thousands above.
Total credits needed
0 credits/month
Fill in the fields above to see the recommendation
Zero content retention + encryption + LGPD.
Audio, text and results are not retained: they are processed and discarded. We keep only usage and audit records — never conversation content.
Account data protected in transit (TLS) and at rest, with full per-account isolation. Conversation content is not stored (Zero-Storage).
You are the data controller; Action Tec Brasil acts as processor. Data-subject requests are handled within 15 days.
Forensic HTML report with a timeline, evidence and violated frameworks — ready for audits and legal disputes.
Infrastructure on certified providers
Start with health, which is free. If the audio sits in the PBX or carrier, Action builds the adapter.