Avoma for AI agents

Avoma records, transcribes, and analyzes sales and customer calls, giving revenue teams meeting notes, scorecards, and conversation insights without anyone taking manual notes. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

MeetingsAPI keyMCP + RESTavoma.com
AUDIT LOG · AVOMAPOLICY: acme-support
09:41:07 · claude · u_8f2read
avoma.list_calls
List Calls✓ allowed · 212ms
09:41:08 · claude · u_8f2read
avoma.get_call
Get Call✓ allowed · 164ms
09:41:09 · claude · u_8f2write
avoma.create_call
Create Call✓ approved · approved by user
EVERY AVOMA CALL, ON THE RECORD
01 · USE CASES

What agents do in Avoma.

01

Pull a call's summary and notes

Retrieve the recording, transcript, and notes for a specific sales call before writing a CRM update.

02

Check a rep's scorecard

List scorecard evaluations for a call to see how a rep performed against the team's talk-track before coaching them.

03

Find calls missing a follow-up

List calls from the past week as a read-only check to find ones missing a follow-up summary.

02 · ACTIONS

16 Avoma actions, graded by risk.

Every Avoma action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

15

Look things up. Allowed by default.

  • avoma.get_call
    Get Call
  • avoma.list_calls
    List Calls
  • avoma.list_notes
    List Notes
  • avoma.list_users
    List Users
  • avoma.get_meeting
    Get Meeting
  • avoma.get_recording
    Get Recording
  • avoma.list_meetings
    List Meetings
  • avoma.list_snippets
    List Snippets
  • avoma.list_webhooks
    List Webhooks
  • avoma.list_transcriptions
    List Transcriptions
  • avoma.get_meeting_analysis
    Get Meeting Analysis
  • avoma.get_engagement_summary
    Get Engagement Summary
  • avoma.list_engagement_metrics
    List Engagement Metrics
  • avoma.list_scorecard_evaluations
    List Scorecard Evaluations
  • avoma.list_configuration_resources
    List Configuration Resources

write

1

Create and change things. Allow, or ask the user first.

  • avoma.create_call
    Create Call

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

Avoma in three steps.

  1. 01Your users connect AvomaThey add their Avoma api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “create Call” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Avoma through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('avoma', {
  read: 'allow',
  write: 'ask',        // create_call
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Avoma connects.

Users add their Avoma api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Avoma connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Avoma from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Avoma and Arc0, answered.

Q01

Can I use Avoma with Claude, ChatGPT or Cursor?

Yes. Connect Avoma to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Avoma actions you allow.

Q02

How do users connect Avoma?

Users add their Avoma api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Avoma actions can my agent take?

16 in total: 15 read, 1 write and 0 destructive, such as “create Call”. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Avoma?

Yes. Allow read actions and deny writes in the Avoma policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Avoma too?

Yes. The same Avoma connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Avoma into your agent.

Your users connect Avoma once, under your brand. Your agent gets 16 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan