Get started

Check Cherry for AI agents

Check Cherry runs the back office for photography and event businesses, handling leads, bookings, appointments, and payments in one system. 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.

Connect Check CherrySee the 25 actions ↓
CRMAPI keyMCP + RESTcheckcherry.com
AUDIT LOG · CHECK CHERRYPOLICY: acme-support
09:41:07 · claude · u_8f2read
check_cherry.list_leads
List Leads✓ allowed · 212ms
09:41:08 · claude · u_8f2read
check_cherry.get_lead
Get Lead✓ allowed · 164ms
09:41:09 · claude · u_8f2write
check_cherry.create_expense
Create Expense✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
check_cherry.delete_expense
Delete Expense✕ blocked · policy: deny
EVERY CHECK CHERRY CALL, ON THE RECORD
01 · USE CASES

What agents do in Check Cherry.

01

Check availability for an event

Check whether a given date and time slot is available before confirming a booking.

02

Look up a lead's details

Look up a lead's details before following up on a new inquiry.

03

Confirm before deleting an appointment

Confirm before deleting a scheduled appointment, since the client would need to be notified.

02 · ACTIONS

25 Check Cherry actions, graded by risk.

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

read

17

Look things up. Allowed by default.

  • check_cherry.get_lead
    Get Lead
  • check_cherry.get_event
    Get Event
  • check_cherry.get_report
    Get Report
  • check_cherry.list_leads
    List Leads
  • check_cherry.list_events
    List Events
  • check_cherry.list_expenses
    List Expenses
  • check_cherry.list_payments
    List Payments
  • check_cherry.list_offerings
    List Offerings
  • check_cherry.get_appointment
    Get Appointment
  • check_cherry.get_questionnaire
    Get Questionnaire
  • check_cherry.list_appointments
    List Appointments
  • check_cherry.list_event_bookings
    List Event Bookings
  • check_cherry.list_questionnaires
    List Questionnaires
  • check_cherry.list_appointment_slots
    List Appointment Slots
  • check_cherry.list_expense_categories
    List Expense Categories
  • check_cherry.list_questionnaire_templates
    List Questionnaire Templates
+ 1 MORE

write

5

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

  • check_cherry.create_expense
    Create Expense
  • check_cherry.update_expense
    Update Expense
  • check_cherry.create_appointment
    Create Appointment
  • check_cherry.update_questionnaire_answers
    Update Questionnaire Answers
  • check_cherry.attach_questionnaire
    Attach Questionnaire

destructive

3

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

  • check_cherry.delete_expense
    Delete Expense
  • check_cherry.delete_appointment
    Delete Appointment
  • check_cherry.remove_questionnaire
    Remove Questionnaire
03 · HOW IT WORKS

Check Cherry in three steps.

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

# 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 Check Cherry connects.

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

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More crm apps.

Salesforce224 actionsHubSpot263 actionsZendesk457 actionsPipedrive403 actionsApollo67 actionsAttio109 actionsAcculynx8 actionsAeroleads1 actions
ALL CRM APPS →
07 · FAQ

Check Cherry and Arc0, answered.

Q01

Can I use Check Cherry with Claude, ChatGPT or Cursor?

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

Q02

How do users connect Check Cherry?

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

25 in total: 17 read, 5 write and 3 destructive, such as “create Expense”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Check Cherry?

Yes. Actions like “delete Expense” 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 Check Cherry too?

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

Get started

Plug Check Cherry into your agent.

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

Connect Check CherryBrowse all apps →

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