Get started

Refiner for AI agents

Refiner collects in-product surveys and feedback, letting teams track contacts, segments, and survey responses to understand users. 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 RefinerSee the 10 actions ↓
Forms and surveysAPI keyMCP + RESTrefiner.io
AUDIT LOG · REFINERPOLICY: acme-support
09:41:07 · claude · u_8f2read
refiner.get_forms
Get Forms✓ allowed · 212ms
09:41:08 · claude · u_8f2read
refiner.get_contact
Get Contact✓ allowed · 164ms
09:41:09 · claude · u_8f2write
refiner.update_contact
Update Contact✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
refiner.delete_contact
Delete Contact✕ blocked · policy: deny
EVERY REFINER CALL, ON THE RECORD
01 · USE CASES

What agents do in Refiner.

01

Pull survey responses

Get the latest survey responses and reporting for a form to summarize what customers are saying.

02

Update a contact record

Update a contact's fields after a support conversation reveals new information about them.

03

Confirm before deleting a contact

Look up a contact's segment and history first, then delete them only once approved.

02 · ACTIONS

10 Refiner actions, graded by risk.

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

read

8

Look things up. Allowed by default.

  • refiner.get_forms
    Get Forms
  • refiner.get_contact
    Get Contact
  • refiner.get_contacts
    Get Contacts
  • refiner.get_segments
    Get Segments
  • refiner.get_reporting
    Get Reporting
  • refiner.get_responses
    Get Survey Responses
  • refiner.get_account_info
    Get Account Info
  • refiner.track_event
    Track Event

write

1

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

  • refiner.update_contact
    Update Contact

destructive

1

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

  • refiner.delete_contact
    Delete Contact
03 · HOW IT WORKS

Refiner in three steps.

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

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

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

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

More forms and surveys apps.

SafetyCulture255 actionsFormbricks45 actionsTypeform35 actionsFillout Forms22 actionsSurveyMonkey22 actionsFormdesk20 actionsBasin19 actionsDatascope19 actions
ALL FORMS AND SURVEYS APPS →
07 · FAQ

Refiner and Arc0, answered.

Q01

Can I use Refiner with Claude, ChatGPT or Cursor?

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

Q02

How do users connect Refiner?

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

10 in total: 8 read, 1 write and 1 destructive, such as “update Contact”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Refiner?

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

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

Get started

Plug Refiner into your agent.

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

Connect RefinerBrowse all apps →

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