Specific for AI agents

Specific analyzes recorded sales calls to surface what worked and what didn't, giving revenue teams structured data on conversations instead of raw transcripts. 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.

SalesAPI keyMCP + RESTspecific.app
AUDIT LOG · SPECIFICPOLICY: acme-support
09:41:07 · claude · u_8f2read
specific.list_users
List Users✓ allowed · 212ms
09:41:08 · claude · u_8f2read
specific.list_sources
List Sources✓ allowed · 164ms
09:41:09 · claude · u_8f2write
specific.create_user
Create User✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
specific.delete_user
Delete User✕ blocked · policy: deny
EVERY SPECIFIC CALL, ON THE RECORD
01 · USE CASES

What agents do in Specific.

01

List recent sales conversations

List conversations logged for a company to review call activity before a renewal discussion.

02

Look up a company before updating it

Look up a company's record and custom fields before an agent updates them with new deal context.

03

Confirm before deleting a company record

Check a company's linked conversations and users before deleting its record, since the removal is permanent.

02 · ACTIONS

18 Specific actions, graded by risk.

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

read

7

Look things up. Allowed by default.

  • specific.list_users
    List Users
  • specific.list_sources
    List Sources
  • specific.list_surveys
    List Surveys
  • specific.list_companies
    List Companies
  • specific.get_my_workspace
    Get My Workspace
  • specific.list_conversations
    List Conversations
  • specific.list_custom_fields
    List Custom Fields

write

7

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

  • specific.create_user
    Create User
  • specific.update_user
    Update User
  • specific.create_company
    Create Company
  • specific.update_company
    Update Company
  • specific.create_conversation
    Create Conversation
  • specific.create_or_update_user
    Create Or Update User
  • specific.create_or_update_company
    Create or Update Company

destructive

4

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

  • specific.delete_user
    Delete User
  • specific.delete_company
    Delete Company
  • specific.delete_user_attributes
    Delete User Attributes
  • specific.delete_company_attributes
    Delete Company Attributes
03 · HOW IT WORKS

Specific in three steps.

  1. 01Your users connect SpecificThey add their Specific api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create User” can wait for the user, and “delete User” can be denied outright.
  3. 03Any agent can actYour agent calls Specific 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('specific', {
  read: 'allow',
  write: 'ask',        // create_user
  destructive: 'deny',  // delete_user
})

# 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 Specific connects.

Users add their Specific 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 Specific 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 Specific from any agent.

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

Specific and Arc0, answered.

Q01

Can I use Specific with Claude, ChatGPT or Cursor?

Yes. Connect Specific 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 Specific actions you allow.

Q02

How do users connect Specific?

Users add their Specific 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 Specific actions can my agent take?

18 in total: 7 read, 7 write and 4 destructive, such as “create User”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Specific?

Yes. Actions like “delete User” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Specific too?

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

Get started

Plug Specific into your agent.

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

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