Chaser for AI agents

Chaser automates accounts receivable follow-up, sending invoice reminders and tracking payments so a finance team gets paid without manual chasing. 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.

Finance and accountingAPI keyMCP + RESTchaserhq.com
AUDIT LOG · CHASERPOLICY: acme-support
09:41:07 · claude · u_8f2read
chaser.list_invoices
List Invoices✓ allowed · 212ms
09:41:08 · claude · u_8f2read
chaser.get_status
Get Status✓ allowed · 164ms
09:41:09 · claude · u_8f2write
chaser.create_invoice
Create Invoice✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
chaser.delete_contact_person
Delete Contact Person✕ blocked · policy: deny
EVERY CHASER CALL, ON THE RECORD
01 · USE CASES

What agents do in Chaser.

01

Check an invoice's status

Check whether a specific invoice has been paid before sending another reminder.

02

Create a new invoice

Create a new invoice for a customer and attach it to their contact record.

03

Confirm before deleting a contact

Confirm before deleting a contact person, since their invoice history stays tied to the account.

02 · ACTIONS

30 Chaser actions, graded by risk.

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

read

13

Look things up. Allowed by default.

  • chaser.get_status
    Get Status
  • chaser.get_invoice
    Get Invoice by ID
  • chaser.get_customers
    Get Customers
  • chaser.list_invoices
    List Invoices
  • chaser.get_overpayment
    Get Overpayment
  • chaser.get_credit_notes
    Get Credit Notes
  • chaser.get_organization
    Get Organization
  • chaser.list_overpayments
    List Overpayments
  • chaser.get_contact_person
    Get Contact Person by ID
  • chaser.get_customer_by_id
    Get Customer by ID
  • chaser.list_contact_persons
    List Contact Persons
  • chaser.get_credit_note_by_id
    Get Credit Note by ID
  • chaser.get_current_organisation
    Get Current Organisation

write

16

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

  • chaser.post_customer
    Create Customer
  • chaser.create_invoice
    Create Invoice
  • chaser.post_credit_note
    Create Credit Note
  • chaser.create_overpayment
    Create Overpayment
  • chaser.update_overpayment
    Update Overpayment
  • chaser.create_contact_person
    Create Contact Person
  • chaser.update_contact_person
    Update Contact Person
  • chaser.put_invoice
    Update Invoice
  • chaser.put_customer
    Update Customer
  • chaser.put_credit_note
    Update Credit Note
  • chaser.upsert_invoices
    Bulk Upsert Invoices
  • chaser.upload_invoice_pdf
    Upload Invoice PDF
  • chaser.upsert_bulk_customers
    Bulk Upsert Customers
  • chaser.upsert_contact_persons
    Bulk Upsert Contact Persons
  • chaser.upsert_credit_notes_bulk
    Bulk Upsert Credit Notes
  • chaser.upsert_overpayments_bulk
    Bulk Upsert Overpayments

destructive

1

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

  • chaser.delete_contact_person
    Delete Contact Person
03 · HOW IT WORKS

Chaser in three steps.

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

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

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

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

Chaser and Arc0, answered.

Q01

Can I use Chaser with Claude, ChatGPT or Cursor?

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

Q02

How do users connect Chaser?

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

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

Q04

Can I stop my agent from deleting things in Chaser?

Yes. Actions like “delete Contact Person” 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 Chaser too?

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

Get started

Plug Chaser into your agent.

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

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