PayChasers for AI agents
PayChasers automates payment reminders and follow-ups for overdue client accounts. Freelancers and small businesses use it to chase late invoices without awkward manual emails. 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.
What agents do in PayChasers.
Send a follow-up on an overdue chase
Trigger a follow-up reminder for a client whose payment is still outstanding.
Check open chases read-only
List active chases to see which overdue accounts still need attention.
Mark a chase as paid
Update a chase to paid once a client's overdue invoice has been settled.
7 PayChasers actions, graded by risk.
Every PayChasers action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- paychasers.list_chasesList Chases
- paychasers.list_clientsList Clients
- paychasers.get_current_userGet Current User
write
4Create and change things. Allow, or ask the user first.
- paychasers.create_chaseCreate Chase
- paychasers.create_clientCreate Client
- paychasers.send_follow_upSend Follow-Up
- paychasers.mark_chase_paidMark Chase Paid
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
PayChasers in three steps.
- 01Your users connect PayChasersThey add their PayChasers api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Chase” can wait for the user to approve.
- 03Any agent can actYour agent calls PayChasers through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('paychasers', { read: 'allow', write: 'ask', // create_chase destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How PayChasers connects.
Users add their PayChasers 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 PayChasers 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
Use PayChasers from any agent.
More finance and accounting apps.
PayChasers and Arc0, answered.
Can I use PayChasers with Claude, ChatGPT or Cursor?
Yes. Connect PayChasers 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 PayChasers actions you allow.
How do users connect PayChasers?
Users add their PayChasers 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.
Which PayChasers actions can my agent take?
7 in total: 3 read, 4 write and 0 destructive, such as “create Chase”. Your policies decide which of them each agent may call.
Can I make my agent read-only in PayChasers?
Yes. Allow read actions and deny writes in the PayChasers policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call PayChasers too?
Yes. The same PayChasers connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug PayChasers into your agent.
Your users connect PayChasers once, under your brand. Your agent gets 7 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan